Welcome DMs
How to write a Slack community welcome DM that actually gets replies
Most paid-community operators write their welcome DM once, at launch, and treat the 6–8% response rate they get as a fixed cost. It is not. Operators who see 30–35% response rates — where roughly one in three new members posts within 48 hours of receiving the DM — are not using a different tool or spending more operator time. They write a structurally different message. This post explains what that structure is.
The three mistakes that kill response rate
The most common welcome DM in paid Slack communities follows the same pattern: a warm greeting, the community name, a brief statement of what the community does, and then a list. Introduce yourself in #intros. Pick your goals from the pinned post in #start-here. Subscribe to the relevant channels. That pattern kills response rate for three distinct reasons, each of which compounds the others.
Mistake 1 — Asking for multiple actions. A DM that ends with three asks produces the response rate of zero asks. The reader sees the list, estimates the combined effort, decides to do it when they have more time, and never returns to the thread. Every additional action beyond one cuts completion rate roughly in half. A message that ends with “please do A, B, and C” converts at roughly the same rate as a message that ends with “please do C” — because C is the hardest item, and the reader’s attention lands on the combined cost, not the individual steps.
Mistake 2 — Using a generic opener. “Welcome to [Community]! We’re so glad you’re here” reads as automated even when it is not. The problem is not warmth — warmth is not the issue — it is that the opener gives the reader no information they did not already have. They know they joined; they know the name. The fact that the operator is glad they are there is the default. A generic opener uses the highest-attention sentence in the message to say nothing, and reader attention drops before the ask arrives.
Mistake 3 — No reason to act now. A welcome DM without any timing frame is a message the reader can act on in an hour, tomorrow, or next week. For most readers, that means never. “No rush, just when you get a chance” is the phrase that most reliably ensures a DM sits unread. Week one is the activation window: after day seven, the probability of a new member who has not yet posted ever posting drops significantly. The message needs to create a reason to act today, not this week.
The anatomy of a high-converting welcome DM
Every welcome DM with a 30%+ response rate has four structural elements, always in this order. The order is not arbitrary — each element creates the precondition for the next one to land.
Name the person. Not only their Slack display name — something that acknowledges why this DM is going to them specifically. If you know what they answered on the purchase survey, use it. If you have only the display name, use that plus a specific community context: “Hi Alex — welcome to [Community].” The name itself is not the personalisation; the rest of the message is. But using the name in the opener primes the reader to expect a message about them, not about the community.
Name the community’s job for them. This is the sentence most operators skip. Before making an ask, state why this community exists for this member in one sentence, framed in terms of the outcome they are supposed to get. Not “this is a community for product managers” but “this is where product managers at Series A–B companies share the exact playbooks they used to ship their first feature from 0 to launched.” The job-for-them sentence does two things: it reminds the member why they paid, and it raises the perceived value of everything that follows it.
Ask for one specific action. One verb, one place, no options. Not “check out #intros or browse #resources” but “post a single sentence in #intros — just where you’re based and one thing you’re working on right now.” The more specific the ask, the lower the perceived effort, even if the specificity makes the task sound more defined. “Post a two-sentence intro in #intros describing your role and one thing you want to get out of this community” converts better than “check out #intros when you get a chance” because the first formulation is specific enough that the reader can picture completing it in the next five minutes.
Explain why that action matters. The payoff sentence closes the loop between the ask and the outcome. “Members who introduce themselves in #intros in their first week are four times more likely to make a connection that sticks by month two” works because it names the outcome the member joined for (connections), quantifies it (4×), and ties it to the action (introduce yourself in week one). The payoff does not need to be a statistic — an anecdote (“two of our most active members met each other through an #intros introduction last month”) works as well — but it must make the member understand why the one specific action they are being asked to do leads to a result they care about.
Before and after — three annotated examples
Example 1: The everything-DM
This is the most common pattern in paid communities at the 100–500 member range. The operator is trying to be helpful by giving the member everything they need upfront.
Before: Hi [Name]! Welcome to [Community]. We’re so glad you’re here. Here are a few things to get started: (1) Introduce yourself in #intros, (2) browse the pinned resources in #start-here, (3) subscribe to the channels relevant to your role, (4) join the weekly Thursday call if you’re free. Let us know if you have any questions!
What to cut: items 2, 3, and 4. “We’re so glad you’re here.” The phrase “Let us know if you have any questions” — it answers a question nobody asked and makes the message feel like a form letter. What remains: the name, the one ask, and the payoff sentence.
After: Hi [Name] — welcome to [Community]. The fastest way to get value here is to post a one-sentence intro in #intros: just your current role and one thing you’re trying to solve this quarter. Members who post in their first week get introduced to two or three other members by the team within 48 hours. Takes thirty seconds. Want to give it a shot?
What changed: one ask instead of four; a concrete payoff (personal introductions from the team); the question at the end invites a reply rather than assigning a task. Response rate on the “after” version in communities that made this change typically moves from 7–9% to 22–28%.
Example 2: The generic-opener DM
This pattern is common in older communities where the welcome DM has not been touched since launch. The operator knows it is generic but assumes personalising it at scale is not feasible.
Before: Welcome to [Community]! You’ve joined a great group of growth marketers. We hope you’ll find a lot of value here. Our main channels are #general, #jobs, and #resources. Feel free to introduce yourself anytime!
What to cut: “You’ve joined a great group of growth marketers” (the member already knows this). “We hope you’ll find a lot of value here” (hope is not a payoff). “Feel free to.” “Anytime.”
After: Hi [Name] — you joined [Community] at a good time. There’s a thread running in #advanced-acquisition right now on getting LinkedIn ads under $20 CPA without sacrificing lead quality — probably the most direct conversation we’ve had on that specific problem. Take a look when you have five minutes, and if you have an angle on it, jump in. That thread is the fastest way to see what the room sounds like.
What changed: instead of describing the community, the DM puts the member inside a specific conversation that matches why they joined. The ask is low-effort (“jump in if you have an angle”) rather than mandatory. This approach requires the operator to update the DM weekly with a current thread reference, which is a maintenance cost — but it is a maintenance cost that compounds, because it forces the operator to keep the DM current rather than letting it decay.
Example 3: The no-urgency DM
This pattern is common in communities run by operators who are worried about coming across as pushy. The instinct is correct; the execution is not.
Before: Hi [Name]! Glad you’re here. No rush, but when you get a chance, feel free to introduce yourself in #intros. There’s no wrong way to do it!
What to cut: “No rush.” “When you get a chance.” “There’s no wrong way to do it” — this phrase lowers the perceived stakes, which also lowers the perceived reward. Urgency and pressure are different things. Removing pressure is correct; removing urgency removes the reason to act at all.
After: Hi [Name] — the next seven days are genuinely the best time to get oriented here. The members who get the most out of [Community] are almost always the ones who post something in #intros in their first week — it doesn’t need to be long, just two sentences on what you’re working on and what you’d want to get out of the community. What’s one thing you’re focused on right now?
What changed: the timing frame (“next seven days”) gives a real reason to act now without manufacturing fake urgency. The last line asks a question rather than issuing a request — a question is easier to answer than a task, and the answer to “what are you focused on right now” can become the intro post, which the operator can offer to help the member write.
When to personalise vs. when to template
Most operators with fewer than 100 new members per month can send a fully personalised welcome DM from their own Slack handle — not a bot — within two hours of each join. At that scale, personalisation is not a nice-to-have; it is the highest-leverage action available, because a message from the operator’s personal handle converts at 50–70% reply rate, compared to 20–35% for a bot-sent message with equivalent content.
The right time to move from personalised DMs to a template is when volume makes personalisation impossible, not when it becomes inconvenient. For most communities, that threshold is somewhere between 30 and 60 new members per month. Below that, a two-hour DM window from the operator’s own handle is the correct tool.
When you do move to a template, the goal-track question is what preserves personalisation at scale. If the day-0 DM ends with a multiple-choice goal-track question — “What brought you here? (A) Breaking in / (B) Growing into senior / (C) Building something on the side / (D) Connecting with other PMs” — then the day-3 nudge can branch on the answer. The member who said “breaking in” gets a nudge about the #breaking-in channel and a thread on portfolio reviews. The member who said “building something” gets a nudge about #projects and the weekly build thread.
The template is the same; the branch makes it feel like a message written for that member specifically. That is the structural advantage of goal-track data over manual personalisation at scale — and it is why the annotated examples of good first DMs treat the goal-track question as the load-bearing element, not an optional add-on. For ready-to-use goal-keyed day-3 nudge variants you can adapt directly, the seven Slack onboarding message templates post has the full set.
What to do when there is no reply by day 3
The day-3 nudge is not a reminder. A reminder says: “Hey, just following up on my earlier message — did you get a chance to introduce yourself in #intros?” That phrasing restates the original ask and adds implicit pressure. The member who did not reply on day 0 has already made, consciously or not, a small decision that the original ask was not worth the effort right now. Restating the same ask does not change that calculus — it only makes the community feel like it is tracking whether the member completed a task.
A day-3 nudge reframes the ask to a lower-effort first step. Instead of reiterating the intro post, it offers a different entry point: “I noticed you haven’t posted yet, which is really common in the first few days — a lot of members find the sidebar overwhelming at first. Instead of a full intro, would you be up for just answering one question: what’s one thing you’re working on right now that you’d love a second opinion on?” The member does not have to write a public introduction. They can answer a private question. That answer can become the basis of an introduction the operator offers to help craft — but that is not what is being asked.
The critical implementation detail is the conditional check: the day-3 nudge should fire only to members who have not yet completed the day-0 action, and it should reference their goal-track answer if one exists. Sending a day-3 nudge to a member who already activated and posted is a bad signal — it tells them the community is not paying attention to what they do. Slack’s Workflow Builder can send a message on a schedule; it cannot check whether the member has posted and skip the send if they have. That gap — the conditional check — is what separates a purpose-built onboarding system from a scheduled message. For a full comparison of the three implementation options at each scale, what is a Slack onboarding bot walks through the capability set and the threshold at which each makes sense.
For an overview of what the full welcome-message system looks like, from first-principles definition through three-touch sequence, what is a Slack welcome message covers the category. And if you want a scored baseline for where your current DM sequence stands before you start testing changes, the Onboarding Health Check runs in two minutes and produces a 0–50 score with the top three fixes for your specific numbers.