Slack onboarding bot

Slack onboarding bot: what it does, what to look for, and one that runs in 30 seconds

A Slack onboarding bot DMs every new member when they join, walks them through a short checklist, and nudges them on day 3 if they have not posted yet. The good ones earn their place by raising the share of new members who post in week one. The bad ones add another channel of noise and get muted by the people you wanted to activate.

TL;DR

For a paid Slack community in the 200–2,000-member range, the right bot does three things and nothing else: a personalised day-0 DM with a 3-step checklist, a goal-keyed day-3 nudge if the checklist is incomplete, and a day-7 scorecard email to the operator. Foothold is that bot. One-click Slack OAuth, 14-day trial, no credit card.

What a Slack onboarding bot actually does

Every new member that joins a paid Slack community walks into the same shape of room: a sidebar of 15–25 channels, a #welcome post they read once, and 200–2,000 strangers who are mid-conversation. The drop-off shape is consistent across operators we have spoken to: roughly half of new joiners never post, and most of those quietly cancel by month six. A Slack onboarding bot is the layer that fills the gap between “they joined” and “they posted.”

A serious onboarding bot does four things:

Detects the join event. The Slack Events API fires a team_join event the moment a new member is provisioned. The bot subscribes to that event — no operator action required after install.
Sends a day-0 DM within an hour. Not from a generic @CommunityBot handle — from a name and avatar the new member recognises. The DM names them, names the community, and asks for one small action.
Tracks completion. Did they post in #intros? Did they react to a goal-track question? Did they subscribe to two channels? The bot writes those events to a database keyed on the member ID.
Acts on incomplete state at day 3. If the checklist is incomplete and the member has not posted, the bot sends one targeted nudge. One. Not three. Operators who set the cap higher are the reason new members mute the bot.

What to look for in a Slack onboarding bot

One-click Slack OAuth install, not a sales call and a custom-deployment process. If the install path needs a calendar booking, the tool is built for the enterprise tier and your paid community is not the design centre.
Personalised day-0 DM from the operator handle, not from a generic bot handle. The first DM a new member gets is the one that determines whether they engage with anything else from the bot for the rest of their life in the community.
Conditional day-3 nudge keyed to the member’s stated goal. A single “Hey, you have not posted yet” reminder works once. A goal-keyed nudge (“You said you joined to find peers in the Series A stage — here are three threads from this week worth jumping into”) works repeatedly.
Hard cap on DMs per member — ideally three across week one. Anything above three reads as spam and gets the bot muted, which means the day-7 scorecard email no longer maps onto the same member identity in the operator’s head.
One-page operator scorecard at the end of week one, not a dashboard the operator has to log in to. The four numbers that matter are: joined, activated (posted at least once), at-risk (incomplete checklist at day 7), and stalled (no Slack open after day 5).
Pricing under $200/mo for the SMB tier. A 300-member paid community charging $100/mo per seat clears $30,000/mo gross. A retention tool that takes more than 1% of gross is a hard sell.

What to avoid

A surprising number of community-tool products ship features that look like they should help and quietly hurt:

Generic “welcome bot” broadcasts in #general. They train everyone in the channel to scroll past welcome posts. The new member sees them but does not feel addressed.
Daily digest DMs to new members. An overwhelmed new member who already feels behind on a 25-channel sidebar does not need a daily summary. They need one specific action.
Gamified onboarding (badges, points, leaderboards). Works in consumer Discord communities, reads as juvenile to founders paying $200/mo for a peer network.
AI question-answering bots used as onboarding tools. An AI that drafts answers to questions in-channel is genuinely useful for dev-tool communities with Q&A bottlenecks. It is not the same product as an onboarding bot, and treating it as one leaves the silent-new-joiner problem unsolved. The honest comparison map is in the Threado vs Common Room vs Orbit comparison.

How Foothold runs the three-touch flow

Foothold does the four jobs above and stops. There is no Q&A drafting, no cross-platform identity graph, no leaderboard. Day 0: personalised DM from your handle within an hour of join, with a 3-step checklist (introduce yourself in #intros, pick a goal track, subscribe to two channels). Day 3: one goal-keyed nudge if the checklist is incomplete — conditional on the goal track the member picked, not a blanket reminder. Day 7: one-page email to the operator listing who activated, who stalled, who is worth a personal DM. That email is pasteable straight into a monthly retention report; the four-numbers-and-three-names format was designed for exactly that use.

Pricing is public — $49 / $99 / $199 per month — and the cheapest plan covers 200 active members, which is enough for a real paid community to start. The most expensive plan removes the member cap and adds Zapier webhooks. Install is one-click Slack OAuth and the trial is 14 days with no credit card.

Related: Compare Foothold to other community tools — honest, no-bashing side-by-side with Threado and Common Room. Threado vs Common Room vs Orbit for SMB paid Slack communities — the full 9-minute category map. A good first DM to a new Slack member — annotated examples.