Customer Service Scripts for Common Situations
Most customer conversations follow a handful of patterns: a late order, a refund request, a price question, a mistake you made. Customer service scripts give your team a calm, consistent starting point for each one, so nobody has to invent the right words on the spot. Here are ready-to-copy scripts for common situations, plus a simple way to build and maintain your own library.
Key takeaways
- Scripts are starting points, not word-for-word speeches. Train your team to adapt them in their own voice.
- Most good scripts follow the same shape: acknowledge, take ownership, explain, offer a next step and confirm.
- Cover your top eight to ten situations first, using real messages from your inbox and phone calls.
- Keep scripts in one shared place, give each an owner and review them whenever a policy changes.
If you have ever typed a reply to an annoyed customer, deleted it and typed it again three times, you already know why scripts help. They save time, they keep the tone friendly when you are tired, and they make sure everyone on the team gives the same answer about refunds, delivery times and policies.
Scripts also make it much easier to bring a new team member up to speed. Instead of shadowing you for weeks, they can read how you handle the ten most common situations and start answering with confidence.
One note before we start: anything here that touches refunds, consumer rights or contracts is general information, not legal advice. Consumer law varies by country and state, so check the official rules where you trade and talk to a qualified professional if you are unsure.
The shape of a good customer service script
Almost every helpful reply follows the same five beats. Once your team understands the pattern, they can handle situations you never wrote a script for.
- Acknowledge. Show you understand what happened and how it feels. "I can see your order has not arrived, and I know you were counting on it for Saturday."
- Own it. Take responsibility for helping, even if the cause was outside your control. "Let me sort this out for you."
- Explain briefly. Share what you know in plain words, without blaming a courier, a colleague or the customer.
- Offer a next step. Give a clear action and, where you can, a choice. "I can send a replacement today or refund you in full. Which would you prefer?"
- Confirm and close. Say what happens next and when. "You will get a tracking link by 5 p.m. today."
Notice what is missing: long apologies, policy quotes in the first line and phrases like "unfortunately, there is nothing we can do." Lead with help, and bring in policy only when it explains the options.
Pro tip
Write placeholders in square brackets, such as [first name], [order number] and [date], and highlight them. It makes scripts quick to personalize and stops anyone sending "Hi [first name]" by accident.
Scripts for orders and delivery
Delivery questions are often the most common messages a small shop receives. These scripts work for email, chat or phone with small changes.
Order is late
"Hi [first name], thanks for getting in touch, and I am sorry your order has not arrived yet. I have checked order [number], and it is currently [status]. I expect it to reach you by [date]. If it has not arrived by then, reply to this message and I will send a replacement or refund you, whichever you prefer."
Wrong or damaged item
"Hi [first name], I am really sorry. That is not what you should have received. Could you send a quick photo of the item and the label? As soon as I have it, I will send the right item out [today or tomorrow]. You do not need to return the incorrect one unless I let you know otherwise."
Customer wants to change an order
"Thanks for letting me know, [first name]. Your order has [not yet shipped / already shipped]. [If not shipped:] I have updated it to [change], and your new total is [amount]. [If shipped:] Once it arrives, you can return [item] and I will send [new item] as soon as it reaches us."
Scripts for refunds, returns and billing
Money conversations need extra care. Be clear about what you can offer, and make sure your scripts match your written policy and the law where your customer lives.
In the UK and EU, consumers usually have 14 days to cancel most online purchases. In the US there is no general federal right to return, so your store policy applies, and some states require the policy to be posted. Rules have exceptions, so check the official guidance for the places you sell to.
Refund request within your policy
"Hi [first name], of course. I have started your refund of [amount] for order [number]. It should show on your [card or account] within [timeframe], depending on your bank. If you would like to send the item back, here is the return address: [address]."
Refund request outside your policy
"Thanks for explaining, [first name]. Our returns window for this item is [period], and your order was placed on [date], so it falls outside it. I do want to help, though. I can offer [store credit / a repair / a discount on your next order]. Would one of those work for you?"
Billing error
"You are right, [first name], and thank you for spotting it. You were charged [amount] instead of [correct amount]. I have refunded the difference of [amount] today, and you will see it within [timeframe]. I am sorry for the mix-up."
Common mistake
Writing a script that promises less than the law gives. A line like "all sales are final" can mislead customers who have legal cancellation rights. Have your returns script checked against your published policy and local consumer rules.
Scripts for complaints, mistakes and tricky moments
These are the conversations people dread. A short script helps your team stay calm and respectful, and it keeps the focus on solving the problem.
Customer is unhappy with the service
"Thank you for telling me, [first name]. I am sorry your visit was not what you expected. I would like to understand what happened so we can put it right. Could you tell me a little more about [the issue]? Once I know, I will come back to you by [time] with what we can do."
You made a mistake
"You are right, and that was our mistake. I am sorry. Here is what I have done to fix it: [action]. I have also [changed process] so it does not happen again. Thank you for your patience while we put it right."
You need to say no
"I understand why you are asking, and I wish I could say yes. We are not able to [request] because [short, honest reason]. What I can do is [alternative]. Would that help?"
Price question or discount request
"Thanks for asking, [first name]. Our price for [service] is [amount], and it includes [what is included]. We do not discount our standard rates, but [mention any current offer, bundle or payment option]. Happy to answer any other questions before you decide."
Customer has been waiting on hold or for a reply
"Thank you for waiting, [first name], and I am sorry it took longer than it should have. I have your details in front of me now, so let us get this sorted."
For heated conversations where a customer is shouting or upset in person, scripts are only part of the answer. Train your team to stay calm, keep their own safety in mind and bring in a manager when needed.
Build and maintain your script library
A script library only works if people can find it quickly and trust that it is current. Keep it simple.
- One place. Store scripts in a shared document or a knowledge base such as Notion, Confluence, Slite or Guru. If you answer email as a team, a shared inbox such as Front, Help Scout or Missive usually lets you save reply templates. Check each tool's current features, pricing and privacy policy.
- Real examples. Pull your last 50 to 100 customer messages and group them. Your top situations become your first scripts.
- Channel versions. A phone script can be warmer and shorter. A chat reply needs short lines. An email can include links to your policy page.
- An owner and a review date for each script, so outdated promises do not linger.
AI writing tools such as ChatGPT, Claude, Gemini or Grammarly can help you draft or soften a script, but always edit the result so it sounds like your business and matches your actual policies. Do not paste customers' personal details into a tool without checking its privacy terms first.
Script library template
Copy this table into a spreadsheet or your knowledge base. The rows below are examples to show the format.
| Situation | Channel | Opening line | Key options to offer | Escalate when | Owner | Last reviewed |
|---|---|---|---|---|---|---|
| Late delivery | Email, chat | "Thanks for getting in touch, and I am sorry your order has not arrived yet." | Tracking update, replacement, refund | Second delay on same order | Alex | March |
| Refund outside policy | "Thanks for explaining. I do want to help." | Store credit, repair, discount | Customer mentions legal rights | Owner | March | |
| Service complaint | Phone | "Thank you for telling me. I would like to understand what happened." | Redo, partial refund, follow-up call | Safety issue or threat of a review campaign | Jo | February |
Hypothetical example
Imagine Leah runs an online stationery shop with two part-time helpers. Every Monday, the inbox is full of "where is my order?" messages, and each helper answers differently. Leah reviews a month of emails, writes six scripts using the five-beat pattern and saves them as reply templates in her shared inbox. She adds an "escalate when" note to each. Within a few weeks, replies go out faster, refunds are handled consistently, and the helpers stop messaging Leah for every unusual case because the scripts tell them when to.
Training your team to use scripts naturally
The goal is a conversation that sounds human, not a recording. A few habits help.
- Role-play. Spend 15 minutes at a team meeting acting out two scripts. One person plays the customer and throws in a surprise.
- Encourage personal wording. Keep the beats and the promises the same, but let people use their own phrases.
- Listen first. Remind the team that a script starts after the customer has finished explaining, not before.
- Collect new situations. Keep a running list of messages that did not fit any script, and turn repeat ones into new scripts each month.
March is a good time to refresh the library before spring sales and seasonal rushes. Review delivery times, returns windows and any promotions so every script matches what you are actually offering.
Your customer service scripts checklist
- Gather 50 to 100 recent customer messages and group them by situation
- Pick your top eight to ten situations to script first
- Write each script using acknowledge, own, explain, offer and confirm
- Add placeholders in square brackets and highlight them
- Check refund and returns scripts against your policy and local consumer rules
- Note when each situation should be escalated, and to whom
- Store everything in one shared place with an owner and a review date
- Role-play two scripts at your next team meeting
Frequently asked questions
Will scripts make my team sound robotic?
Only if people read them word for word. Treat scripts as a structure and a set of agreed promises, and encourage everyone to use their own natural phrasing around them. Role-play helps people get comfortable.
How many scripts does a small business need?
Start with eight to ten covering your most frequent situations. That usually handles most conversations. Add new ones only when the same unusual question keeps coming up.
Should I apologize if the problem was not my fault?
You can say you are sorry the customer had a bad experience without accepting blame for something you did not cause. Then focus on what you can do to help. Avoid blaming couriers, suppliers or colleagues in front of customers.
How often should I update my scripts?
Review them at least every quarter, and immediately whenever a policy, price, delivery time or product changes. An outdated script can promise something you no longer offer.
Related reading
The bottom line
Customer service scripts take the guesswork out of everyday conversations. Build them around a simple pattern of acknowledging, owning, explaining, offering and confirming, base them on real messages, and keep them in one shared place with clear owners and review dates.
Block out an hour this week to pull your recent messages and write your first five scripts. The next time the phone rings with a late order or a refund request, you and your team will know exactly how to begin.
