Chatbot Greeting Message· Conversation design
Chatbot Greeting Message — The First Turn That Sets Every Expectation (2026)
Quick answer: A chatbot greeting message is the opening line the bot shows before the user says anything. It does three jobs at once: it tells the user what the bot can actually help with, it offers a few concrete paths to start down, and it sets the tone for everything after. The greeting is the only turn the bot scripts in advance, with no intent recognition in the way, which makes it the highest-leverage sentence in the whole conversation. Get it wrong — by promising more than the bot delivers, or by asking a blank-page question with no guidance — and users either ask for things the bot cannot do or freeze and leave. Get it right and the same bot, with the same underlying capability, resolves more conversations because users start down paths it can finish.
What it is
The greeting message is the bot's first turn: the text (and often the buttons) a user sees the moment a chat window opens or they message your business on a channel like WhatsApp or Instagram. It is part of conversation design, but it is a special part, because it is the one turn that runs before the user has said a word. Everything else the bot does is a reaction to input; the greeting is pure initiative.
That distinction matters more than it sounds. Every later turn depends on the bot correctly reading what the user meant, which is fallible. The greeting depends on nothing — you write it once, it always fires, and it is identical for every visitor. So it is the most reliable lever you have over how a conversation goes. A well-built greeting does three things in a sentence or two: it scopes (here is what I can help with), it routes (here are a few good places to start), and it sets tone (this is how I talk). A weak greeting does none of them and leaves the user to guess at all three.
Why the greeting is higher-leverage than it looks
The greeting sets the expectation against which the user judges every answer that follows. Tell a user "I can help with orders, returns, and shipping" and they ask about orders, returns, and shipping — and the bot, scoped to exactly those things, handles them well. Tell the same user "Hi! Ask me anything!" and they ask about anything: warranty law, a competitor's product, whether your CEO is nice. The bot fails those not because it got worse, but because the greeting wrote a check the bot was never built to cash. Over-promising in the greeting manufactures the very failures users then blame on the bot.
The opposite failure is just as common and quieter. The blank-page greeting — "How can I help you today?" with no buttons, no examples, no scope — hands the user an empty text box and full responsibility for figuring out what to type. Many do not bother. Faced with an open prompt and no signal about what the bot understands, a meaningful share of users simply close the window, and that abandonment never shows up as a wrong answer because no question was ever asked. The greeting that offers two or three concrete starting paths consistently outperforms the open-ended one, because it converts hesitation into a click.
Greeting versus the things it gets confused with
The greeting is one of several early-conversation elements, and treating them as interchangeable produces muddled bots. The distinctions:
| Element | What it is | Where it lives |
|---|---|---|
| Greeting message | The bot's scripted first turn that scopes, routes, and sets tone | The visible opening line and buttons |
| Small-talk handling | How the bot responds to chit-chat ("how are you?") mid-conversation | Reactive turns after the greeting |
| System prompt | Standing instructions and persona the user never sees | Behind the scenes, shaping every turn |
| Quick replies | Tappable suggested answers, often used to present the greeting's paths | The UI layer of the greeting and beyond |
The two most often blurred are the greeting and the system prompt. The system prompt is the bot's private instruction sheet — its persona, rules, and scope — and the user never reads it. The greeting is the public, visible first message. They should agree (a system prompt that says "support only" paired with a greeting that says "ask me anything" is a contradiction the user will find), but they are different artifacts. The greeting is also not small-talk handling: the greeting opens the conversation on the bot's terms, while small-talk handling is how the bot reacts when the user opens with something off-script. And the greeting frequently uses quick replies to present its routing options, but the buttons are the delivery mechanism, not the greeting itself.
What separates a good greeting from a bad one
The difference between a greeting that starts conversations well and one that sabotages them comes down to a few properties, and they are properties of the writing, not the platform:
- Honest scope. The greeting should describe what the bot actually handles, in the user's words, not aspirational marketing. "I can help with orders, returns, and store hours" tells the truth; "Your AI assistant for anything" sets up failure. Scope that matches capability is the single biggest driver of whether early questions land in the bot's wheelhouse.
- Concrete routing. Offer two to four specific starting paths, ideally as quick replies, rather than a blank prompt. The paths double as a capability menu: they tell the user what is possible without making them guess.
- A clear exit on turn one. A good greeting makes it obvious that a human is reachable, so a user who needs something the bot cannot do sees the human handoff immediately instead of fighting the bot to find it.
- Tone that matches the brand and the moment. The greeting sets the register for the whole chat. A playful greeting on a billing-dispute flow reads as tone-deaf; a stiff one on a casual consumer brand reads as cold. Match the channel and the likely emotional state of the user arriving.
- Brevity. The greeting is read, not studied. One or two lines plus a few buttons beats a paragraph nobody finishes. Front-load the scope and the paths; cut the rest.
A greeting with a warm tone but no routing, or crisp routing but a scope that over-promises, will underperform a plain one that is honest and directive. Polish is not the metric; honest direction is.
How platforms handle the greeting
Most chatbot platforms expose the greeting as one of the first things you configure, though what you can do with it varies. Flow-first builders aimed at marketing and messaging, such as Manychat and SendPulse, let you script a greeting with buttons and branch each one into a flow, and they often vary the opening by entry point — an Instagram story reply can open differently from a website widget. Support-desk platforms like Intercom and Tidio tie the greeting to targeting rules, so the message can change by page, by whether the visitor is a logged-in customer, or by business hours — a greeting that promises live help at 2 p.m. and routes to a contact form at 2 a.m. Developer-grade builders such as Botpress and conversation-design tools like Voiceflow give you full control over the opening turn and its branching logic, at the cost of building it yourself.
The capability that actually matters across all of them is contextual variation: a single hard-coded greeting for every visitor in every situation is the blunt instrument. A returning customer mid-purchase, a first-time visitor on a pricing page, and someone messaging at midnight need different openings, and the platforms that let you match the greeting to the context turn one scripted sentence into the right scripted sentence. Whichever platform you use, the writing is yours, and the discipline of writing a greeting that scopes honestly and routes concretely is covered in the companion guide on designing a chatbot welcome message.
Related terms
- Conversation design — the broader craft of shaping a bot's dialogue; the greeting is its opening move.
- Quick replies — the tappable buttons a greeting uses to present its routing paths.
- Small-talk handling — how the bot reacts to off-script openers, the reactive counterpart to the scripted greeting.
- Human handoff — the exit a good greeting surfaces on turn one for users the bot cannot help.
- Intent recognition — the fallible reading of user input that the greeting, uniquely, runs before.
FAQ
What is a chatbot greeting message?
It is the bot's first turn — the opening line, and usually a few buttons, that a user sees before they type anything. Its job is to set expectations about what the bot can help with, offer concrete paths to start down, and establish the tone of the conversation. Because it runs before any intent recognition, the greeting is the one turn the bot fully controls and the most reliable lever you have over how a conversation goes.
What makes a good chatbot greeting?
Honest scope, concrete routing, and brevity. Describe what the bot actually handles in plain language, offer two to four specific starting paths as quick replies rather than a blank prompt, make a human handoff visible on turn one, and match the tone to your brand and the user's likely state. Keep it to a line or two — the greeting is read, not studied.
Why does "How can I help you today?" make a bad greeting?
Because it is a blank page. It hands the user an empty box and full responsibility for guessing what the bot understands, with no signal about scope. Faced with no guidance, a meaningful share of users close the window without asking anything, and that abandonment never registers as a wrong answer because no question was asked. A greeting that offers concrete starting paths converts that hesitation into a click.
What is the difference between a greeting message and a system prompt?
The greeting is the public, visible first message the user reads. The system prompt is the bot's private instruction sheet — its persona, rules, and scope — which the user never sees. They should agree, but they are different artifacts: a system prompt scoped to "support only" paired with a greeting that says "ask me anything" is a contradiction users will quickly expose.
Should the greeting be the same for every visitor?
Ideally not. A returning customer mid-purchase, a first-time visitor on a pricing page, and someone messaging at midnight need different openings. Most platforms let you vary the greeting by page, entry point, customer status, or business hours, and matching the opening to the context turns one scripted sentence into the right one. A single hard-coded greeting for every situation is the blunt-instrument version.
Sources
- Intercom. Documentation — Messenger, targeting, and welcome messages. intercom.com/help (verified 23 June 2026).
- Manychat. Documentation — opening messages and flow triggers. manychat.com/blog (verified 23 June 2026).
- Tidio. Documentation — chatbot triggers and welcome nodes. tidio.com/help (verified 23 June 2026).
- Chatbotscape Glossary. Conversation design. /glossary/conversation-design (verified 23 June 2026).
- Chatbotscape evaluation methodology. /methodology (continuously updated).