Sally runs Linchpin's daily standup and end-of-day check-ins in Slack, using what ClickUp already knows.
Slack standup and EOD
Your standup, drafted from ClickUp
Sally DMs each person a draft of their standup and end-of-day check-in, asks only about the gaps, and writes the answers to ClickUp as them.
Where to start
Choose a starting point
What are you here to do?
Sally serves the people who answer it, the PMs who read it, and the admins who run it.
- People answering: The morning standup, The end-of-day check-in and Commands and shortcuts.
- PMs: The team digest and the Configuration reference.
- Admins and whoever works on it: Running Sally, Troubleshooting, How Sally works, Setting Sally up and How Sally talks in Slack.
What problem it solves
Standup and EOD happen as live calls, with a recurring Daily Standup and EOD Wrap Up task in ClickUp (Linchpin › Stand Up / EOD › Recurring Meetings).
- People hand-type what they did yesterday, what they're doing today, and their blockers. They use client shorthand and plain-text task IDs, with no links.
- PMs then copy and paste those IDs to find the tasks.
- Most of that information is already in ClickUp: assignees, due dates, priorities, status changes, time entries and comments.
What Sally does
- Drafts each person's check-in from ClickUp:
- What they logged time on during their previous working day (Friday, on a Monday).
- What changed.
- What is due today.
- What carried over.
- Asks only about the gaps, with buttons and short forms in Slack:
- A task moved but no time was logged.
- Time was logged with no note.
- A planned task was not touched.
- Today is over capacity.
- Blockers.
- Writes each answer to ClickUp as it's made, as the person: time entries, statuses, and date, priority, estimate or assignee changes. Changing an answer changes ClickUp to match.
- Posts the words when they submit, or ten minutes before the call if they haven't: comments on the tasks they decided about, and one linked comment per person on that day's Daily Standup or EOD Wrap Up task.
- Sends the PM a digest a minute later, before the call.
Getting connected
- Run
/sally connectin Slack and approve ClickUp access. Sally links your Slack account to you by the email address on your Slack profile. - Run
/sally statusto check that you are connected./sallyon its own lists every command and shortcut; see Commands and shortcuts. - Aaron switches people on one at a time. Until then, nothing is sent and nothing is written.
The admin
The admin is at sally.linchpin.com/admin, behind Cloudflare Access. Its pages:
| Page | What it shows |
|---|---|
| Today | Each person's check-in state, and adoption over the last 30 days |
| Activity log | Everything Sally did, in plain English, each row with a reference |
| People | Who is connected and switched on, capacity and out days |
| Preview | A standup or EOD draft built now, with nothing sent |
| Rules | Every setting a PM can tune, versioned with revert |
| Health | Platform status, failed jobs, connections and the webhook (admins) |
Is it working?
- Once a month, right after someone submits a standup, Sally asks whether it's useful: Yes, it helps, It's OK or Not really. One tap, and it never interrupts a check-in.
- Adoption on the admin's Today page shows, for each person over the last 30 days:
- how many check-ins were submitted,
- how many were never confirmed or were out,
- the typical time from prompt to submit,
- their latest answer to the monthly question.
Rollout
The rollout is in phases, tracked in ClickUp under Linchpin › Sally:
| Phase | What it adds |
|---|---|
| 0 | The scaffold, the Slack and ClickUp apps, the admin shell, and spikes |
| 1 | The morning standup draft and the Daily Standup rollup |
| 2 | Triage for untouched and overdue tasks |
| 3 | Capacity and the carried-over breakdown |
| 4 | The EOD check-in |
| 5 | The PM digest, App Home and health |
| 6 | General chat (optional) |
The pilot order is Aaron, then Julia, then Francisco and Brian.