Slack welcome bot
Slack welcome bot: anatomy of a DM that gets new members posting
A Slack welcome bot is the first message a new member ever gets in your community. It either invites them to do one specific thing, or it gets muted along with every other notification. The difference between the two outcomes is mostly down to how the message is shaped — not which tool sends it.
TL;DR
A welcome DM that converts has three parts: name them (proves the message is not a broadcast), name the community’s job (proves you remember why they joined), and ask for one specific action (gives them somewhere to land). Skip any of the three and the DM gets read once and ignored. The template is here for free; Foothold automates the whole flow if you don’t want to wire it up yourself.
Why most Slack welcome bots fail
Walk into a paid Slack community as a new member and the welcome experience is almost always one of two shapes. The first is a generic broadcast in #general from a bot named something like @WelcomeBot or @CommunityHelper. The second is a long DM with five emoji bullets and links to seven channels. Neither converts because both treat the new member like a row in a list.
The number to watch is the share of new members who post in their first week. Operators we have spoken to in communities of 200–2,000 paid seats run that number anywhere from 18% to 55%. The 55% number does not come from a longer DM or a fancier bot — it comes from a DM that reads like a human wrote it once and a bot is now sending it on their behalf.
The three-part anatomy of a welcome DM that converts
Part 1
Name them by name — not “hey there!”
If your welcome DM opens with “Welcome to the community!”, the new member knows within half a second that you didn’t write it for them. They will scroll past it. Use the first name from the Slack profile and lean into the casualness. “Hey Priya —” is more personal than “Hello, Priya Sharma.”
Why: the first half-second is when the brain decides whether the message is for them or for everyone. Address-by-name is the cheapest signal you have.
Part 2
Name the community’s actual job — not its tagline
Don’t say “Welcome to the world’s premier community for ambitious operators.” Say what people actually do here. “You joined a Slack of ~600 SaaS founders and PM leaders. Most days, the highest-signal thread is in #peer-coaching — that’s where founders post a wedge they’re stuck on and ask three other founders what they’d do.” Two sentences, with a real channel name and a real description of what gets posted there.
Why: a new member needs to map “why I paid for this” to “what happens here.” You make that map; the bot does not get to skip it.
Part 3
Ask for ONE specific action — not a checklist of five
The welcome DM has one job: get the new member to take their first action. Not five. “Want to introduce yourself? Post one paragraph in #intros — we keep them short, and you’ll usually get 4–6 replies within the day.” Then stop. The bot can come back at day 3 with a different ask if they didn’t take this one. Stacking five asks into one DM means most readers do zero of them.
Why: choice paralysis is real and an overwhelmed new member who already feels behind on a 25-channel sidebar will pick “close this DM” over any of the five options.
A worked example
Here is a real-shape welcome DM stitched together from the three parts above. It runs about 95 words — short enough to be read on a phone, long enough to feel written.
Three things this DM does not do:
- It does not list the 25 channels in the sidebar.
- It does not mention every onboarding resource you have ever made.
- It does not end with a meeting booking link.
It asks for one thing. If the new member doesn’t take it, the welcome bot’s next job — the day-3 nudge, covered in detail in the 3-touch onboarding playbook — is to come back with a different ask, keyed to what the new member said they were here for.
Slack’s built-in welcome bot — what it gives you, and what it doesn’t
Slack’s native Workflow Builder can fire a welcome DM on team-join. It is free, takes about ten minutes to wire up, and sends a single message. For very small communities (under 50 members) where a 30-second human follow-up is realistic, that is enough. The Workflow Builder welcome message also works fine as part 1 of the three-part anatomy — you write it once, it sends every time.
What Workflow Builder does not give you:
- No conditional follow-up. The day-3 nudge needs to know whether the member posted, what goal track they picked, and what to send instead if they didn’t. Workflow Builder fires-and-forgets.
- No operator scorecard. You won’t know who activated, who stalled, or who is worth a personal DM unless you build that yourself.
- No goal-keying. The DM is the same to every new member, regardless of why they joined.
The honest 3-tier comparison of Workflow Builder, Zapier, and a purpose-built bot covers when to graduate from each.
How Foothold runs the whole flow
Foothold is a purpose-built welcome bot for paid Slack communities in the 200–2,000-member range. It runs the three-part DM at day 0, sends one goal-keyed nudge on day 3 if the member hasn’t posted, and emails the operator a one-page scorecard at day 7 listing who activated, who stalled, and who is worth a personal DM. There is a hard cap of three DMs across week one because anything above that gets the bot muted, which kills the day-3 nudge anyway.
If you only want the day-0 part, you can build the welcome DM in Workflow Builder using the template above. If you want the rest of the flow without writing a custom Slack app, that’s what Foothold is for. The deeper page on what a Slack onboarding bot actually does is at /seo/slack-onboarding-bot.