Definition
What is a Slack onboarding bot?
A short definition card for paid-community operators evaluating their tool stack — what the category actually covers, what it doesn’t, and how to tell it apart from the three things people most often confuse it with.
TL;DR
A Slack onboarding bot is a Slack app that runs a short, time-released sequence on every new member of a workspace: a personalised day-0 DM that asks for one specific first action, a conditional day-3 nudge that fires only if that action is still incomplete, and a day-7 scorecard email to the operator. It is distinct from a welcome bot (single-touch greeting), from a moderation bot (content policy), and from Slack Workflow Builder (one-shot automation, no member-state branching).
What it does
- Day-0 DM. Within the hour after a new member is provisioned, a direct message lands in their Slack — addressed by name, from a handle they recognise, asking for one small action (introduce themselves in #intros, pick a goal track, subscribe to two channels) and not five.
- Day-3 conditional nudge. Three days later, the bot checks whether the member has completed the first action. If yes, it stays silent. If no, it sends one targeted message keyed to the goal track the member picked. One nudge, not three — anything more reads as spam and gets the bot muted.
- Day-7 operator scorecard. At the end of week one, the operator gets a one-page email: how many members joined, how many activated (posted at least once), how many stalled (incomplete checklist at day 7), and three names worth a personal DM. Pasteable straight into a monthly retention report.
What it does not do
- Moderation. An onboarding bot does not remove spam, enforce a code of conduct, filter profanity, or warn rule-breakers. Those are different products with different design centres — usually purpose-built moderation tools or Slack’s native admin controls.
- Community content. An onboarding bot does not draft answers to questions in-channel, run a Q&A knowledge base, or send daily digests. Those are AI-assistant or summarisation tools; bundling them into “onboarding” muddies the metric the operator is trying to move.
How it differs from a Slack welcome bot
People use the two terms interchangeably, but the difference is real and shows up in week-one activation numbers. A welcome bot is a single-touch surface: the public “Welcome @newmember!” message in #general the moment someone joins, plus maybe a one-line DM with a link to a Canvas. An onboarding bot is a multi-touch sequence with conditional logic and persistence between touches.
| Welcome bot | Onboarding bot | |
|---|---|---|
| Touches | One (greeting) | Three (day 0, day 3, day 7) |
| Operator output | None | Weekly scorecard email |
The welcome bot greets; the onboarding bot drives activation and reports on it. For the full anatomy of a welcome DM that doubles as the day-0 surface inside a real onboarding flow, see the welcome bot page.
How it differs from Slack Workflow Builder
Workflow Builder is Slack’s free, native automation surface. It fires a message on a trigger (member joins channel, button is clicked) and can collect form input. It is the right answer for the day-0 DM at sub-100 members, and a real one — do not buy a bot if Workflow Builder solves the problem. Above 100 members the differences start mattering.
| Workflow Builder | Onboarding bot | |
|---|---|---|
| Conditional branching on member state | No (every workflow fires unconditionally) | Yes (day-3 nudge fires only if checklist incomplete) |
| Persistence between touches | No (each workflow run is independent) | Yes (member ID keyed to checklist state across days) |
| Operator-facing scorecard | No (operator must assemble by hand) | Yes (day-7 one-page email) |
The honest read: Workflow Builder gets you the first touch for free; the conditional second touch and the scorecard are what you pay a bot for. The dollar value of those two depends on how much it costs the operator to lose a member who would have stayed if nudged once on day 3 — usually $50–500/mo per seat in a paid community.
Examples in production
Foothold is the purpose-built example: three touches at Day 0, Day 3, Day 7, public pricing at $49 / $99 / $199 per month, one-click Slack OAuth install, designed specifically for paid Slack communities in the 200–2,000-member range. The full onboarding sequence and the goal-track logic are walked through in the 3-touch onboarding playbook.
Donut plays in the adjacent intros-and-1:1s space — it pairs members for coffee chats and runs welcome introductions, but it does not run a member-keyed activation checklist or send the operator a week-one scorecard, so it sits closer to the engagement layer than the onboarding layer. Common Room is further afield: a cross-platform community-data tool that aggregates Slack + Discord + GitHub activity into an analytics view. It is not an onboarding bot — it does not run the day-0 DM — but operators sometimes confuse the two because both surfaces report on member behaviour. The slack onboarding bot anatomy page goes deeper on the install flow and the four jobs of a serious bot.