Every chat platform now ships some flavor of "welcome bot" — a scripted message that fires N seconds after a visitor opens the room. Done well, it makes a dead room feel alive and gives the visitor a reason to type. Done badly, it screams "we paid for a SaaS plan to fake friendliness at you".
Three rules separate the two.
Rule 1: Don't introduce yourself. Just talk.
The dead giveaway is the opening "Hi! I'm the Embedded Chat bot." The visitor instantly clocks that nothing is happening, and the first three words have already wasted the goodwill.
Better openings:
- (Storefront) "DM us if a size question doesn't get a quick answer — we usually reply within an hour."
- (Radio show) "Friday's Felt-E mix lands at 8pm UK. Drop the track you're hoping for ✨"
- (SaaS docs) "Anything not clicking? Ask here, the team checks chat every couple of hours."
Each one provides information, not a hello. The visitor reads it and knows what the chat is for.
Rule 2: Time it so the visitor doesn't see it appear
If the welcome message is on the page when the visitor lands, it reads as decoration. If it appears while the visitor is reading, it reads as someone typing. Aim for the latter.
The sweet spot:
- 10–15 seconds after page-load. Long enough that the visitor is scrolling or skimming. Short enough that they haven't given up on the page.
- For livestream pages where viewers settle in for an hour: bump to 30 seconds. They're not going anywhere.
- For storefront product pages where decision time is short: 5–8 seconds.
Rule 3: The follow-up nudge is where it earns its keep
Most welcome bots stop at one message. The pattern that actually converts is: one greeting + one nudge ~60 seconds later if the visitor hasn't typed.
The nudge:
- Must be specific. Not "let us know if you need anything". Yes "have a quick question about sizing? happy to help."
- Must be different from the greeting. Two variants of "hi, ask anything" feel robotic.
- Should reference something they could plausibly have seen. "Did you spot the sizing chart on the right?"
Full script templates
Storefront (Shopify, BigCommerce, etc.)
welcome_delay: 8 seconds
welcome: Welcome 👋 Most "does this run small?" questions
get answered here in < 10 minutes.
followup_delay: 60 seconds
followup: Trying to choose between two sizes? Drop the
second one and we'll tell you which most buyers
kept.
Live stream / radio
welcome_delay: 30 seconds
welcome: Hardcore Friday — Felt-E warms up at 8pm UK,
Fibzy headlines at 10. 🎶 What set are you
hoping for tonight?
followup_delay: 90 seconds
followup: New here? Track IDs go in chat — regulars
drop them within a minute usually.
SaaS / documentation site
welcome_delay: 12 seconds
welcome: Stuck on something in the docs? Ask here —
we check chat at the top of every hour during
weekdays.
followup_delay: 90 seconds
followup: If it's a quick fix you found yourself: post
it anyway, helps the next person who searches.
What never works
- "Hi! 👋 Welcome to [Brand Name]." — generic, identifies as bot, wastes a turn.
- "Have any questions?" — open-ended, low information, induces decision paralysis.
- Three messages in 90 seconds — feels needy.
- Welcome message that contradicts the chat (e.g. "ask any question!" on a chat with no admin online).
When the welcome bot is the wrong tool
If your chat has 20+ visitors at peak and a steady stream of new arrivals, you don't need a welcome script — the room is alive on its own. The welcome bot is for the cold-start case: a chat that's empty 30 seconds after a visitor lands.
For chats that have moments of empty + moments of busy (radio shows between sets, storefronts overnight), consider the AI chat assistant instead. It's a persona-driven bot that can carry conversation, not just kick it off. Set the daily token cap and let it cover the dead-air windows.