50 Customer Service Live Chat Scripts (Free Templates)

Your team closes a chat, and the customer never comes back. Why? Often because the reply was improvised on the spot, and it missed the one thing the customer needed to hear.

Good live chat scripts aren’t robotic. They’re guardrails. They shape the conversation without reading like a template, and they keep your team on message while still sounding human.

Here are 50 customer service live chat scripts, all free templates you can drop into your support process, plus three sample conversations that show them in action. Pick what works for your team, adapt it to your brand voice, and save it as a TextExpander Snippet so it’s always there when a chat comes in.

What are live chat scripts?

A live chat script is pre-written text that guides customer service agents through common conversations. It’s not a word-for-word monologue. It’s a framework covering the key points a support agent needs to hit without sounding scripted.

Think of it as a skeleton. The agent fills in specifics based on the actual customer and situation. A good chat script handles the hard part (what do I say first?) and leaves room for the agent’s personality to come through.

Live chat scripts sit somewhere between rigid call scripts (which feel awkward in writing) and completely improvised responses (which meander and contradict your policies). They’re customer service scripts specifically formatted for the chat channel: shorter paragraphs, faster responses, and acknowledgment that the customer is reading along in real time.

Live chat scripts vs. canned responses

The two terms get used interchangeably, but there’s a useful difference. Canned responses are complete, pre-written responses to a specific question, such as your refund policy or the steps to reset a password. An agent sends a canned response more or less as written.

A live chat script is broader. It covers how an agent opens, moves through, and closes a live chat conversation, and it often strings several shorter canned responses together. A troubleshooting script might include a greeting, a diagnostic question, a canned response with the fix, and a closing check.

Most support teams need both. Live chat canned responses keep factual answers accurate, while scripts keep the overall customer interaction on track. Together, they shape the whole customer experience, from the first greeting to the final thank-you. The templates in this guide work either way: use them as standalone replies or combine them into a full flow for your live chat agents.

If you’re creating canned responses for other channels too, see our list of canned responses for customer service.

Why customer service teams use chat scripts in 2026

Three reasons a customer service team relies on chat scripts:

• Consistency. Customers expect the same level of professionalism whether they reach one agent or another. A shared script levels the playing field and protects the customer experience.
• Speed. Agents aren’t searching for what to say. They’re thinking about how to help, which shortens the gap between reading a question and sending a reply. A shorter response time helps improve customer satisfaction, too.
• Approved language. Teams in financial services, healthcare, and SaaS often need agents to use reviewed wording for sensitive topics. Scripts make that wording easy to reuse.

That said, chat is unique. Customers see the conversation as it unfolds, and customer expectations for live chat support are different from other channels. A response that feels natural in a longer message falls flat in real-time text. Live chat interactions move fast, and every chat session needs replies that feel natural. These live chat templates are built for that rhythm.

Opening and live chat greeting examples

First impressions matter in chat. The greeting tells customers who they’re talking to and whether they’ll get real help, so greet customers by name whenever your chat tool provides it and start the conversation off on the right foot.

1. Standard greeting

Hi [Customer Name], thanks for reaching out! I’m [Agent Name] with the [Company Name] support team. How can I help you today?

2. After-hours automated greeting

Thank you for contacting [Company Name]! Our support team is offline right now. Our live chat hours are [Business Hours], and we’ll reply as soon as we’re back. Feel free to leave details about your issue, and we’ll prioritize your request.

3. Greeting with acknowledgment of wait time

Hi [Customer Name], thanks for your patience. I’m [Agent Name]. Let me dig into this for you right now.

4. VIP or premium customer greeting

Hi [Customer Name], great to see you again. As a valued customer on the [Plan Name] plan, you have priority support. What can I help you with today?

5. Proactive greeting during browsing

Hi [Customer Name]! Looks like you’ve been checking out [Key Feature]. Would you like a quick tour, or do you have a question I can answer?

6. Returning customer with a previous issue

Welcome back, [Customer Name]. I can see you chatted with us about [Previous Issue] last week. Is this about the same thing, or something new?

Information gathering scripts

Good questions save time for both sides. Ask for the details you need in one message rather than spreading them across several.

7. Standard diagnostic question

Got it. Just so I can point you in the right direction, when did you first notice this, and what were you trying to do?

