Customer Service Scripts: 40 Examples Agents Actually Use, by Scenario

Most lists of customer service scripts run alphabetically or by channel, but agents do not work that way. An agent works in moments: the greeting, the verification, the pause while a system loads, the caller who has already repeated the problem twice and is bracing to do it a third time, and the last ten seconds where a good call can still turn bad. So this guide follows those moments. It holds forty scripts you can drop into a knowledge base today, and four full conversations that show how the pieces fit together.

One warning before the list. A script is a floor, not a ceiling. It stops a new agent from freezing and stops two agents in two cities from giving two different answers. It does not replace judgment, and a customer can hear the difference between a person reading and a person talking. The last section covers how to keep the floor without hitting the ceiling.

What customer service scripts are for

A customer service script is a prepared line, or a short sequence of lines, for a predictable point in a conversation. The predictable points are the reason scripts work. Every call opens, most calls need identity verification, many need a hold, and a fair share end with an unhappy customer. Those moments repeat thousands of times a week, so it makes sense to get the words right once.

Customer service scripts earn their place in four ways. They cut the silence while a new agent decides what to say. Brand tone stays consistent across shifts and sites. Compliance language, such as recording disclosures and payment verification, comes out the same way every time. And they give a nervous agent something to hold on to when a caller is angry.

Scripts fail when agents use them as a wall. If the customer asks something the script did not anticipate and the agent reads the next line anyway, the call gets longer and the customer gets angrier. That is why the strongest teams deliver scripts inside a customer service knowledge base, next to the procedure each script belongs to, rather than on a printed sheet.

Which customer service scripts you need, by moment

Match the script to the moment, then to the channel. The table shows where each group below belongs and the tone that fits it.

40 customer service scripts, grouped by moment

Replace the bracketed words with your own. These customer service scripts are meant for the ear, which is why every one of them is short, uses contractions, and avoids the kind of policy language that a customer hears as a wall going up between them and the person who is supposed to be helping. If a line feels stiff when you read it out, shorten it.

Opening and greeting

1. Thank you for calling [Company]. This is [Agent]. What can I do for you today?
2. Hello, welcome to [Company]. I am [Agent], and I’ll be helping you. So, what’s going on?
3. Good [morning/afternoon], [Customer]. I can see you’re calling about your [product], so tell me if that’s right or if it’s something else.
4. Welcome back, [Customer]. I have your last conversation in front of me, so you won’t need to explain it again. Where should we pick up?
5. Hi [Customer], thanks for reaching out on chat. I am [Agent]. I will stay with you until we fix this.

Verification and compliance

1. Before I open the account, I need to confirm two details for your security. Could you tell me the phone number and the postal code on the account?
2. This call may be recorded for quality and training. If you’d prefer it not be, tell me now and I’ll make a note.
3. For your protection, I can’t read the full card number back to you. If you give me the last four digits, I’ll match them against the payment.
4. I have verified the account, thank you. Everything from here is on the record for you.

Hold and transfer

1. I’d like to check that with our billing team. It should take under two minutes. Are you okay to hold, or would you rather I call you back?
2. Thanks for waiting. I am still checking, and I’ll be with you in about a minute.
3. The fastest way to fix this is our [team] team. I will transfer you now, and I’ll pass on everything you’ve told me so you don’t repeat it.
4. Good news, I have an answer for you.

Billing and payments

1. I can see the charge you’re describing. Let me walk you through what it covers before we decide what to do about it.
2. You’re right, that amount doesn’t match the quote we gave you. I am going to correct it now and you’ll see the adjustment within [timeframe].
3. The payment didn’t go through on [date]. It’s usually the bank declining rather than us, so let’s try once more, and if it fails again I’ll give you another option.
4. I have applied the credit. Your next bill will show [amount], and I’m sending a confirmation to your email while we’re talking.
5. I understand you want this refunded. Our policy covers [condition], and your case meets it, so I’m processing the refund now.

Troubleshooting

1. I am going to ask a few questions first so we fix the right thing. When did this start, and did anything change around that time?
2. Tell me if there’s a message or a code on the screen, and read it to me exactly as it appears, punctuation and all.
3. Let’s try the most common fix first. Turn the [device] off, wait ten seconds, and turn it back on. I will stay on while you do that.
4. That rules out the [component]. The next step is to check [setting], and I will tell you where to find it.
5. I can send the steps to your email so you have them in writing. I will stay on the line while you follow them.
6. This one needs a technician. I can book a visit for [date], and there’s no charge because it’s a fault on our side.
7. That did it. Before you go, I’ll note what fixed it on your account, so if it ever happens again the next agent knows.

Orders and delivery

