Customer service chat scripts for the 20 situations you see most

Below are 20 customer service chat scripts for the live chat moments that come up most, grouped by where they fall in a conversation: the opening, asking for details, delays and transfers, bad news, awkward moments and the close. Each one is short enough to send as a single chat message, with a note on when to use it and what to change. Copy them, put the bracketed parts in your own words and drop the script whenever the conversation needs judgment instead.

How to use customer service chat scripts without sounding robotic

Customers can tell a pasted reply from a typed one, usually because the pasted one answers a slightly different question. Scripts work when they handle the structure of a message and leave the specifics to the person sending it. A few rules keep them sounding human:

• Change the first line every time. Use the customer's name and repeat one detail from their message, so they know it was read.
• Send one idea per message. Chat is read on phones, and three short messages land better than one long paragraph.
• Match the customer's register. Someone who writes "hey quick q" doesn't want "Dear customer". The Nielsen Norman Group's four dimensions of tone of voice (formal or casual, serious or funny, respectful or irreverent, matter-of-fact or enthusiastic) are a handy way to agree on where your team sits.
• Never send a script that asks for something the customer already gave you.
• Keep the library small and owned. One person keeps it current; anything nobody has used in three months gets deleted.

Here are the 20 situations at a glance:

Greetings and openers

1. The chat opens with a full question

"Hi [name], thanks for the detail on [their issue]. Let me check that now."

Use it when the first message already contains everything you need. Skip any greeting script that asks "How can I help?", since they've already told you. Replace [their issue] with their own words, such as "the discount code not applying at checkout".

2. The chat opens with just "hi"

"Hi [name], I'm [your name]. What can I help you with today?"

Use it when the customer is testing whether anyone is there. Keep it to one line and reply fast; the speed of this first answer decides whether they stay. If you know the page they are on, make it specific: "Hi, I'm Sam. Questions about the pricing page?"

3. A returning customer

"Hi [name], good to hear from you again. I can see our chat from [day] about [topic]. Is this about the same thing, or something new?"

Use it only when you can actually see the earlier conversation. Customers notice when "welcome back" is followed by questions they answered last week. If the earlier issue was solved, ask briefly whether it stayed solved.

4. A proactive message on a page

"Comparing plans? If you tell me roughly how many people would use it, I can point you to the one that fits."

Use it on high-intent pages like pricing or checkout, after the visitor has spent some time there. Make it about the page they are on and ask a question that is easy to answer. A generic "Can I help you?" on every page trains visitors to close the widget. Our welcome message generator drafts page-specific versions if you need a starting point.

Asking for details

5. You need an order number or account email

"I can look into that. What's the email address you used for the order? That's all I need to find it."

Ask for one identifier, not three. "That's all I need" reassures people who expect a long form. Never ask for full card numbers or passwords in chat, and say so if a customer starts typing them: "Please don't send card details here; I don't need them to help."

6. "It doesn't work"

"Sorry that's getting in your way. What happens when you try: do you see an error message, or does nothing happen at all?"

Use a question with two easy answers. It narrows the problem faster than "Can you describe the issue?", which tends to get the same three words back. Follow up with the next fork in the road, one question per message.

7. You need a screenshot

"Could you send me a screenshot of what you see? On Windows press Windows + Shift + S, on a Mac press Cmd + Shift + 4, then paste it here."

Use it when describing the screen would take longer than showing it. Including the shortcut saves a round trip with less technical customers. On mobile, swap in "a screenshot from your phone is fine too".

Delays, holds and transfers

8. You need a minute to check

"Let me check that with [the warehouse / our billing system]. Give me about two minutes and I'll be right back here."

Always name a time, and come back before it runs out, even if only to say you need one more minute. Silence in a chat window feels much longer than the same silence on hold, because there is no music telling the customer you're still there.

9. It will take longer than the chat

"This needs [our engineers / the courier] to look at it, which usually takes [time]. You don't need to keep this window open. I'll email you at [address] as soon as I hear back, and by [day] at the latest."

Use it when the answer won't arrive in the next few minutes. The important parts are the latest date and the channel. Then keep the promise, ideally from the same conversation thread so the history stays together.

10. Transferring to a colleague

"[Colleague] looks after [refunds / integrations] and can sort this properly. I've passed on everything you told me, so you won't need to repeat it. They'll reply right here in a few minutes."

Only send this if the colleague really can see the conversation, and write them an internal note with what you checked. A transfer that makes the customer start over is worse than no transfer.

11. A message arrives after hours

"Thanks for your message. Our team is offline right now and back at [time, time zone]. Leave your email and we'll reply first thing; you don't need to stay on this page."

Set it as an automatic reply outside your hours. Give a real time with a time zone rather than "soon". If you have help articles covering common questions, link the top one or two here.

Bad news and refusals

12. Saying no to a request

"I can't refund this one: it's past our [30]-day window, and I'd rather be straight with you than make you wait for a no. What I can do is [exchange it / give store credit / cancel the renewal]. Would one of those help?"

Use it for refunds, discounts or exceptions you can't make. The reason goes in the same sentence as the no, and the alternative follows immediately. If there is no alternative at all, say what you have done, such as passing the feedback on, and stop there.

13. A feature you don't have