8. Warranty or return eligibility check

Let me look up your purchase history. What’s your order number?

9. Multi-product issue triage

I see you have a few products with us. Is this issue happening in [Product A], [Product B], or both?

10. Request for account details

I can help with that. Can you share your username so I can look up your details?

11. Asking for a screenshot

Thanks, [Customer Name]. Would you mind sharing a screenshot of what you’re seeing? It shows me more detail than a description can, so I can spot the problem faster.

Hold and wait time scripts

Silence feels longer in a live chat session. Tell customers what you’re doing and roughly how long it will take, and check back before they wonder whether you’re still there.

12. Immediate acknowledgment, coming back

Just a moment, looking that up for you now.

13. Longer wait with context

I’m checking our system. This should only take a couple of minutes. Thanks for waiting.

14. Managing an extended wait

Still digging. This is a less common issue, but I want to get you the right answer, not a quick one.

15. Offering an alternative during the wait

While I look into this, would it help if I sent you a workaround link? You can try it in the meantime.

16. Customer waiting in the queue

Hi [Customer Name], thanks for waiting. Our live chat agents are helping a high volume of customers right now, and your estimated wait time is about [Number] minutes. You can stay in the queue, or I can have someone follow up with you later instead. Which would you prefer?

Problem resolution and troubleshooting scripts

Troubleshooting replies should be specific and short. Share troubleshooting steps one at a time and confirm it worked before moving on.

17. Known bug or outage acknowledgment

We’re aware of this technical issue, and our technical team is working on a fix right now. In the meantime, here’s a workaround: [steps].

18. Password reset walkthrough

No problem. Go to the login page, click “Forgot Password,” and enter your email. You’ll get a reset link in a few minutes. Check your spam folder if you don’t see it.

19. Basic troubleshooting step

Check your internet connection, then try refreshing the page in a private browser window. Let me know if that fixes it.

20. Offering a screen share or call

This might be faster to show than explain. Would you like me to send a quick screen share link so you can see exactly what I mean?

21. Confirming the fix worked

Awesome, [Customer Name]. Before I let you go, try it one more time on your end so we know it’s fully resolved.

22. Sharing a help center article

Here’s a direct link to our help center article that walks through this step by step: [Help Center Link]. It’s a good one to bookmark, and our help center articles cover self-service options for most account questions. Here are a few additional resources, too: [Links].

Escalation and transfer scripts

When a chat needs another person, the customer should never have to repeat themselves. Pass along the context, explain why you’re transferring, and say what happens next.

23. Routing to a specialist

I’m going to get you connected with [Specialist Name], who handles billing. They’ll have your account details and billing information and can move faster. One moment.

24. Escalation with context handoff

This one needs a second look from our technical team. I’m pulling together everything you told me and passing it along. Someone will follow up within [Timeframe].

25. Escalation for a feature request or feedback

That’s a great suggestion. I’m sending this directly to our product team. We can’t promise when it’ll happen, but they’ll review it.

26. Transferring to another department

Great question. Our [Department Name] team is the right department for this, and [Agent Name] is the best person to help, so I’m transferring you now. I’ve added a note with everything we discussed, so you won’t need to start over.

27. When the customer reached the wrong company

It sounds like this might be about an order with a different company. I don’t see it in our system, but I’m happy to help you check. Do you have an order confirmation you could look at?

Handling angry or frustrated customers

These are difficult conversations, and active listening matters more than speed. Handling angry customers starts with acknowledging the problem before solving it. Stay calm, keep a positive tone (apologetic where it’s warranted), and avoid jargon or anything that sounds like an excuse.

28. Validating frustration

I get it, [Customer Name]. This is frustrating. Let me see what I can do to fix it for you right now.

29. Apology without over-promising

I sincerely apologize for the inconvenience. That’s not the experience we want you to have. Let’s figure out what went wrong and make it right.

30. Compensation or goodwill gesture offer

As an apology for the trouble, I’m adding [credit/discount] to your account toward your next purchase. It should show up in the next few minutes.

31. When a customer threatens to leave

You’ve been a loyal customer, and I don’t want to see you go. I completely understand why you’re upset. Before you decide, can I ask what would make this right for you?

32. Responding to an out-of-policy request

