Live Chat Greeting & Routing Playbook

Use this when your live chat feels random: visitors get a generic "Hi, how can I help?" and end up in the wrong queue, or wait while a teammate figures out whether it's sales or support. Drop these greetings, the first qualifying question, and the routing rules into your chat tool (or sem.chat) so every conversation opens warm and lands in the right place. Edit the bracketed parts to match your team, your hours, and the pages you greet on.

Format
Editable doc
Length
5 sections · ~2 pages
Price
100% free
Setup
Copy or deploy

Copy the whole template, or grab a single block below.

Get started free
4.9·Free · No signup · Copy-paste ready
Connects toWebsiteWhatsAppTelegramInstagram
Support

Live Chat Greeting & Routing Playbook

Greetings by page and channel

Homepage / general: Hi, welcome to [Company]. I'm here to help with anything: pricing, setup, or a quick question. What brings you in today?

Pricing page: Hi there. Looking at plans? I can help you find the right one or answer anything about [pricing/billing]. What matters most to you?

Product or features page: Hey, glad you're checking out [Product]. Want me to point you to the right feature, or set up a quick demo with [name/team]?

Docs or support page: Hi, need a hand with something? Tell me what you're trying to do and I'll get you the steps or the right person.

Checkout / cart: Hi, anything holding you up at checkout? I can help with [payment, shipping, a discount question] right here.

WhatsApp / Telegram: Hi, thanks for messaging [Company] on [WhatsApp/Telegram]. How can I help today?

Instagram: Hey, thanks for the message on Instagram. Happy to help with [orders, products, or a question]. What's up?

The first qualifying question

Ask one open question, not five. Start with: "What brings you in today?" or "What are you trying to get done?"

If you need a quick fork, offer simple choices: "Are you (1) looking to buy or try [Product], (2) needing help with an existing account, or (3) here for something else?"

For an existing customer, capture the account fast: "Happy to help. What's the email or order number on the account?"

For a sales lead, get the use case before the budget: "Tell me a bit about what you're hoping [Product] will do for [team/company]."

Always capture a way to follow up: "In case we get cut off, what's the best email to reach you?"

Avoid dead ends: never ask a yes/no question when an open one would tell you where to route.

5 ready-to-use sections

1

Greetings by page and channel

When to use: Use these as the opening message so the greeting matches where the visitor is and which channel they came in on.

Homepage / general: Hi, welcome to [Company]. I'm here to help with anything: pricing, setup, or a quick question. What brings you in today?

Pricing page: Hi there. Looking at plans? I can help you find the right one or answer anything about [pricing/billing]. What matters most to you?

Product or features page: Hey, glad you're checking out [Product]. Want me to point you to the right feature, or set up a quick demo with [name/team]?

Docs or support page: Hi, need a hand with something? Tell me what you're trying to do and I'll get you the steps or the right person.

Checkout / cart: Hi, anything holding you up at checkout? I can help with [payment, shipping, a discount question] right here.

WhatsApp / Telegram: Hi, thanks for messaging [Company] on [WhatsApp/Telegram]. How can I help today?

Instagram: Hey, thanks for the message on Instagram. Happy to help with [orders, products, or a question]. What's up?

2

The first qualifying question

When to use: Use this right after the greeting to learn intent in one reply, so you can route without a back-and-forth.

Ask one open question, not five. Start with: "What brings you in today?" or "What are you trying to get done?"

If you need a quick fork, offer simple choices: "Are you (1) looking to buy or try [Product], (2) needing help with an existing account, or (3) here for something else?"

For an existing customer, capture the account fast: "Happy to help. What's the email or order number on the account?"

For a sales lead, get the use case before the budget: "Tell me a bit about what you're hoping [Product] will do for [team/company]."

Always capture a way to follow up: "In case we get cut off, what's the best email to reach you?"

Avoid dead ends: never ask a yes/no question when an open one would tell you where to route.

3

Routing decision list

When to use: Use this as the rule set that decides where each chat goes based on the visitor's first answer.

If they mention pricing, plans, demo, trial, "talk to sales," or buying for a team: route to Sales / [sales queue or owner].

If they mention login, bug, error, "not working," how-to, or an existing order: route to Support / [support queue].

If they mention invoice, refund, card, or "cancel my plan": route to Billing / [billing owner].

If it's outside scope (partnership, press, jobs): share the right email, [partners@company.com] / [press@company.com], and close warmly.

