Call center scripts

A call center script is a written guide for what an agent says at each point in a call. The good ones cover the moments that come up every shift: the greeting, the hold, the transfer, the complaint, the close. The best agents don’t read them out. They don’t need to.

They learn the shape of the call, then say it in their own words. A script that gets recited sounds like a script. A script that gets absorbed just sounds like someone who knows what they are doing.

Below are 40 scripts you can lift and adapt, grouped by scenario, plus the habits that make them work. Most are written with ecommerce and retail teams in mind, though the structure holds up anywhere.

What is the basic script for a call center?

Nearly every call center script runs on the same five beats:

1. Greeting. Say the company name and your own name.

2. Verification. Confirm who you are speaking to.

3. Discovery. Find out why they called.

4. Resolution. Fix it, or say plainly what happens next.

5. Close. Check they are satisfied, thank them by name.

Everything else is a variation on those five. Once an agent knows the spine of a call, they can handle one that goes sideways without freezing up.

Call center scripts best practices

Before diving into specific scripts, it's important to cover some key best practices that all agents should follow. These principles ensure that agents are not only using scripts effectively but are also engaging with customers in a way that enhances their experience.

1. Mastering the right tone

Your script's effectiveness hinges on the tone used during the call. Agents should be energized, positive, and empathetic. Encourage them to:

• Smile while speaking: Smiling can positively impact tone and mood, making the conversation feel warmer and more engaging, even over the phone.

• Be empathetic: Acknowledge the customer’s feelings and show genuine concern. Phrases like "I completely understand" or "I'm so sorry this happened" go a long way in building rapport.

2. Be concise and clear

While scripts provide a structure, situations may require agents to deviate slightly. When they do, remind them to keep their responses simple and concise to avoid overwhelming the customer with information.

3. Know your customer

With a customer-centric CX platform like Gladly, agents have access to a complete purchase and communication history at their fingertips. Train your agents to review this information before each call so they can anticipate why the customer is reaching out and identify any products involved.

4. Know when to go off script

A script is a floor, not a ceiling. Agents should step away from the wording when:

• The customer has already explained the problem and the script asks them to explain it again.

• The scripted phrase does not match the weight of what happened. "Sorry for the inconvenience" lands badly on an order that ruined someone's birthday.

• The customer is in a hurry and the script is padded.

• The customer says something the script simply does not cover.

What should not change is the structure. Agents can rewrite the words all they like. They should still verify identity, confirm the issue, and close the call properly.

Script examples for common scenarios

Opening a call with a first-time caller (the opening spiel)

Creating a welcoming experience for first-time callers sets a positive tone for the interaction.

Script examples:

• "Hi, this is [your name] from [company name]. How can I help you today?"

• "Hi, you’ve reached [name] from [company name]. How are you doing today?"

• "Thank you for calling [company name]. How can I assist you?"

Tips for first-time callers

• Collect essential information: If it's their first time, gather necessary information like their order number or contact details to create a customer history.

• Script example: "Absolutely. Before we proceed, could I please have your order number?"

• Script example: "Could you provide your name, phone number, and address to confirm the order?"

What is the best opening spiel for a call center?

A strong opening does three things in about eight seconds. It names the company so the caller knows they dialed correctly, names the agent so the call feels like a conversation with a person, and hands control straight back to the caller with an open question.

• "Thank you for calling [company name], this is [name]. How can I help you today?"

Anything longer starts costing you. Slogans, menu recaps and extended greetings all make the caller wait to say the thing they rang up to say, and it shows in your average handle time.

Acknowledging returning customers

Recognizing returning customers makes them feel valued and creates a personalized experience.

Script examples:

• "Welcome back, [Customer Name]! What can I do for you today?"

• "Hey [customer name], welcome back! How can I assist you today?"

• "Thanks for calling again, [customer name]. I see you made that purchase on [date] for a [product name], is that right?"

Handling common issues

Scripts help structure responses for issues like incorrect orders or missing products.

Script examples:

• "I'm sorry about the mix-up. Let’s see what we can do to correct your order."

• "I apologize for the inconvenience. Let’s get this sorted for you right away."

• "It seems there was a mix-up with your order. We’ll correct this immediately."

Putting a customer on hold (the hold spiel)

Nobody enjoys being put on hold. What makes it tolerable is knowing why, and roughly how long.

Script examples:

• "Sorry [customer name], let me put you on hold for a moment while I check in with the [department]."

• "I need about two minutes to pull this up. Are you okay to hold, or would you prefer I call you back?"

• "Thanks for holding, [customer name]. I’m still working on it and I need another minute or so."

Tips for encountering a hold:

• Ask before you hold rather than announcing it.

• Give a number, even a rough one. "A couple of minutes" beats "one moment please."

• Come back and check in if you go past the time you gave.

Transferring to another department (the transfer spiel)

Transferring the customer to another department is sometimes necessary, and handling this correctly is essential.