I totally understand why you’re asking, and I wish I had a different answer. [Request] falls outside our [Policy Name] policy, so I’m not able to do that. Here’s what I can do instead: [Alternative Solutions]. Would one of those work for you?

Sales and pre-purchase chat scripts

Live chat isn’t only for support. Many customers reach out before they buy, and a helpful answer at that moment can make all the difference between a sale and an abandoned cart. Keep these replies informative, not pushy, and the same goes for any upsell or cross-sell.

33. Pricing question

Good question, [Customer Name]! Our pricing plans start at [Price], and you can compare everything on our pricing page: [Pricing Page Link]. Would you like help figuring out which plan is a good fit for your team?

34. Booking a demo or call

Happy to set that up. A quick call with our sales team is the best way to see [Product Name] with your own use case. Would you like to schedule a time that works for you? Here’s the booking link: [Booking Link].

35. Discount or coupon code question

Thanks for asking! We’re running [Offer Details] right now. Use code [Discount Code] at checkout, and the discount amount will show up before you confirm your order.

36. Help at checkout

I can see you’re on the checkout page. Is anything getting in the way? I’m happy to help with payment, your shipping address, or any last-minute questions.

Order, refund, and cancellation scripts

Order and account changes are some of the most common chat requests. Confirm the details, explain the timeline, and make sure the customer knows what to expect next.

37. Order status update

Thanks, [Customer Name]. I found your order details for [Order Number]. It shipped on [Date], and the latest tracking update shows it should arrive by [Delivery Date]. Here’s the tracking link: [Tracking Link].

38. Refund approved

Thanks for being a [Company Name] customer. I’ve processed a full refund of [Amount] to your original payment method. It usually takes [Number] business days to appear, depending on your bank.

39. Cancellation request

I can help with that, [Customer Name]. Before I cancel your subscription, would you mind sharing what prompted the change? If it’s something we can fix, I’d love to try. If not, I’ll take care of the cancellation right now.

Closing and follow-up scripts

A good close confirms the outcome, sets up any follow-up, and ends on a positive note. Think of it as a professional send-off that leaves the customer with a positive experience. It’s also your best moment to ask for customer feedback.

40. Standard closing with next steps

Does this sound good? I’ll send you a summary of what we talked about. Let me know if you need further assistance.

41. Upsell or cross-sell after resolution

By the way, a lot of other customers in your situation also use [Related Feature]. It might save you time. Would you like me to show you how?

42. Closing when the issue is unresolved and needs follow-up

I’m still investigating this on my end. Let me dig deeper and get back to you by [tomorrow/Friday]. Would you prefer a follow-up by email, or should I reach you here?

43. Checking satisfaction

Are we good? Do you have any further questions, or is there anything else I can help you with before I head off?

44. Asking for feedback

This is [Agent Name] signing off. Thanks for chatting with me today, [Customer Name]. You’ll see a short feedback survey when this chat closes. It takes about 30 seconds, and it helps us improve customer satisfaction. Have a great day!

Moving a live chat to email or phone

Some complex inquiries are too detailed or too urgent for a chat window. These templates help you move the conversation to the right channel without making the customer feel brushed off.

45. Suggesting email for complex issues

This one needs more detail than chat allows. Let me grab your contact information, and I’ll send over a full breakdown with screenshots.

46. Starting with chat, following up in writing

I’ve got the overview. To make sure you get all the details right, let me write this up and send it to you. You’ll have it in a few minutes.

47. Offering a phone call for urgent issues

This needs a conversation. Can I call you right now, or would later today work better?

48. Using chat to break news before a follow-up

I want you to hear this directly: your request was approved. Full details are coming to your inbox in 2 minutes.

49. Confirming preference

Got it, you prefer email follow-ups. I’ve made a note on your account.

50. Quick chat resolution with written confirmation

That’s all set on my end. I’m sending you a confirmation right now so you have it for your records.

Live chat examples: 3 sample conversations

Scripts are a starting point. Here’s what they look like when an agent adapts them in a live chat session. These live chat response examples are illustrative, and the names are made up. Use these live chat examples as models when you train new agents.

Example 1: Handling a missing feature scenario

Customer (Elena, 2:15 pm): Hi, I’m trying to bulk edit my contacts but I can’t find the option.