"We don't support [feature] at the moment, and I don't have a date for it. Some customers get close with [workaround]. Want me to walk you through that?"

Avoid "not yet" unless it is actually planned. A vague hint at the roadmap turns into "you told me it was coming" six months later. If it is on the roadmap, say so plainly and offer to message them when it ships.

14. A known outage

"Yes, [feature] is down for some customers right now, and we're working on it. Your data is safe. I'll update this chat by [time], or you can follow the status page: [link]."

Confirm the problem in the first words, because the customer's real question is "is it me?" Only say data is safe if you know it is. Give an update time even when you have no fix time.

15. Your team made a mistake

"That's our mistake: we sent the wrong size. I've already booked a free collection for [day] and the right one ships today. Sorry about the hassle."

Name the mistake and the fix together. A long apology without the fix reads as stalling. If you can't fix it on the spot, say exactly when you will.

16. An angry customer

"I can see why you're annoyed. You've been waiting [time] and still don't have [the thing]. I'm going to stay on this until it's sorted. First, [the one thing you need or are doing]."

Use it for the second or third message, after you have read everything they wrote. Name the specific problem instead of saying "I understand your frustration", then move to an action. Short sentences help; long explanations read as excuses. This is also the situation where you should most often throw the script away and write from scratch.

Awkward moments

17. Abusive language

"I want to help you with this, and I will. I can't continue if the messages stay personal, though. Can we go back to [the problem]?"

Use it once, calmly, for insults or threats aimed at the agent, not for ordinary frustration or swearing at a situation. If the abuse continues, end the chat with a short note that they can write again, and tell your team lead. Agents should know they are allowed to do this.

18. A question you can't answer

"That's outside what I can advise on: it's really a question for [your accountant / your bank / your web developer]. What I can tell you is [the part you do know]."

Use it for legal, tax, medical or third-party questions where a wrong answer from you could cause harm. Give the part you are sure of and point to who can answer the rest.

Closing the chat

19. Closing a solved chat

"Great, so to recap: [what was done] and [what happens next, with a date]. If anything else comes up, reply here and it comes straight back to us. Have a good [afternoon]."

The recap catches misunderstandings while the customer is still there, and it is the line they will screenshot later. If you send a satisfaction question after the chat, keep it to one click. Our CSAT survey previewer shows how different rating styles look.

20. The customer went quiet

"Hi [name], just checking you're still there. I'll keep this open for a few more minutes. If you've had to step away, no problem: reply any time and we'll pick it up from here."

Send it once after two or three minutes of silence, then close the chat if nothing comes back. If the problem wasn't solved, add a line with where things stand so they don't have to start again.

When to go off-script

Scripts cover the predictable part of the work. Write from scratch when:

• The customer is upset on their second message. They have already seen your template once.
• The question doesn't quite match any script. A near-miss script is worse than a plain typed answer.
• Money, safety, legal or account security is involved.
• The customer has written in about the same issue before.
• The script would repeat something they just told you.

A useful test before sending: would this message make sense if the customer read it next to their own last message? If not, edit it.

How to build your own chat script library

1. Export or read your last 100 chats and tag each by situation. The top 15 to 20 situations usually cover most of the volume.
2. Write one script per situation from your best real reply, not from a blank page.
3. Read each one aloud. If it sounds like a letter, cut it down.
4. Save them as saved replies in your inbox with short names agents can search, like "refund-no" or "outage".
5. Review the list once a month. Fix anything that changed (prices, policies, product names) and delete scripts nobody uses.

For topic-specific replies beyond live chat moments, such as shipping, billing and account changes, our canned responses examples has 70 templates you can copy. The AI reply generator drafts a reply for an unusual message you'd rather not write from scratch.

Scripts are also the raw material for automation. In Sellio, the AI agent answers routine questions on website chat from your own site and documents and hands the conversation to a person when it isn't sure, which leaves agents more time for situations 12 to 18. If your chats, emails and messages arrive in different places, a shared inbox keeps saved replies and conversation history in one place, so transfers like script 10 actually work.

If you are still choosing a help desk, our Freshdesk vs Help Scout comparison looks at two common options for a small team.

FAQ

What is a customer service chat script?

A chat script is a short, pre-written message for a situation that comes up often in live chat, such as greeting a customer, asking for an order number or closing the conversation. Agents adapt it to the customer rather than sending it word for word.

Are chat scripts the same as canned responses?

They overlap. Canned responses usually answer a topic, like a refund policy or delivery times. Chat scripts tend to cover a moment in the conversation, like a transfer, a delay or a close, and they are written to be short enough for a chat window.

How long should a live chat message be?

Short enough to read on a phone without scrolling: usually one to three sentences. If an answer needs steps, send them as a numbered list or a link to a help article rather than one long block.

Should you use the customer's name in chat?

Yes, in the first message and occasionally after that. Using it in every message sounds like a sales script.

How many chat scripts does a small team need?

Most small teams do well with 15 to 30. Past that, agents stop searching the list and type from memory, and old scripts drift out of date.

Can a chatbot use these scripts?

A rule-based chatbot can use the openers and the after-hours message as they are. An AI agent works better when it learns from your help content and policies, with scripts like 10 and 17 kept for the people who take over from it.