1. Your order should have arrived by [date] and it hasn’t. That’s on us to sort, so let me find where it is.
2. I can see the wrong item was sent. I am dispatching the right one today, and I’ll email you a prepaid label for the return.
3. That product should never have reached you damaged. Could you send a photo to [address]? As soon as it lands, I’ll ship a replacement.
4. The tracking shows it’s delayed at [location]. I will flag it with the carrier now and you’ll get an update from me by [time].

Angry customers

1. You’ve explained this twice already, and that’s not good enough from us. I have got the full picture now, so you won’t have to say it a third time.
2. I can hear how frustrating this has been. Let me tell you exactly what I’m going to do, and then I’ll do it while you’re on the line.
3. You’re right to be annoyed about that. Here’s what I can do today, and here’s what I can’t, so there are no surprises.
4. I am not going to read you a policy. I am going to fix the part I can fix, which is [action], and escalate the part I can’t.
5. If it helps, I’ll give you my name and a direct reference number, so if you have to call again you won’t start from zero.
6. I have done [action]. I will call you back at [time] tomorrow to confirm it held, whether or not you hear from anyone else.

Closing

1. To confirm, we’ve [summary]. Is there anything I’ve missed?
2. Is there anything else I can help with while I have your account open?
3. You’ll get a confirmation email in the next few minutes. If it isn’t there in an hour, check spam, and if it’s still missing, reply to any of our emails and it’ll reach me.
4. Thanks for your patience with this, [Customer]. I am glad we fixed it.
5. Have a good rest of your day, and thanks for being with [Company].

Four complete sample conversations

Individual lines are useful, but seeing them strung together is what teaches a new agent the rhythm of a call, where the acknowledgment comes before the fix and the confirmation comes before the goodbye, so here are four short calls built entirely from the scripts above.

Late delivery, angry caller. The agent opens with script 1, listens without interrupting, then uses 30 to acknowledge the repeated explanation. Line 26 takes ownership, 29 gives a concrete next update, and 34 offers a reference number before the close with 36 and 39. Total talk time was under four minutes.

Duplicate charge. The agent verifies identity with 6, explains what the charge covers with 14 before promising anything, then corrects it with 15 and confirms the new amount in writing with 17. Closing with 37 catches a second question the customer had forgotten, which avoids a repeat call.

Router not connecting. Line 19 gathers the timeline, 20 gets the exact error, 21 tries the reboot, 22 checks the setting, and 25 notes the fix on the account. If step 22 fails, the agent moves to 24 and books the technician instead of trying a sixth thing.

Account locked, customer in a hurry. The chat opens with 5, then 6 verifies, 23 sends the reset steps by email, and 38 explains what to do if the email does not arrive. No hold, no transfer, one contact.

How to use customer service scripts without sounding robotic

Customers rarely object to scripts. They object to an agent reading at them. The difference lies in how the agent delivers the line and where the line lives.

Write for the ear, not the page. Speak every line aloud before it goes live, and cut anything over twenty words in two. Contractions stay in.

Cover the moment, not the whole call. Give agents an opener, a verification block, and a closer, then let the middle follow the procedure. Fully scripted calls run long and sound worse.

Put the script next to the procedure. If the billing correction script sits in the same guided flow as the billing steps, the agent sees it at the right moment. If it sits in a separate document, they skip it or read it late. An interactive decision tree is the natural home, because each branch can carry the line that fits it.

Give permission to deviate. Tell agents which lines are mandatory, usually compliance, and which are suggestions. Agents who know the difference stop reading the suggestions word for word.

Pair scripts with empathy that is specific. “I understand your frustration” read from a card is worse than silence. A short library of empathy statements helps, but the rule is to name the actual thing that went wrong, as script 30 does.

Measure what the script changes. Track average handle time and repeat contacts by call type before and after a script goes in. If a script lengthens calls, rewrite it or remove it.

Where customer service scripts live in a modern contact center

Printed sheets are gone. The question now is whether a script sits in a document the agent has to search for, or inside the workflow they already follow.

The trend is clear. Gartner predicted that 73% of customer service organizations would have agent assist in place by the end of 2025. Its August 2025 survey of 265 service leaders also found live chat, self-service portals and knowledge management systems becoming the essential tools for scalable support. Agent assist is where customer service scripts now surface, because the tool reads the conversation and shows the line that fits.

That only works if the content behind it is current. In a Gartner survey of 321 leaders published in February 2026, 58% said they aim to upskill agents into knowledge management specialists. The reason is that AI and self-service both depend on accurate, maintained content. A script library with no owner goes stale in a quarter, and a stale script delivered by AI is stale at scale, because the same wrong line now reaches every agent on every call instead of the one agent who happened to open the old document.

So the practical setup is simple. Store the forty customer service scripts above as reusable snippets in your knowledge platform, and attach each one to the procedure it supports. Assign an owner per group and review quarterly, then let AI call center software surface the right line during the call rather than asking the agent to remember it.

If you want a head start, the ready-made script templates pack loads the first set in an afternoon.

Frequently asked questions about customer service scripts