Live chat scripts are short, pre-written replies for the moments that come up again and again: greeting a visitor, answering a pricing question, asking for details, passing a chat to a colleague, apologizing, and wrapping up. Good scripts make replies faster and more consistent without sounding robotic, because they're starting points your team adapts, not lines to paste blindly. Keep them in one shared document, write them in your brand's voice, and update them whenever the same question gets answered three different ways.
Below you'll find a simple formula, templates for sales and support, and a routine for keeping your scripts useful.
The formula behind a good chat reply
Most strong chat replies follow the same four beats:
- Acknowledge. Use the visitor's name and restate what they asked, so they know a person read it.
- Answer or ask one question. Give the answer, or ask the single question you need to answer well. Not three.
- Give the next step. Say what happens now: a link, a follow-up, a handoff, or a confirmation.
- Check in. "Does that help?" or "Anything else I can do?"
Keep each message short. Chat is read on phones and in small windows, so two or three short messages beat one long paragraph.
Where to keep your scripts
Scripts only help if the whole team uses the same ones.
- One shared document, organized by situation (openers, pricing, support, escalation, closing).
- A clear name for each script, so people can find it in seconds.
- An owner who updates scripts when prices, policies or processes change.
- Placeholders in brackets, like [name] or [plan], so nobody sends a template with the blanks still in it.
Opening scripts
When a visitor has already talked to a chatbot, your opener should prove you've read what they said. Nothing frustrates people more than answering questions for a bot and then being asked "How can I help?"
After a bot handoff, with context
Hi [name], I'm [agent] from the team. I can see you're asking about [topic] for a team of [size]. Let me help with that.
When the visitor started with a direct question
Hi [name], thanks for your question about [topic]. Give me a moment while I check that for you.
When you're joining after a short wait
Hi [name], thanks for waiting. I'm [agent], and I've read your message about [topic]. Here's what I found:
Returning customer
Welcome back, [name]! I can see we spoke about [previous topic] last time. What can I help with today?
If you're building the bot side of this, our chatbot to human handoff checklist explains how to pass context so these openers are possible.
Sales scripts
Sales chats are usually about fit, price and timing. Your scripts should answer quickly, then learn just enough to help.
Pricing question
Good question. [Plan] is [price] a month, and it includes [the two features this visitor cares about]. To point you to the right option, roughly how many people would use it?
Visitor wants a demo or a call
Happy to set that up. What's the best email to send a few time options to? And is there anything specific you'd like us to cover?
"Is this right for us?"
Let's check. What are you hoping to solve, and what are you using today? I'll tell you honestly whether we're a good fit.
Price objection
That's fair. Many teams start on [smaller plan] and move up when they need [feature]. Would it help if I outlined what you'd get on each?
Not a fit
Thanks for explaining. Based on what you've told me, we're probably not the best fit for [need], because [honest reason]. [Optional: what might help instead.]
Following up on an offline message
Hi [name], thanks for your message last night about [topic]. [Answer.] If it's easier to talk it through, just reply here and I'll pick it up.
Honest "not a fit" replies cost you nothing and save both sides time. Never promise features, discounts or dates you can't confirm.
Support scripts
Support chats are about understanding the problem fast and keeping the visitor informed.
Asking for details
Sorry you've run into that. So I can look into it properly: what were you trying to do, and what happened instead?
Asking for one specific detail
Thanks. Could you send me [the one thing you need, such as the email on your account or the page you were on]?
You need time to check
Thanks, that's clear. I'm checking this now and will be back within [realistic time]. You don't need to stay on this page; if you leave, I'll follow up by email.
Giving step-by-step help
Here's how to fix it:
- [Step one]
- [Step two]
- [Step three] Let me know which step you get stuck on, if any.
Passing to a colleague
This one's best handled by [colleague or team], who knows [area] in depth. I've passed on everything you've told me, so you won't need to repeat it. They'll reply [here / by email] within [time].
You can't solve it in chat
I can't fix this from here, but I don't want to leave you without an answer. I've noted the details and [who] will follow up by email by [time].
Scripts for difficult moments
These are the moments where a script helps most, because they're stressful to write on the spot.
Frustrated customer
I'm sorry, that sounds really frustrating, especially when [their situation]. Let's sort it out. Here's what I'll do right now: [action].
Mistake on your side
You're right, that was our mistake, and I'm sorry. Here's how we'll fix it: [fix]. I'll confirm once it's done.
Refund or exception request
I understand. Our policy is [policy, stated plainly]. [If you can't decide:] I'll pass your request to [person] who can review it, and they'll reply by [time].
Off-topic or inappropriate message
I can only help with questions about [business] here. Is there anything about [product or service] I can help with?
Don't argue, don't blame the visitor, and don't over-apologize in every message. One sincere apology and a clear fix land better than five sorries.
Closing scripts
A good close confirms the outcome and leaves the door open.
Resolved
Glad that's sorted! Anything else I can help with today?
Final close
Thanks for chatting, [name]. If anything else comes up, just open the chat again. Have a great [day / evening].
Waiting on something
To recap: [what you'll do] by [when]. I'll follow up at [email]. Thanks for your patience.
Common script mistakes
| Mistake | Why it hurts | Fix |
|---|---|---|
| Pasting without editing | Feels robotic, sometimes answers the wrong question | Personalize the first line every time |
| Asking for details the bot already collected | Visitor repeats themselves | Read the collected answers before replying |
| Long paragraphs | Hard to read in a small window | Two or three short messages |
| Vague timing ("soon") | Erodes trust | Give a realistic time or window |
| Leaving placeholders in | Looks careless | Use obvious [brackets] and reread before sending |
| Promising what you can't confirm | Creates bigger problems later | Say what you'll check and when you'll reply |
Keep your scripts fresh
Scripts age quickly. A light monthly routine keeps them useful:
- Read a sample of recent chats. Where did agents improvise the same answer? Turn it into a script.
- Retire scripts nobody uses, or that customers seem to misunderstand.
- Move repeat answers upstream. If one script gets used constantly, the answer may belong in your chatbot greeting, an FAQ page or your AI assistant's knowledge base, so visitors get it instantly.
- Update the same day prices or policies change.
For the bot side of the conversation, our chatbot welcome message examples cover the greetings visitors see before a person joins.
How to do this in RetroChat
RetroChat's shared inbox gives agents the context these scripts rely on. When a chat is handed off, the agent sees everything the chatbot collected next to the conversation, plus the contact's past conversations, so context-aware openers are easy. A typing preview shows what the visitor is writing before they send it, which gives you a head start on the right reply. On Team plans and above, private notes let you leave internal context for a colleague, and assignment shows who's handling each chat. See Inbox and team for the details.
Greeting-level scripts can live in your chatbot flow itself, with saved answers inserted as {{variable}}. On the Autopilot plan, Suggest reply drafts an answer from your knowledge base and the conversation so far; agents review it and send it, or edit it first. If you're still setting chat up, start with our guide to adding live chat to your website.
Give your team a head start
Write ten scripts for your most common situations this week, keep them in one shared document, and review them monthly. You can put them to work in a free 14-day RetroChat trial, no credit card required.
Frequently asked questions
What is a live chat script?
It's a pre-written reply for a situation that comes up often in chat, such as greeting a visitor, answering a pricing question or apologizing for a mistake. Agents use it as a starting point and personalize it, so replies are faster and more consistent.
Do live chat scripts make support sound robotic?
Only if agents paste them without editing. Personalize the first line, use the visitor's name and details, and keep the language natural. Scripts should handle the structure so agents can focus on the person.
How many live chat scripts does a small team need?
Start with ten to fifteen covering your most frequent situations: openers, pricing, common support issues, escalation, apologies and closings. Add new ones only when you notice agents writing the same answer repeatedly.
Should a chatbot use the same scripts as agents?
The tone should match, but the job is different. A chatbot handles greetings, routing and simple, predictable answers, while agent scripts cover judgment calls. When a script is used constantly for the same simple question, consider moving that answer into the bot.