Onboarding & Activation
How to set up a Slack community onboarding DM sequence without a bot
Most paid Slack community operators reach for a bot before they have a sequence worth automating. The sequence is the value; the bot is just scheduling. This post covers the three-touch architecture (Day 0, Day 3, Day 7), the anatomy of each message, the minimum viable tracking spreadsheet, the three most common mistakes operators make when running the sequence manually, and the threshold at which each touch becomes worth automating.
The sequence before the automation question
The decision to automate an onboarding sequence is a separate decision from the decision to have one. Operators who jump straight to finding a bot are solving the wrong problem: they are asking which tool will send their messages, when the prior question is whether the messages are worth sending. A bot that sends a generic Day 0 welcome, an automated Day 3 reminder, and a templated Day 7 follow-up at scale delivers a genericised experience at scale. The conversion rates reflect this — automated sequences without personalisation produce Day 3 reply rates in the 5–8% range; operator-personalised sequences produce rates of 25–35% because the signal of operator investment reads in the message itself.
The practical implication: design the sequence on paper first. Understand what each message needs to accomplish, what the anatomy of a high-converting version of each looks like, and what the most common failure modes are. Then, and only then, decide what parts are worth automating and when. The operators who get the most out of purpose-built tools are the ones who ran the sequence manually for 60–90 days first — they know which parts of the sequence their community specifically responds to, and they automate those patterns rather than a generic starting point.
This post is about the sequence itself. The member engagement rate benchmarks give you the number that tells you whether your sequence is working once it is running.
The three-touch architecture
The three-touch onboarding sequence has a Day 0 welcome DM, a conditional Day 3 nudge, and a conditional Day 7 escalation. Each touch is conditional: Day 3 fires only if the member has not yet posted; Day 7 fires only if the Day 3 nudge did not produce a post. The sequence is a diagnostic ladder, not a broadcast. A member who posts after Day 0 never receives the nudge or the escalation.
Day 0: the welcome DM
The Day 0 DM is sent within 2 hours of a member joining — ideally within 30 minutes if you are watching the workspace. The orientation window is open when a new member joins; they are paying attention to the community and ready to be directed. A welcome DM sent 24 hours later converts at roughly half the rate of one sent within the hour. The member’s attention has moved on.
The anatomy of an effective Day 0 DM has three components:
1. Acknowledge the join with specificity. Reference something from the member’s signup form — their stated goal, the problem they mentioned, their role. If you collected any goal or context at signup, the Day 0 DM should demonstrate that you read it. The difference between “Welcome to the community” and “Welcome — you mentioned you’re trying to get your first 50 paying members off the waitlist, and that’s exactly the thread in #early-stage this week” is the difference between a form letter and evidence of investment. Members who receive a specific acknowledgement post in week one at a dramatically higher rate than members who receive a generic welcome.
2. Give one specific, narrow first action. Not a channel tour. Not a list of resources. One action: introduce yourself in #intros with a specific prompt (“post one sentence about the problem you’re working on right now”), or reply to a specific thread, or answer a question in a specific channel. The action should be completable in 15 minutes and should have an obvious payoff. The most common failure mode in Day 0 DMs is giving the new member too much to do — linking to eight channels and asking them to explore at their own pace. That instruction produces silence because it offers no specific starting point. One action produces a post because it removes the decision about where to start.
3. Offer to help in a way that requires a reply. Close the message with a specific offer: “DM me if you have a question about where to post first” or “Reply here if you’d like me to introduce you to the two or three members whose work is most relevant to what you’re working on.” The offer of specific introductions is particularly effective in paid communities because peer connections are typically a primary motivation for joining, and the offer converts the welcome message from “here is the product” to “here is the product, being delivered right now.”
What not to include: the community guidelines, links to eight channels at once, a summary of how the community is organised, or any language that reads as automated. Keep the Day 0 DM under 120 words. The signal of investment is the specificity of the reference, not the length of the message.
Day 3: the conditional nudge
The Day 3 nudge goes to members who have not posted in the three days since joining. It is sent on day 3 if the member is in a state of “has not posted and three or more days have passed.” Do not send it to members who already replied to the Day 0 DM or posted in any channel — they are activated and a nudge reads as noise, or worse, as evidence that your messages are automated regardless of how personal they sound.
The structural requirement for the Day 3 nudge is that it must not repeat the Day 0 ask. A member who did not post after the Day 0 DM received the ask, evaluated it, and chose not to act. Sending the same ask again confirms that the choice not to act was reasonable. The Day 3 nudge should pivot: reframe the entry point, lower the bar explicitly, and give a different reason to engage.
Hey [name] — quick note. You mentioned [goal/topic from signup] when you joined. There’s a thread in [specific channel] this week where [brief description of what is being discussed] that you might find worth ten minutes. Happy to pull together a few names to introduce you to if that would be useful — just reply with a yes and I’ll flag the two or three members whose work overlaps most with what you’re focused on right now.
The structural components: a reference to something specific from their signup (demonstrates this is not an automated blast), one concrete object to engage with (a specific thread, not “the community”), and a low-friction secondary offer (introductions) that creates a reason to reply even if the member is not ready to engage publicly. Vary the sentence structure, the framing, and the tone relative to the Day 0 DM. Two DMs that read identically in voice confirm that the sequence is automated. The Day 3 nudge should sound as if you wrote it that morning, not as if you scheduled it three days earlier.
If you do not have a specific goal or role from the signup form, the next best personalisation signal is the channel they first joined if they joined a specific one, their Slack display name domain if it implies a company or profession, or their LinkedIn profile if they linked it in Slack. “I noticed you joined #product-led-growth first — is that the area you’re focused on right now?” is meaningfully more effective than “just checking in to see how things are going.”
Day 7: the escalation
The Day 7 escalation goes to members who are seven or more days in and have still not posted after receiving the Day 3 nudge. These are the members who have received two messages from the operator and have not replied to either. The escalation is the most psychologically challenging touch to send — it feels like a third imposition — and it is also the highest-converting touch in the sequence. Operators who skip the Day 7 escalation because it feels awkward lose 40–60% of the members they could have saved.
The escalation should not read as a third attempt to produce a post. It should read as a genuine check-in from someone who has noticed the silence and wants to understand it. The structural requirements are different from both Day 0 and Day 3:
Hey [name] — I’ve noticed you haven’t had a chance to jump in yet and wanted to check in directly. No pressure at all — some members take a month to find their footing and that’s completely normal. But if there’s something specific that’s made it hard to find the right conversation to join, I’d genuinely like to know — one sentence is more than enough. If the community is just not the right fit for where you are right now, that’s also completely fine to say. I want to make sure it’s not a “didn’t know where to start” problem that I could fix in ten minutes.
The structural components: acknowledge the silence plainly rather than pretending it has not happened, remove the social obligation with explicit permission not to engage, normalise the situation, ask one binary diagnostic question (is this a fit problem or a where-to-start problem?), and give the member permission to say the community is not right for them. The last component is important and counterintuitive: members who feel permission to leave often choose to stay. Members who feel trapped often cancel quietly. A clear “it’s fine to say this isn’t the right fit” produces replies in both directions — and the ones who say “actually I just needed a starting point” convert at a high rate because you have now offered them exactly that.
The Day 7 escalation also generates the most useful operator intelligence of the three touches. Win-back replies from cancelled members are less candid; members at day 7 are still paying and still emotionally close to the decision to join. The answers to “what made it hard to find where to start” are direct product feedback. See the community churn rate benchmarks for the diagnostic framework that turns escalation responses into systematic churn intelligence.
The five-column tracking spreadsheet
The minimum viable tracking system is a Google Sheet with five columns. One row per new member. The weekly routine — pull the member export, add rows, send Day 0 DMs, check who is due for Day 3 or Day 7 — takes 15 minutes for communities receiving under 20 new members per month.
Column A: member_name. Display name from the Slack member directory export.
Column B: join_date. The date the member joined the workspace. Use YYYY-MM-DD format for consistent sort and date arithmetic.
Column C: day_0_sent. The date you sent the welcome DM. Fill this in when you send the message. If you batch-send Day 0 DMs weekly rather than on the day of join, note the actual send date, not the join date — the window timing in columns D and E depends on send date for the conditional logic to work correctly.
Column D: day_3_sent. The date you sent the Day 3 nudge, or the text “skipped — posted” if the member activated before day 3 arrived. Leaving this blank means you have not yet reviewed whether the member needs a nudge. A blank with a day_0_sent more than three days ago is the trigger to check and send.
Column E: day_7_sent. The date you sent the Day 7 escalation, or “skipped — posted after nudge” if the member activated between day 3 and day 7. Again, blank with a day_3_sent more than four days ago and no post is the trigger to check and send.
The weekly review routine: open the sheet, sort by join_date descending. For any row where day_0_sent is blank, send the welcome DM and fill in the date. For any row where day_0_sent is filled, day_3_sent is blank, and today is three or more days after day_0_sent, check whether the member has posted; if not, send the nudge and fill in day_3_sent; if yes, mark “skipped — posted.” For any row where day_3_sent is filled with a date (not “skipped”), day_7_sent is blank, and today is four or more days after day_3_sent, check whether the member has posted; if not, send the escalation and fill in day_7_sent; if yes, mark “skipped — posted after nudge.”
For communities receiving more than 20 new members per month, a sixth column — activated_date (the date of the member’s first post) — is worth adding. It lets you calculate week-one activation rate directly from the sheet and compare it to the benchmarks in the onboarding scorecard guide without running a separate query.
The three most common mistakes
Mistake 1: sending the Day 3 nudge to members who already replied. This is the most common error when operators do the weekly review quickly. Check the day_3_sent column before sending — if it says “skipped — posted,” the member is activated and should not receive a nudge. Sending the Day 3 nudge to an activated member confirms that your sequence is automated regardless of how personal the message sounds. The member who received a personalised Day 0 DM, posted in #intros, and then received a “hey just checking in to see if you found where to start yet” message three days later will correctly conclude that the sequence is a bot. Checking the sheet before sending takes 10 seconds per row and is the most important quality step in the weekly routine.
Mistake 2: writing both Day 0 and Day 3 in the same voice. When the Day 0 welcome and the Day 3 nudge read identically in structure, sentence length, and tone, they confirm that the sequence is automated. This destroys the conversion value of the Day 3 nudge regardless of the content. The Day 0 DM should read as an orientation message; the Day 3 nudge should read as a thought you had specifically about this member’s situation. Vary the sentence structure. Vary the framing. If the Day 0 DM was formal and direct, the Day 3 nudge can be shorter and more conversational. The member should never be able to pick both DMs out of a lineup and say “these are clearly from the same template.”
Mistake 3: skipping the Day 7 escalation because it feels awkward. This is the most expensive mistake in the sequence. The Day 7 escalation is the highest-converting touch of the three — operators who skip it lose 40–60% of the members they could have activated. The discomfort of sending a third message to someone who has not responded twice is real but systematically overestimated. Members who have not replied have not told you they want to be left alone; they have not posted, which is different. The Day 7 escalation that gives explicit permission to leave often produces the most honest conversations an operator has with their community, and the replies are the most useful diagnostic data in the entire sequence. Skip Day 7 consistently and your activation rate will plateau 15–20 percentage points below where it could be.
When to automate (and what you lose)
The right approach is to automate the touches in order from lowest-leverage to highest-leverage — the opposite of the order most operators follow. Most operators automate Day 0 first because it is the easiest to schedule; this is correct. Automate Day 3 second when you hit 15–20 new members per month and the conditional logic (only send if no post) becomes tedious to check manually each week. Keep Day 7 manual for as long as possible.
The reason is conversion rate differential. An automated Day 0 DM that uses personalisation tokens from the signup form (first name, stated goal, community type) converts at 15–20% — meaningfully below the 30–35% of a genuinely personal operator DM, but acceptable at volume because the alternative is no Day 0 DM or a delayed one. An automated Day 3 nudge with conditional logic (fires only if no post detected in the last 72 hours) converts at 12–18%, compared to 25–35% for a manual one; again, the time savings justify the conversion cost at volume. An automated Day 7 DM converts at 10–15%. A clearly personal Day 7 DM converts at 40–60%. The Day 7 gap is large enough that automating it should be the last step in the sequence, not the first.
The automation thresholds that make practical sense:
Under 15 new members per month: run the full sequence manually. The time cost is under 2 hours per month, the personalisation is achievable at that volume, and a manual Day 7 escalation at 40–60% conversion is more valuable than any automation saves in time.
15–30 new members per month: automate Day 0. Keep Day 3 and Day 7 manual. At 20 new members per month, the Day 0 DM send takes 20–40 minutes per week; automating it saves meaningful time without sacrificing the conversion impact that matters most (Day 3 and Day 7).
30–50 new members per month: automate Day 0 and Day 3 with conditional logic. Keep Day 7 manual. At 40 new members per month, the Day 3 nudge list is 20–30 members per week; checking each manually takes 30–45 minutes. Automating the conditional check and the send saves that time. Day 7 is still 10–15 members per week at this volume — manageable manually, and worth keeping personal for the conversion differential.
Above 50 new members per month: automate Day 0 and Day 3. Consider a hybrid Day 7 where the tool flags the at-risk member list and pre-populates a personal DM template you review and send with one click, rather than full automation. The Onboarding Health Check will tell you which of your three touches is currently underperforming so you know which one to prioritise fixing before automating.
Frequently asked questions
What should I say in a Slack community onboarding DM?
A Day 0 onboarding DM should acknowledge the join with a specific reference to the member’s stated goal or reason for joining, give one specific narrow first action completable in 15 minutes, and offer to help in a way that requires a reply. Keep the message under 120 words. Do not include the community guidelines, links to eight channels, or any language that reads as automated. The Day 3 nudge should structurally differ from Day 0 — reframe the original ask rather than repeat it, lower the bar explicitly, and give a different reason to engage. The Day 7 escalation should acknowledge the silence directly, remove social obligation, and ask one binary diagnostic question: is this a fit problem or a where-to-start problem?
When should I send onboarding DMs to new Slack community members?
The Day 0 DM should be sent within 2 hours of a member joining. The Day 3 nudge is sent to members who have not yet posted after 3 days — conditional on inactivity, not on the calendar. Do not send the nudge to members who already replied or posted. The Day 7 escalation goes to members who received the Day 3 nudge and still have not posted. The sequence is conditional throughout: each subsequent touch fires only if the previous touch did not produce a post. A member who posts after Day 0 receives no nudge or escalation.
How do I track who has received onboarding DMs in a Slack community?
The minimum viable tracking system is a Google Sheet with five columns: member_name, join_date, day_0_sent, day_3_sent (or “skipped — posted” if the member activated first), and day_7_sent (or “skipped — posted after nudge”). One row per new member. Review weekly: add rows for new joiners, send Day 0 DMs, check the day_3_sent and day_7_sent columns for anyone who is overdue. The routine takes 15 minutes per week for communities under 20 new members per month. The most important quality step is checking the sheet before sending to confirm you are not nudging a member who already posted — that mistake confirms the sequence is automated regardless of how personal it sounds.
What is the difference between the Day 0 DM, Day 3 nudge, and Day 7 escalation in a Slack community onboarding sequence?
The three touches serve structurally different moments. The Day 0 DM is an orientation message that meets the member while their attention is open, acknowledges their goal, and gives one specific first action. The Day 3 nudge is a conditional reframe — sent only to members who have not posted, it pivots the entry point rather than repeating the Day 0 ask. The Day 7 escalation is a diagnostic intervention that acknowledges silence directly, removes social obligation, and asks one binary question to identify whether the problem is fit or where-to-start. The Day 7 touch converts at 40–60% when personal and is the highest-leverage touch in the sequence — operators who skip it because it feels awkward lose the majority of the members they could have activated.