Welcome DMs
Seven Slack community welcome message templates (annotated)
Writing a welcome DM from scratch is harder than adapting a working one. This post gives you seven templates — five day-0 welcome DM variants by community type, a conditional day-3 nudge, and a win-back DM for passive subscribers — each with line-by-line annotations explaining what makes each structural element work. Use them as starting points; the layer you personalise on top of the scaffold is what gets you from a 12% to a 30%+ reply rate.
How to use these templates
Every template here is built on the same four-element structure: name the person, name the community’s job for them, ask for one specific action, explain why that action matters. The anatomy post explains why those four elements, in that order, produce the structural difference between a 7% and a 30% reply rate. This post skips the theory and gives you the copy.
Two things to preserve when adapting any template below. First, do not add items back. The single-ask structure is the load-bearing element; every item you restore from the “to-do list” approach cuts your reply rate. Second, do not cut the payoff sentence. Operators who adapt these templates and remove the “here’s why this action matters” line — because it feels like explaining yourself — see reply rates drop to the same level as a generic welcome. The payoff sentence is what makes the ask feel worth doing.
Template 1 — The knowledge community day-0 DM (product, SaaS, growth)
Use this for communities where members joined to learn from peers at similar career stages. The core product the community sells is access to how others solved the same hard problems. The activation action should be an introduction that names the problem, not just the person.
Hi [Name] — welcome to [Community]. You’re in a room of [role, e.g., “B2B SaaS founders”] who are actively working on [the one shared hard problem, e.g., “taking a product from first revenue to a repeatable sales motion”]. The fastest way to start getting value is to post a two-sentence intro in #intros: your stage and the one thing you’re trying to solve right now. Members who name a specific problem in their intro get replied to, on average, within [X] hours. What are you working on?
Line-by-line notes:
“You’re in a room of [role] who are actively working on [problem]” — this is the community’s-job sentence. It names the peer group and the problem, not the community’s features. “Actively working on” signals that the room is current and alive, not a static resource library.
“The fastest way to start getting value” — frames the action as an on-ramp, not a requirement. The member reads this as a path to the outcome they paid for, not a task they owe the operator.
“Members who name a specific problem in their intro get replied to, on average, within [X] hours” — this is the payoff sentence. Fill in your actual number; if you do not know it, estimate conservatively. A vague “people usually respond quickly” is weaker than a specific “within four hours” even if the specific number is an approximation.
“What are you working on?” — ends with a question, not a directive. A question has a lower activation threshold than a task. The answer is the intro post draft.
Template 2 — The professional association day-0 DM (sales, RevOps, marketing leadership)
Use this for communities where the product is peer benchmarking: members join because they want to know how peers at similar revenue targets or team sizes are solving the same operational problems. The activation action should surface an immediate business context.
Hi [Name] — you joined at a good time. There’s a thread running right now in #[relevant channel] on [specific current topic, e.g., “what’s actually working in cold outbound at $2M–$10M ARR without SDR headcount”]. That thread is exactly what this community is for — [role] at [stage/segment] comparing notes on the problems that don’t have obvious answers. Jump in if you have an angle, or just read and see what the room sounds like. One question: what’s the problem you’re sitting on right now that you don’t have a clean answer to?
Line-by-line notes:
“You joined at a good time. There’s a thread running right now” — opens by orienting the member to something live, not describing the community. This requires updating the DM weekly with an actual current thread. That maintenance cost is the compound investment: it forces the community to stay current rather than coasting on the static welcome copy.
“That thread is exactly what this community is for” — the community’s-job sentence delivered through an example rather than a definition. Showing is more credible than telling for a peer-benchmarking community, because the value of a peer network is demonstrated by the quality of the conversations, not the description.
“Jump in if you have an angle, or just read and see what the room sounds like” — gives the member two options that both serve the operator. Jumping in is activation; reading is partial activation that usually becomes full activation once the member sees the conversation quality. Neither option feels like a task.
“One question:” — the explicit framing “one question” signals that the operator is not building a to-do list. It also names the ask as a question, which is easier to answer than a task. The answer gives the operator a warm signal for personalising the day-3 nudge.
Template 3 — The creator and solopreneur community day-0 DM
Use this for communities where members are building something independently — audience, product, consulting practice — and the value is accountability and visibility with peers who are in the same solo-operator position. The activation action should create a public artifact the member is invested in.
Hi [Name] — welcome to [Community]. You’re now in a room of [solopreneurs / creators / indie founders, depending on your ICP] who are building in public. The fastest way to show up here is to post a one-paragraph intro in #intros: what you’re building, where you are right now (month one, year two, whatever), and the one milestone you’re working toward this quarter. Members who post specific current milestones get people in their corner, not just likes. What are you building?
Line-by-line notes:
“You’re now in a room of [ICP] who are building in public” — “building in public” is load-bearing for this community type. It names the social contract: members share work-in-progress, not polished outputs. That norm lowers the barrier to the intro post, because the member does not need to have something finished to show.
“What you’re building, where you are right now, and the one milestone you’re working toward this quarter” — three sentence-starters in the ask. This is the exception to the single-ask rule: for a long-form intro template, giving the member a three-part structure actually lowers the perceived effort because they have prompts to fill in rather than a blank page. The three-part structure is the ask; it is still one action.
“Members who post specific current milestones get people in their corner, not just likes” — the payoff sentence is about the quality of engagement, not the quantity. For a creator community, “likes” is the low-value outcome the member has already experienced everywhere else. “People in their corner” is the high-value outcome that is specific to this community.
Template 4 — The career transition community day-0 DM
Use this for communities where members are navigating a change — breaking into a field, moving from IC to leadership, changing industries. These members have the highest emotional investment at join; they are paying for a specific outcome (getting a job, getting promoted) that has a clear deadline in their mind. The activation action should acknowledge the goal without pressure.
Hi [Name] — welcome to [Community]. Whatever stage of the transition you’re in — exploring, actively applying, or just deciding whether to take the leap — you’re in the right room. The fastest way to get value here is to introduce yourself in #intros: your background, where you want to go, and where you’re stuck right now. The more specific you are about the stuck part, the more useful the room can be. Members who post a specific question in their intro get direct responses from people who have been exactly where you are. What’s the hardest part of the transition for you right now?
Line-by-line notes:
“Whatever stage of the transition you’re in — exploring, actively applying, or just deciding” — meets the member where they are rather than assuming they are at the same urgency level. This is important for career communities because member motivation varies widely; a member still deciding feels out of place in a room that assumes everyone is actively applying.
“The more specific you are about the stuck part, the more useful the room can be” — this gives the member a principle for what to put in the intro, not just a prompt. It reframes the intro post from a social obligation (introduce yourself) to a functional investment (name the problem and get useful responses).
“Members who post a specific question in their intro get direct responses from people who have been exactly where you are” — the payoff sentence names both the outcome (direct responses) and the quality of the respondents (been where you are). For a career community this peer-experience signal is the product; it should be named explicitly.
Template 5 — The referral-join day-0 DM
Use this when the new member was referred by an existing member. The referral context is the highest-converting personalisation signal available: the new member already has social proof from someone they trust, and the welcome DM should use it.
Hi [Name] — [Referrer name] mentioned you’d be a good fit here, which is why you’re getting this DM directly. [Referrer name] is exactly the kind of member who makes this room work — [one sentence on what the referrer contributes, e.g., “they share what’s actually working in early-stage sales without the LinkedIn polish”]. The fastest way to get oriented is to post a quick intro in #intros — two sentences, what you’re working on and what brought you here. [Referrer name] will likely reply. What’s the main thing you were hoping to get from this community?
Line-by-line notes:
“[Referrer name] mentioned you’d be a good fit here, which is why you’re getting this DM directly” — uses the referral as the personalisation context rather than the community description. The new member’s first signal about the community is not a feature list; it is a trusted contact’s endorsement, delivered again, in the first message they receive.
“[Referrer name] is exactly the kind of member who makes this room work” — social proof and community norm in one sentence. The operator is saying: the person who referred you is valued here; by extension, their judgment about your fit is trusted.
“[Referrer name] will likely reply” — this is the payoff sentence for the intro-post ask. The new member is not posting into the void; there is a specific person likely to engage. This requires the operator to have actually told the referrer to reply to the new member’s intro — which is a two-minute DM to the referrer and compounds the referral value significantly.
Template 6 — The day-3 nudge (conditional: non-activated members only)
This is the highest-leverage template in this set. The day-3 nudge fires only to members who have not yet completed the day-0 action — posted, replied, or answered the goal-track question. Sending it to activated members damages trust; sending it to every member regardless of activation status is a mistake that makes the community feel like it is not paying attention. The conditional check is the implementation detail that separates a purpose-built onboarding tool from a scheduled reminder.
The structural difference from a reminder: a nudge reframes to a lower-effort entry point; a reminder restates the original ask. Members who did not reply on day 0 have already made a soft decision about the original ask. This template offers a different door.
Hi [Name] — a quick note three days in. You haven’t posted yet, which is really common — the channel sidebar can look overwhelming from the outside. Instead of a full intro, one question: what’s one thing you’re working on right now that you’d want a second opinion on? No need to post it publicly; you can answer me here. If it’s something where the community would have a useful take, I can help you phrase it as a thread. Takes two minutes.
Line-by-line notes:
“You haven’t posted yet, which is really common” — names the situation directly and normalises it. Operators often avoid naming non-activation because it feels like an accusation; in practice, naming it and normalising it is the move that reduces the member’s sense of social debt.
“Instead of a full intro, one question” — the reframe. The new ask is explicitly smaller than the original. The member who felt the intro post was too much to write can answer a private question with a sentence.
“No need to post it publicly; you can answer me here” — removes the public-performance aspect. For members whose barrier to posting is visibility, this is the relevant permission. The private answer can become the basis of a public post, but that is not the ask.
“I can help you phrase it as a thread. Takes two minutes” — closes with an offer and a time estimate. “I can help you phrase it” signals that the operator will do work on the member’s behalf, which shifts the dynamic from task-assignment to collaboration. The two-minute estimate sets an expectation that the next step is low-friction.
Template 7 — The month-two win-back DM (passive subscriber, pre-cancellation)
Use this for members who joined, may have activated briefly, and have not opened the workspace in 30 or more days. This is the last automated touch before a member becomes a cancellation. The goal is not to re-sell the community; it is to surface a current, specific reason to open Slack today. A generic “we miss you” DM does not provide that reason.
Hi [Name] — it’s been a while since you’ve been active in [Community], and I wanted to send a quick note before you decided whether to stick around. In the past month: [two or three specific recent things that happened, e.g., “the thread on [topic] in #advanced got 40 replies from people who all ran into the same wall you mentioned in your intro; the weekly call on [date] covered [specific thing] and the recording is in #resources; someone asked for exactly the kind of referral you could give in #hiring last week”]. Any of those useful? If the timing or focus of the community isn’t working for where you are right now, I’d rather know that than have you cancel without it being worth asking about.
Line-by-line notes:
“I wanted to send a quick note before you decided whether to stick around” — names the retention context directly rather than pretending this is a general check-in. Members who are at risk of cancelling often already know it; treating the message as a casual “hey, how are you?” reads as either oblivious or manipulative. Direct is more credible.
“In the past month: [two or three specific recent things]” — this is the load-bearing element. The operator must fill this in with real recent content. Generic claims (“there’s been a lot of great discussion”) tell the member nothing they can act on. Specific recent events give the member a reason to open the workspace today rather than at some undefined future point.
“Any of those useful?” — the ask is a question, not a re-subscription pitch. The question asks the member to evaluate whether the specific events named are relevant to them, which is a much lower-friction ask than “please stay.”
“I’d rather know that than have you cancel without it being worth asking about” — signals that cancellation is a known option and that the operator is not going to guilt-trip the member into staying. This is counterintuitive but it lowers the defensive posture that makes win-back DMs feel like sales calls. A member who was going to cancel often replies to this message because it does not ask them to do anything they did not already want to do.
What to change when adapting these templates
Change: the community’s-job sentence. This is where your community is different from every other one. The role, the problem, the peer group, the stage — those are the four variables that make the sentence specific to your community. If two of your adapted templates could plausibly be from a competitor, the job sentence is not specific enough.
Change: the payoff sentence detail. Replace the examples with your real numbers, real examples, or real member stories. “Members who post in their first week are four times more likely to renew at month three” only works if it is approximately true for your community. Made-up specifics produce a short-term lift followed by a trust deficit when members compare expectations to reality.
Do not change: the single-ask structure. The most common adaptation mistake is restoring items from the original to-do list DM. “Just one more thing” additions each cut reply rate. If you genuinely need members to do two things in week one, send two separate messages spaced two days apart, not one message with two asks.
Do not change: ending with a question. A question has a lower activation threshold than a directive. A member who would not complete a task can answer a question in thirty seconds. That answer is the foot-in-the-door for activation. Member onboarding at scale is a sequence of micro-commitments, not a single big ask delivered once.
For the full framework on what separates a welcome message system from a one-shot DM — including the three-touch sequence and what each touch should accomplish at the structural level — see what is a Slack welcome message. For a scored audit of how your current welcome sequence performs against the structural criteria, the Onboarding Health Check runs in two minutes.