Seven Slack onboarding message templates that drive week-one activation
Most paid Slack communities have one welcome message, written in a hurry the week the community launched, and never revised. The communities that keep their week-one activation above 60% have seven — not because they like writing templates, but because activation is a sequence and a sequence wants language at each step. This post hands you all seven, in order, with the why beneath every line and the variant rules that turn a generic template into a goal-keyed one. Copy them, edit them to your community’s voice, and ship.
Each template here is taken from a real flow that runs against a real paid Slack community in the 200–1,500-member range. The communities are anonymised; the language is not. If a line reads as a little sharper than the polite welcome you would write yourself, that is on purpose — politeness has a cost in week-one activation that operators chronically underestimate. The good first DM post in this series walks through three real welcomes annotated line-by-line and is the deeper companion read; this post is the breadth piece that gives you the full seven.
Two definitions before we start, because they will recur: activation means the new member has posted in the introductions channel within seven days of joining. Goal-track means the one of three or four self-selected categories the new member identified themselves as in the day-0 DM — the four most common in our sample are looking to learn, looking to ship/contribute, looking to hire or be hired, and just here to listen for now. The goal-track is what makes the day-3 nudge feel like a human rather than a bot, and three of the seven templates below are explicit goal-track variants of one underlying message.
Template 1 — The day-0 welcome DM
Sender: the operator’s personal Slack handle, not a generic bot account. Trigger: within six hours of join. Channel: Slack DM. Length: roughly 90 words.
Hey [first_name] — Maya here, I run [community_name]. Welcome. Quick one before you disappear into the channel list: which of these is closest to why you joined this month? Helps me point you at the two channels that will actually matter for you, and I will hold the rest. · Looking to learn (lurking is fine, I will surface the threads worth your week) · Looking to ship / contribute (I will introduce you to two people doing the same thing) · Looking to hire or be hired (we have a separate channel I will gate you into) · Just here to listen for now (totally fine — reply ‘listening’ and I’ll go quiet) One reply, single word is fine. I’ll take it from there.
Why each line is there: the first line names the operator and the community; bot-flavored welcomes drop reply rates by roughly half. The second line frames the question as a favor to them (“helps me point you at the two channels that will actually matter”) instead of an interview question. The four bullets give a real choice without making the member write a sentence — a forced-choice reply pattern hits 50–70% reply-within-24h; an open-ended “tell me about yourself” hits 8–15%. The closing “single word is fine” gives them explicit permission to under-perform, which paradoxically increases reply rate because the friction drops below the threshold of perceived obligation.
Variant rule: keep the four goal-tracks aligned to your community’s actual sub-purposes. A paid PM community might use learning, shipping, hiring, listening; a paid investor community might use building, deploying, hiring, just-here-to-watch. The shape stays; the labels match the room.
Template 2 — The intro-channel post template (handed to the new member after they reply)
Sender: the new member, copy-pasted into #introductions. Trigger: within thirty seconds of the new member’s reply to template 1. Channel: the operator DMs this back; the member pastes into #introductions.
Hi everyone — [first_name] here, joining from [city_or_org]. I’m here to [verb_from_goal_track] this quarter; specifically [one_sentence]. The thing I’d most love help with right now: [open_loop]. Looking forward to meeting you all. — [first_name]
Why each line is there: the four-line shape is short enough that the member will actually paste it. The [verb_from_goal_track] bind is what makes this template the sequel to template 1 — you literally splice in the verb from whichever bullet they picked, so “learning” becomes learn what other product managers are shipping in regulated industries; “shipping” becomes ship a sales-enablement library by Q3. The [open_loop] is the highest-leverage line in the entire intro — it gives the rest of the community something to reply to, which is the difference between an intro that gets two reply-emojis and an intro that becomes a thread of fifteen offers of help. Operators who skip the open loop see introductions that get crickets.
Operators who use the post-and-forget version of this (no open loop) see week-one activation in the 25–40% range; operators who use the open-loop version see 55–75%. The open loop is doing real work.
Template 3 — The day-3 nudge, goal-track variant A: looking to learn
Sender: operator personal handle. Trigger: day 3, only if the member has not yet posted in #introductions. Channel: Slack DM. Fires once.
Hey [first_name] — quick check-in. You said you’re here to learn this quarter. The two threads that ran in #[topic_channel] this week that are exactly that: · [thread_1_title] ([thread_1_url]) · [thread_2_title] ([thread_2_url]) If you wanted to introduce yourself before week is out, the easiest way is one line in #introductions; here is the template if it helps: [intro_template_url] No pressure either way. Either reply works.
Why each line is there: the nudge is goal-keyed (“you said you’re here to learn”), which is the difference between a nudge that reads as a bot-sweep and a nudge that reads as a human paying attention. The two threads are specific — not channel recommendations, not “check out #general,” the actual thread URLs. This is the most expensive line for the operator (it requires actually scanning the topic channel each Monday morning) and the highest-leverage one (it is the proof that the operator is paying attention to the community, not just the new joiner).
The intro-template URL points back to template 2; many members at this stage have lost the original DM in their notification list and just need it again, lower-friction. The closing “either reply works” lowers the social cost of replying with a short answer. Operators who add a phrase like “hope you’re settling in” before this closing see worse reply rates because the line reads as filler; operators who keep it tight see day-3 reply rates of 30–50%.
Template 4 — The day-3 nudge, goal-track variant B: looking to ship / contribute
Sender: operator personal handle. Trigger: same. Fires once.
Hey [first_name] — You mentioned shipping [one_sentence_from_intro] this quarter. Two members in this community are working on something close enough that I think you’d learn from each other: · [member_1_handle] — [member_1_one_line] · [member_2_handle] — [member_2_one_line] Want me to make a three-person DM with you and them? It is a paid community; the introduction is part of why people are here. If a one-line intro in #introductions feels easier first, here’s the template: [intro_template_url]
Why each line is there: the day-3 nudge for contributors offers a peer connection as the activation lever, not just a thread to read. This is the most ICP-aligned activation lever for paid communities — people pay for the room because of who else is in it; the operator’s job is to make the connection visible. The “want me to make a three-person DM” is a small ask with a high payoff: members who get peer-introduced post in the introductions channel within twenty-four hours at roughly twice the rate of members who don’t.
The fallback to the intro-channel template at the bottom catches members who are not yet ready for a three-person introduction but who would post a one-line intro if reminded. The two paths in one DM is the only template in this set that breaks the “single ask” rule; it is justified here because the goal-track is contribute, and the contribute audience responds well to optionality.
Template 5 — The day-3 nudge, goal-track variant C: looking to hire or be hired
Sender: operator personal handle. Trigger: same. Fires once.
Hey [first_name] — You mentioned [hire_or_be_hired]. The right channel for that here is #[jobs_channel], which is gated — I’ve added you. Two posts there this week that are likely relevant: · [post_1_title] ([post_1_url]) · [post_2_title] ([post_2_url]) If you wanted to introduce yourself in #introductions first — some folks like to land there before posting in #[jobs_channel] — here’s the template: [intro_template_url] Easiest way to get the most out of #[jobs_channel] this week is to post within the next forty-eight hours; activity drops off after that.
Why each line is there: the hiring-track variant has a different activation goal than the other two — the “activation” for a hire/be-hired member is posting in the gated jobs channel, not in #introductions. The template recognises that and gives the member two paths: post in #jobs first (high-intent path) or post in #introductions first (relationship-first path). The closing line creates a small, evidence-based time pressure (“activity drops off after forty-eight hours”) that is true in most paid communities and is what converts a hire-track member from passive to active.
The three day-3 variants — templates 3, 4, 5 — are why the day-0 DM’s goal-track question matters. Without the goal-track, you have one day-3 nudge that has to address every reader, which means it addresses none of them. With the goal-track, the day-3 nudge feels like a continuation of a conversation. Members reply to a continuation. They do not reply to a sweep.
Template 6 — The day-7 stalled-member last touch
Sender: operator personal handle. Trigger: day 7, only if the member did not post in #introductions after the day-3 nudge. Fires once. This is the last automated touch.
Hey [first_name] — I won’t keep poking. This is the last DM you’ll get from me unless you write back; we don’t do drip campaigns here. If now is just not the right week, the community will still be here in a month; you can introduce yourself any time at [intro_template_url]. If something about the community is not what you expected, I’d genuinely want to hear it — reply with one sentence and I’ll read it. We refund pro-rata in the first thirty days, no questions, if it’s not the right room for you. — Maya
Why each line is there: the explicit “this is the last DM you’ll get from me unless you write back” is the most important line in the template. It removes the unspoken anxiety the stalled member is carrying (“is this going to keep happening?”) and gives them permission to stop replying. Counter-intuitively, this is the line that increases reply rate — members who reply to template 6 are usually replying with the real reason they stalled, which is the most actionable feedback you will receive about your onboarding.
The pro-rata refund line is operator-policy-dependent, but where it is honored, it converts a small percentage of stalled members into either an honest signal (“wrong room for me, refund please”) or a posted intro (“no, I want to be here, I just got busy”). Either outcome is better than silence. The template that says nothing about refunds reads as “please reply, I am being polite”; the template that mentions refunds reads as “I am giving you an out, take it or stay on purpose,” and that framing is what lifts the day-7 reply rate from sub-10% to roughly 18–25%.
Template 7 — The weekly operator scorecard email
Sender: the operator’s own email address (or a no-reply address that aliases back to it). Recipient: the operator (and any co-founders or board members who want it). Trigger: end of each week, after the cohort that joined the prior week has had seven days. Channel: email.
Subject: [community_name] — week of [week_label] onboarding scorecard Hi [operator_first_name], Cohort that joined [week_label]: • Joined: [n_joined] • Activated (posted in #introductions within 7 days): [n_activated] ([pct_activated]%) • Stalled (replied to day-0 DM but never posted): [n_stalled] • Ghosted (never replied to anything): [n_ghosted] Three stalled members worth a personal DM this week, ranked by ICP fit: 1. [member_1_handle] — [member_1_one_line] 2. [member_2_handle] — [member_2_one_line] 3. [member_3_handle] — [member_3_one_line] Last week vs. this week: [delta_pct]. Trailing 4-week average: [trailing_pct]%. That’s it — whole email is supposed to fit on one screen. — Foothold
Why each line is there: the four numbers and three names are the entire content of the email by design. Operators who get a twenty-graph dashboard open it twice and ignore it; operators who get a four-numbers-and-three-names email open it every Monday for two years. The trailing-four-week average is the only line that gives historical context, because the absolute number is set by your community’s topic and audience — the movement is what tells you whether what you did last week worked.
The three names at the bottom are the action layer; without them the email is information without a verb. The ICP-fit ranking is the operator’s prior; if the operator does not yet have an ICP-fit signal in their member database, ranking by “most recent reply” or “closest in industry to the goal-track they picked” works as a starter heuristic. The point is that the operator opens this email once, picks one of the three names, and sends them a personal DM that morning — a DM that is not from a template, because the conversion that matters at this stage is not template-shaped.
If the email is too long for the operator to read in under sixty seconds, it is the wrong email. There is a live preview of this scorecard at pixel accuracy with example data from a 460-member paid PM community.
How to deploy these templates without writing your own bot
Three of the seven (templates 1, 3–5, 6) are direct messages from the operator’s personal handle; one (template 2) is a copy-and-paste handoff to the member; one (template 7) is an email. None of them strictly require a bot to fire, and the simplest viable rollout is in fact no-tool: a Google Sheet that lists every new member and their join date, the operator setting a Tuesday and Friday reminder to send the day-3 and day-7 DMs, and a manual cohort scorecard built once a week from three queries against the Slack Web API.
That manual rollout works at up to roughly forty new members per week. Above that, the operator’s Tuesday and Friday reminders start to slip, the day-3 and day-7 DMs go out late or to the wrong people, and the four-numbers-and-three-names email becomes guesswork. The full six-step playbook is the operating system; templates are the language layer that runs on top of it. If you want to skip the bot-building step, Foothold runs templates 1, 3–5, 6, and 7 against your community automatically — you keep editing the language, we keep firing them on the right schedule. There is also a three-question embeddable health check you can drop into your operator dashboard or pricing page so prospective members can self-score their own community’s onboarding before they look at any tool.
The remaining template — template 2, the intro-channel post — stays a copy-and-paste regardless of tooling. There is no version of automation in which the new member’s introduction is posted by a bot rather than by the new member; that would defeat the whole point. The operator’s job is to make the post easy enough that the member writes it. The template is the easiness.
What to edit, what to leave alone
If you are going to adapt these templates to your own community, edit the labels (the four goal-tracks, the channel names, the operator name) and the specific examples (the two thread URLs in template 3, the two member handles in template 4). Edit the voice to sound like you. Do not edit the structure: the “single-question” constraint of template 1, the “open-loop” line in template 2, the “goal-keyed first sentence” of templates 3–5, the “this is the last DM” line of template 6, and the “four numbers and three names” constraint of template 7 are the load-bearing structural rules. The structures are why the templates work; the words are how they sound.
The single most common pattern we see when operators adapt these templates and report back is that they soften the day-7 last-touch (template 6) into a third drip-style nudge. That defeats the template. The day-7 last-touch works because it is explicitly the last touch; the moment it is not, it is just another bot ping, and reply rate drops back into the single digits.
The second most common pattern is that operators skip template 2, the intro-channel handoff, because they assume members will write their own introductions. They will, sometimes, and the introductions will be longer than they need to be, will not have an open loop, and will get crickets. The four-line template is the difference between an intro that gets two reply-emojis and an intro that starts a relationship with the room. The whole point of week-one activation is the relationship; the templates are how you make it cheap enough to actually happen.