Checklist
Slack onboarding flow checklist: 8 elements every paid community needs
TL;DR
A Slack onboarding flow is not a single welcome message — it is a sequence with timing, conditions, and at least one operator-visible signal. The 8-item checklist below covers what a complete flow includes, the go/no-go threshold for each item, and which automation tier handles it. Items 1–3 are table stakes and free. Items 4 and 5 — the conditional day-3 nudge and the day-7 scorecard — are where most operators have gaps.
What “onboarding flow” means here
Many operators use “onboarding flow” to mean the Slack Workflow Builder rule that fires a welcome DM when someone joins a channel. That is one step in a flow, not a complete one. A flow has three properties a single automated message lacks: it runs over time (the whole first week, not just day 0), it branches on member behaviour (the day-3 nudge fires only for members who stalled), and it gives the operator visibility into who needs a personal intervention before the billing date arrives.
If any of those three properties is missing, you have a greeting, not a flow. The checklist below audits all three. Items 1–3 cover the greeting. Items 4–8 cover the flow.
The 8-point operator checklist
Day-0 personalised DM fires for every new join
Go threshold: 100% of new joins receive a direct message within 5 minutes of joining, addressed by name. Not a channel post — a DM that lands before the member has opened any other channel.
The DM contains exactly one call to action
Go threshold: One verb, one place to go, no more than two sentences of ask. A message that lists three things for the member to do cuts activation in half because most members defer to “when I have more time.”
The DM asks a goal or intent question
Go threshold: The DM ends with an open question (“What do you most want to accomplish in the next 90 days?”) or a two-option choice that captures the member’s intent. This data makes the day-3 nudge specific rather than generic, and it gives the operator a concrete reason to reply personally to the most promising members.
A conditional day-3 nudge — only for stalled members
Go threshold: The nudge fires on day 3 only for members who did not complete the day-0 action. Members who already posted do not receive it. A blanket day-3 reminder sent to everyone performs roughly half as well as a conditional one: the already-active members find it patronising, and stalled members respond better to a message that acknowledges the stall than to a message that pretends it did not happen.
A day-7 operator scorecard with named at-risk members
Go threshold: By Monday of week 2, the operator has a structured list showing who from the prior week’s joins activated, who stalled, and who needs a personal DM before they make a soft cancellation decision. “I will check the workspace member list” is not a go — the scorecard must arrive as a push, not require the operator to pull the data themselves.
Join-to-first-post interval is tracked somewhere
Go threshold: The operator knows their current median time from join event to first post. This is the single most useful measure of onboarding health. Most operators who check find their median is 5–10 days; in communities with a working three-touch flow it is 0–2 days. Without the baseline number there is nothing to improve against.
A week-3 passive-subscriber sweep
Go threshold: At or before day 21, a named list of zero-post members exists and a targeted action is taken. Most monthly communities bill around day 30; the window for an intervention is weeks 3–4, not the day the cancellation request arrives. Identifying passive subscribers at week 3 gives the operator time to act while the member still has a reason to stay.
Personal outreach before first billing date
Go threshold: No member reaches their month-1 billing date without a personal touchpoint from the operator if they have not yet posted. At $50–500/mo per seat, one avoided cancellation covers several hours of operator time. A complete flow rarely lets this situation arise; when it does, this is the last line of defence.
The 5 binary activation signals
You cannot tell whether a flow is working without knowing which member actions correlate with long-term retention. These five signals are binary (done or not done) and are the most predictive in the first week of a paid Slack community. The new member checklist covers the member-facing version — what to ask members to do. This table covers the operator-facing version: what to track and when to treat a missing signal as a risk flag.
| Activation signal | Why it matters | Risk flag if missing |
|---|---|---|
| Posted in #introduce-yourself or equivalent | A public post is an identity commitment. Members who post publicly are measurably less likely to churn in month one. | Not done within 48 hours |
| Replied to the day-0 DM | A reply is a conversation started. Members who reply have signalled they are paying attention and willing to engage with the operator directly. | No reply by day 3 |
| Subscribed to at least 2 non-general channels | Channel subscriptions create pull forces. A member in #general only will stop receiving relevant content and drift away from the workspace. | Still in default channels at day 7 |
| Opened Slack 3+ distinct days in the first week | Habit formation requires repeated activation. Members who open the workspace three or more days in week one have started to build a habit; members who open once and disappear almost never recover. | Fewer than 2 opens in week 1 |
| Participated in one event, thread, or live session | Participation creates a peer connection. Members with at least one peer connection are materially less likely to cancel in months 2–4. | No participation by day 21 |
Which automation tier covers each item
Items 4, 5, and 6 are where Workflow Builder falls short. Items 1–3 are free with a 20-minute Workflow Builder setup and are the right starting point for any community that has not yet automated the day-0 DM.
| Checklist item | Manual DMs | Workflow Builder (free) | Purpose-built bot |
|---|---|---|---|
| 1. Day-0 DM, every join | Partial — only if operator remembers | Yes | Yes |
| 2. Single call to action | Yes | Yes — operator writes the template | Yes |
| 3. Goal question on day 0 | Yes | Partial — can ask; cannot read or branch on reply | Yes |
| 4. Conditional day-3 nudge | Partial — operator checks manually | No — can schedule a day-3 message but not make it conditional | Yes |
| 5. Day-7 operator scorecard | No — manual audit only | No | Yes |
| 6. Join-to-first-post tracked | No | No | Yes |
| 7. Week-3 passive-subscriber sweep | Partial — manual audit possible | No | Yes |
| 8. Personal outreach before billing | Yes — if operator has the list | No — no list generated | Yes — list generated; operator executes |
Items 1–3 can be covered with Workflow Builder for free. The setup guide is on the Slack onboarding automation page, which maps all three tiers (Workflow Builder / Zapier / purpose-built bot) and explains when each is the right layer to add. For a plain-English explanation of what a purpose-built bot does on top of Workflow Builder, see what is a Slack onboarding bot. For the full framework of why the first-week failure is motivational rather than technical, and why items 4–6 are the ones that change the outcome, see the 6-step onboarding playbook.