Script examples:

• "I completely understand, [customer name]. Let me put you through to my supervisor for further assistance."

• "[Department] handles this and they will sort it faster than I can. I’m going to introduce you so you do not have to start over."

• "Before I transfer you, let me take your number in case we get cut off."

Handling billing and payment information

Accurate and secure handling of billing information is critical.

Script examples:

• "To process your order, could you please provide your credit card number, CVV code, and expiration date?"

• "Can I verify your billing address and the last four digits of your card for security purposes?"

• "I'll need to confirm your payment details to complete the transaction."

Handling angry or frustrated customers

Empathy and understanding are key when dealing with angry customers.

Script examples:

• "I completely understand, [customer name]. I’d be just as upset if I were in your shoes. Let me see what happened so I can fix the problem."

• "I'm so sorry this has happened, [customer name]. Let me see what went wrong with your delivery."

• "Absolutely, [customer name]. I completely understand, and I’m here to make things right."

Following up

Not every issue can be resolved on the spot, and follow-up is essential.

Script examples:

• "We’re still working on replacing your [product name]. Can I call you back within the next hour with some options?"

• "I’ll follow up with you shortly to provide an update on this matter."

• "I’m awaiting confirmation on your request and will get back to you as soon as possible."

Ending a call and cross-selling (the closing spiel)

End calls on a positive note and, when appropriate, introduce other products.

Script examples:

• Ending: "Thanks so much for your call today. Is there anything else I can help you with, [customer name]?"

• Cross-selling: "I'm so happy we were able to find the right [product name] for you. Many of our customers also enjoy [related product]. Is that something you might be interested in?"

What are good closing lines for a call script?

A good close confirms what was agreed, gives one last opening, and uses the caller's name.

• "So your replacement goes out today and you’ll have tracking by tonight. Anything else while I have you, [name]?"

• "That’s all sorted on my end. Thanks for being patient with this one, [name]."

• "You’re all set. If anything else comes up, ask for me by name and I will pick it straight back up."

One caution. If the call has already run long, "Anything else?" is fine but "What else can I help you with today?" can talk someone into starting a second call.

Scripts for the calls nobody trains you for

Some calls fall outside what anyone can predict. These four come up constantly and are rarely written down anywhere, which means most agents improvise them badly.

Dead air and no response (the ghost call spiel)

The line connects and nobody speaks. Sometimes it’s a bad connection, sometimes an accidental dial, and sometimes it’s a customer who has walked away.

• "Hello, this is [name] with [company]. I can’t hear anything on my end. If you can hear me, could you try speaking again, or call us back at [number]?"

• "I’m still here, I am just not picking up any sound. I will stay on the line another moment in case it’s the connection."

• "I haven’t been able to hear you for the last minute, so I am going to release the line. Please do call back on [number] and we’ll pick up where we left off."

Give it a set amount of time, usually 30 to 60 seconds, and always say you are about to hang up before you do it.

When a customer swears at you (the profanity spiel)

Swearing about a situation is not the same as swearing at an agent. The first is someone venting. The second needs handling, and agents should not have to work out the wording in the moment.

• "I can hear how frustrated you are and I do want to get this fixed. I would just ask that we keep the language civil so I can concentrate on sorting it."

• "I understand you’re upset. I am not able to keep going if the language keeps up, but I am absolutely able to help if we can talk it through."

• "I will have to end the call if this keeps up, and I would much rather stay on and resolve it. What would you like to do?"

Standard practice is two warnings, then disconnect. Whatever your threshold is, write it down so every agent applies the same one.

When your systems are down (the downtime spiel)

The worst version of this call is an agent guessing. Say what you cannot do, then offer a route forward.

• "Our system is running slowly at the moment, so this may take a minute longer than usual. Thanks for bearing with me."

• "I can’t pull your account up right now because our system is down. I can take your details and call you back within [timeframe], or you’re welcome to hold while I try again."

• "We have a technical issue on our end and I don’t want to give you the wrong information. Can I take your number and call you the moment I can see your account?"

Asking a customer to take the survey (the survey spiel)

Survey response rates live or die on how this is asked. Rushed and mumbled at the end of a call gets nothing.

• "Before you go, there’s a short survey after this call about how I did today. It takes about a minute and it genuinely helps me."

• "You will hear a quick survey when we hang up. It comes straight back to my team, so I would appreciate it if you had a moment for it."

• "If you have a moment, please stay on the line for a short survey. It’s four questions about the service you had today."

Ask only after the issue is resolved. Asking a customer whose problem is still open to rate you is how you get a one.

Final thoughts on call center scripts

Scripts aren’t meant to make agents sound identical. They’re there so nobody has to invent the words for a hold, a complaint, or a transfer while a customer waits. Give your team the structure, let them find their own phrasing inside it, and revisit the wording whenever a scenario starts coming up that nothing on the list covers.