Definition
What is a Slack greeter bot?
A short definition card for paid-community operators who have heard the term “greeter bot” and want to know whether it is the same thing as a welcome bot, an onboarding bot, or something narrower — and whether they already have one.
TL;DR
A Slack greeter bot is an automation that sends a personalised direct message to every new member on the day they join — a single first touch, scoped to the day-0 DM. It is narrower than an onboarding bot (which also runs a conditional day-3 nudge and a day-7 operator scorecard) and more specific than the generic term “welcome bot” (which can mean a channel announcement or a DM, depending on who you ask). If you have a Workflow Builder flow that fires a DM on member-join, you already have a greeter bot.
What a Slack greeter bot does
- Sends a first-touch DM. Within minutes of a new member joining — or being provisioned in a paid community — the bot sends a direct message addressed by name. The message typically names the community’s main value (why the member paid), asks for one small action (introduce yourself in #intros, pick a goal track, or subscribe to two channels), and stops. Not five asks. One.
- May collect a goal response. Better implementations use a button or a short prompt to capture what the member is there to do — a goal track selection. That response keyed to the member is what makes the day-3 nudge conditional and useful if the flow graduates to a full onboarding sequence. A greeter bot that collects nothing is a dead end; a greeter bot that collects a goal is step one of a real activation flow.
- May post a channel greeting. Some operators pair the private DM with a public “Welcome @member!” post in #general or #intros. That channel post is sometimes called the greeter too, though strictly it is the welcome announcement — a different surface from the DM. Both can run from the same automation.
What it does not do
- Conditional follow-up. A greeter bot fires once and is done. It does not check on day 3 whether the member has taken the first action and send a different message if they haven’t. That is the day-3 nudge — the second touch of an onboarding bot — and it requires persisting the member’s state between messages, which Workflow Builder and most simple greeter automations do not do.
- Operator-facing reporting. A greeter bot does not tell the operator who activated and who stalled. At the end of week one, the operator who only has a greeter bot has to pull a Slack admin export and count manually. The day-7 scorecard that summarises who posted, who is at risk, and who is worth a personal DM is a feature of a full onboarding bot, not a greeter.
How a greeter bot differs from a Slack welcome bot
The two terms are used almost interchangeably in most Slack community conversations, and the confusion is understandable — both describe automations that run when a new member joins. The practical distinction is about the surface. A “welcome bot” can refer to either a public channel message (“Welcome @priya!” posted in #general) or a private DM. A “greeter bot” almost always refers to the private DM specifically. If you search “Slack greeter bot” you are almost always looking for the DM; if you search “Slack welcome bot” you may land on either.
| Welcome bot | Greeter bot | |
|---|---|---|
| Primary surface | Channel post or DM (ambiguous) | Private DM (specific) |
| Touches | One | One |
For the anatomy of a welcome DM that actually converts — the three-part structure that makes a new member read and respond rather than mute and move on — see the welcome bot page. The same principles apply whether you call it a welcome DM or a greeter DM.
How a greeter bot differs from a Slack onboarding bot
This is the more important distinction for operators evaluating their tool stack. A greeter bot is the day-0 DM. A Slack onboarding bot runs three touches across the first week: the day-0 DM (the greeter), a conditional day-3 nudge, and a day-7 operator scorecard. The greeter is the first touch inside an onboarding bot — a subset, not a synonym. If you only have the first touch, you have a greeter bot. If you have all three, you have an onboarding bot.
| Greeter bot | Onboarding bot | |
|---|---|---|
| Day-0 DM | Yes | Yes (first touch) |
| Conditional day-3 nudge | No | Yes (fires only if checklist incomplete) |
| Day-7 operator scorecard | No | Yes (who activated, who stalled) |
The practical question is: at what member count does adding the second and third touch pay for itself? Operators we have spoken to in communities of 200–2,000 paid seats (at $50–500/mo per member) find that a well-timed day-3 nudge recovers roughly one stalled member per 20 who join. At $150/mo average seat value, that is $1,800/year per 20 new joiners — worth the upgrade from a greeter to a full onboarding bot well before 200 members. The full definition of what an onboarding bot covers is at what is a Slack onboarding bot.
Examples and typical setups
Slack Workflow Builder is the most common greeter bot implementation. The member-joined trigger fires a DM to every new member with whatever text you write once in the workflow. It is free, takes about ten minutes to set up, and works well as a greeter for communities under roughly 100 members. Its limit is the absence of conditional logic: it fires the same message to everyone regardless of whether they took the first action, and it cannot send anything to the operator at day 7.
Donut includes a welcome-message feature that sends a DM (and optionally a channel post) when a new member joins. Its primary product is intro-pairing — matching members for coffee chats — so the greeter component is a supporting surface rather than the core. It is worth running if you already use Donut for pairings and want the day-0 DM for free without a separate tool.
Foothold runs the day-0 greeter DM as the first touch of a three-touch onboarding sequence. The greeter collects a goal-track response; that response drives the conditional day-3 nudge; and the day-7 operator scorecard uses activation state across all three touches to tell the operator who posted, who stalled, and who is worth a personal follow-up. If you want just a greeter, Workflow Builder is the right answer. If you want the greeter to feed into a conditional sequence with operator reporting, that is Foothold. The annotated examples of what makes a day-0 DM land well — greeter or full sequence — are at good first DMs to new Slack members.