Agent (Marcus): Hi Elena, thanks for reaching out. Bulk editing is available, but it’s tucked under a different menu than most people expect. Let me walk you through it.

What Marcus did right: Named the customer, confirmed the feature exists (reassurance), and set expectations that it’s a UX issue, not a missing feature. Moved straight to the help instead of asking diagnostic questions Elena already answered.

Customer: Oh okay, I thought it was gone. Where is it?

Agent: Go to Contacts, then click the three-dot menu in the top right (not the row menu). From there select “Bulk Actions.” It should open a panel on the right side.

What Marcus did right: Specific steps, with visual cues (three-dot menu, panel on the right) so Elena can recognize elements as she goes. No ambiguity.

Customer: Got it! That worked. Thanks.

Agent: Awesome. Before I let you go, quick question. Was that intuitive for you, or would you have expected the option somewhere else? Just thinking about feedback for our team.

What Marcus did right: Closed the loop, confirmed the fix, and gathered feedback in a natural way. It didn’t feel like a survey.

Example 2: Handling a billing question with escalation

Customer (James, 11:42 am): I was charged twice last month. Why?

Agent (Dana): That’s not right. I’m pulling your billing history now to see what happened.

What Dana did right: Immediate validation (that’s not right). Quick acknowledgment of the action she’s taking. No defensiveness.

Customer: It’s been three days and nobody’s responded to my email.

Agent: I see the email. Let me flag this directly with our billing team. This shouldn’t take another three days. Can I get a phone number so they can reach you, or do you want me to follow up here?

What Dana did right: Acknowledged the frustration without excusing it. Took ownership (“I see the email”) and gave a direct action (flagging with billing). Offered a choice of follow-up channel.

Customer: Email is fine. How long will this take?

Agent: I’m going to make sure someone gets back to you by tomorrow at the latest. If I can spot the issue in the meantime, I’ll reach out sooner. Sound okay?

What Dana did right: Set a concrete expectation. Didn’t promise instant resolution (she doesn’t control billing’s speed) but promised a real response timeline.

Example 3: De-escalating frustration with empathy

Customer (Raj, 4:03 pm): This product is broken. I’ve wasted two hours trying to make this work.

Agent (Tom): Two hours is a lot. I’m really sorry you hit this. Let me see if I can get you back on track.

What Tom did right: Didn’t dismiss the frustration. Acknowledged the time investment specifically. Apologized without making excuses. Used “I can” language (active, problem-solving) instead of “This is a known issue” (passive).

Customer: The export feature keeps timing out.

Agent: That’s our known issue from this morning. We pushed a fix about 30 minutes ago. Are you still hitting the timeout, or did it come back?

What Tom did right: Transparency about the issue. Gave context (this morning, 30 minutes ago) so Raj knows it’s being handled. Asked a follow-up that either confirms the fix or uncovers a different problem.

Customer: I’m refreshing the page now and trying again.

Agent: Good call. It might also help to clear your browser cache while you’re at it. Sometimes that speeds up the rollout to older sessions.

What Tom did right: Suggested a proactive step while Raj is already trying a refresh. Extra context (why clear the cache) without being condescending.

Customer: It works now! Ugh, two hours wasted but at least it’s going.

Agent: I really am sorry about that. As a small apology, I’m adding a month of free service to your account. You shouldn’t have to lose that kind of time.

What Tom did right: Followed through with a real repair (credit). Didn’t overpromise or make it weird. The apology was human, not corporate.

How to build and maintain your script library

Scripts and canned responses only work if your team actually uses them. Here’s how to make that happen.

Start small and test

Don’t roll out all 50 scripts on day one. Pick the top five common scenarios your team hits every day and write canned responses for those. Run them for two weeks. Ask your agents what worked and what felt clunky. Revise. Then add five more.

Keep scripts short

Live chat responses should be short. If a reply is more than two paragraphs, it’s too long for chat. Break it into steps. Long-form explanations belong in a follow-up message or a help center article, not in the chat window.

Write in your brand voice

Your live chat responses should sound like your company, not like a generic support bot, because tone is part of your brand identity. Decide on a few tone rules (for example, contractions are fine, exclamation points are rare, no jargon) and apply them to every customer interaction. Aim for a friendly tone. Positive scripting helps too: use positive language, so “Here’s what I can do” replaces “I can’t do that.”