If they ask for a human or sound frustrated, escalate immediately to a live agent using the handoff script and pass the full transcript so they never repeat themselves.

Always capture name, email, channel, and the routing tag so the next person has full context.

When unsure, default to Support and let them reroute: a wrong-but-fast answer beats a long wait.

4

Busy and after-hours messages

When to use: Use these when no agent is free or you're outside support hours, so the visitor still feels handled.

Busy (agents online but tied up): Thanks for your patience. The team's helping other customers right now. Leave your question and email, and we'll reply within [time, e.g. a few minutes].

Busy, short wait (staffed): You're next in line. While you wait, what's the issue in a sentence? That way [name/team] can jump straight in.

After-hours: Thanks for reaching out. Our team is offline right now (hours: [days, times, time zone]). Leave your question and email and we'll get back to you first thing on [next business day].

After-hours with self-serve: We're offline at the moment, but you can likely solve this now: [link to help docs]. If not, drop your details and we'll follow up.

Holiday / closed: We're closed for [holiday] and back on [date]. Leave a message and we'll reply as soon as we're back.

Channel note: WhatsApp, Telegram, and Instagram have no live queue, so skip "next in line" there and send a plain auto-reply: "Thanks for messaging. We're offline right now and will get back to you once we're open again." Always set the expectation and stick to it.

5

Tone and handoff rules

When to use: Use this as the style guide so every greeting and routing message sounds like one warm, consistent team.

Lead with warmth, then get useful: welcome first, qualify second.

One question at a time. Don't stack three asks in a single message.

Match the visitor's energy and channel: short and casual on Instagram, WhatsApp, and Telegram, a touch more complete on email and docs.

Escalate to a human the moment they ask for one, repeat the same question twice, or sound frustrated. Don't make them work for it.

On every handoff, pass the full transcript and tags to the human so the visitor never starts over.

Set the handoff up cleanly: "I'm bringing in [name] from [team], who handles this. Here's what you told me so far so you won't repeat yourself."

Close every chat with a clear next step: a reply time, a link, or a name.

Replace the [highlighted fields] with your own details. Free to use.

Do it in sem.chat

Greet, qualify, and route every chat automatically

This playbook works best when something runs it 24/7. sem.chat's AI agent opens with the right greeting, asks the first qualifying question, and sends each visitor to the correct team based on their first answer.

  • One AI agent greets and routes across your website, WhatsApp, Telegram, and Instagram
  • After-hours and busy messages send automatically so no visitor is left waiting in silence
  • Every chat lands in the built-in CRM with name, channel, and routing tag, and handoff passes the full transcript so no one repeats themselves

How to use this template

  1. 1

    Map your pages and channels: list the pages where chat appears (home, pricing, product, docs, checkout) and your channels (website, WhatsApp, Telegram, Instagram), then paste the matching greeting into each.

  2. 2

    Fill in the brackets: set your team names, queues, hours with time zone, and follow-up emails so the routing list and after-hours messages reflect how you actually work.

  3. 3

    Wire up the routing decision list as rules or tags in your chat tool so each first answer sends the visitor to sales, support, or billing automatically.

  4. 4

    Test it like a visitor: open a chat from two or three pages, answer as a buyer and as a stuck customer, and confirm each one lands in the right place with your details captured.

Frequently asked questions

How many greeting variations do I actually need?
Start with three: a general one for the homepage, a sales-leaning one for pricing and product pages, and a support-leaning one for docs and checkout. Add channel-specific versions for WhatsApp, Telegram, and Instagram only once your traffic there is steady. More variations help only if each one changes the first question or the routing.
What's the single most important thing to get right?
The first qualifying question. One good open question tells you whether the chat is sales, support, or billing, which drives every routing rule that follows. Ask one thing, capture an email so you can follow up, and route on the answer. Everything else is polish.
Should I greet automatically or wait for the visitor?
A proactive greeting usually gets more chats started, but keep it light: one warm line, then let them lead. Set it as a configurable rule, for example greet "after [N] seconds on [page]," and avoid stacking multiple pop-ups or asking several questions before they've said a word. On high-intent pages like pricing or checkout, an offer to help tends to land well; on docs, a quieter prompt often fits better.

Power it up with sem.chat

Everything you need to put this template to work.

Put this template to work in sem.chat

Drop this template into sem.chat, put it to work across your channels, and go live the same day. Free to start, no credit card.