Make them searchable

If your team has to dig through a spreadsheet or wiki to find a script, they won’t use it. Save your live chat canned responses in a tool like TextExpander that works across platforms, so they’re one keystroke away in chat, help desk, or ticketing systems.

Review and refresh quarterly

Pull your chat logs. Look for repeated questions or scenarios your library doesn’t cover. Update templates that aren’t landing. Remove the ones nobody uses, since dead templates take up mental space. Update any reply right away when a price, policy, or process it mentions changes.

Empower agents to personalize

A script is a starting point, not a prison. Good agents will tweak it. Let them. Capture the tweaks that work and push them back to the template. Bad scripts will disappear. Good scripts will evolve.

How to personalize canned chat responses

The biggest complaint about live chat canned responses is that they sound canned. Customers want to know they’re talking to human agents, not a bot. Unhappy customers can spot a copy-and-paste reply instantly, especially when it doesn’t match what they asked. A few habits keep pre-written responses personal, so customers feel the reply was written for them:

• Use the customer’s name and specific details. A placeholder like [Customer Name] or [Order Number] is a reminder to add details that show you read the message.
• Acknowledge the customer’s issue in your own words first. One sentence that restates the problem shows you actively listen before the template does the heavy lifting.
• Leave room for a personal line. Build templates with a blank spot at the start or end where the agent adds something specific to the conversation.
• Let agents keep their own versions. A shared library covers the facts, while personal variations let each agent sound like themselves.

Fullscript’s support team takes this approach. Their trainers build shared templates but give agents room to make them their own:

“We preach personalization in all of our channels. We want it to be personal to the agent so it does not feel robotic. They have the agency to set it up in a way that works for them.”

Mikayla Cunningham, Support Trainer, Fullscript

The goal is a personalized experience at scale and a consistent customer experience: the accurate, approved parts of a reply stay consistent, and the human touch comes from the agent.

Using live chat scripts to onboard new agents

A well-organized script library doubles as training material. New live chat agents don’t have to memorize every policy or guess at the right tone. They can start with tested live chat responses and canned responses the team already knows work, then learn the reasoning behind them as they go.

A few ways to use your library during onboarding:

• Start new hires with the most common scenarios. Give them the five to ten live chat templates that cover most incoming chats, and have them practice with those first.
• Pair each script with a short note on when to use it and which company policies apply. Context helps new agents choose the right reply instead of the closest one.
• Review early chats together. Use the sample live chat examples above as a starting point, then look at where a new agent adapted a script well and where they reached for the wrong one.

Amwell’s support team builds this into training from day one:

“The very first thing agents do when managing a case is put in a TextExpander Snippet. It helps them understand what to ask and what to focus on. When we train new agents, one of the first things we do is show them TextExpander. It makes onboarding so much easier.”

Manager, Amwell

Because a shared library holds what your experienced agents already know, new agents can handle common customer contacts sooner, and experienced agents spend less time answering the same internal questions.

How TextExpander powers chat scripts

The biggest barrier to using chat scripts isn’t writing them. It’s access. Your team forgets they exist, or spends 30 seconds hunting through a folder, and decides to wing it instead.

TextExpander solves that. Your scripts and canned responses live in Snippets. Type a short abbreviation (like “;chatgreet”) and the full chat script expands right where your agent is working, in your chat tool, help desk, or ticketing system. No switching windows, no searching. It’s muscle memory after the first few uses.

Snippets can include fill-in fields, so an agent types the customer name, order number, or other details before the reply appears. Your team can organize scripts into Snippet groups by channel (live chat, email, phone), by scenario (escalation, angry customers, closing), or by department, so support, sales, and other customer-facing teams each see the scripts they need.

Queenasia Carr, a Technical Support Specialist at Apple, described it this way: “Since I work in chat support, having quick access to my case notes and email templates really speeds up my workflow.”

And when a script works well, it spreads. One agent tweaks it, saves the improvement, and the whole team gets the better version. Virta Health’s care team, which handles most member communication in chat, saved 69,000 hours with TextExpander in one year. See how teams use TextExpander for customer support.