Call center scripts and spiels: 7 examples for clear, consistent calls

Call center scripts give agents a consistent starting point they can personalize for each caller. Use greeting, hold, angry-customer, insurance, and closing script examples, plus 10 best practices for writing effective scripts.

Contact center agent on a call while a ;xferwarm Snippet fills call center scripts with a warm transfer handoff and the caller’s issue

Call center scripts give customer service agents ready-to-say wording for the moments every call shares, from the first greeting to the final goodbye. Many teams call these short passages spiels. 

The best ones are built for one specific moment: a warm handoff, a line with no audio, a billing review that’s still open. Below are 7 call center spiels, one for each moment, written to sound natural out loud and to promise only what your team can deliver.

Key takeaways

  • A spiel is a building block, not a full script. Pick the one that fits the moment of the call, fill in real details, and leave out anything that doesn’t apply.
  • Warm and direct transfers need different wording. Only say you’ve briefed the next agent when you have.
  • A recap confirms the outcome before the goodbye. State what’s done, what’s still open, and who owns the next step, then let the caller correct anything.
  • Survey and closing spiels should match how your phone system works. If the survey starts after the agent hangs up, tell the caller to stay on the line.

Start with what a spiel is, and how it differs from the scripts you may already have.

Call center scripts and spiels at a glance

A call center spiel is a short, reusable passage for one moment in a customer service call. An opening starts the conversation, a recap confirms the outcome, and a closing ends the exchange. A full call center script strings those moments together across the entire interaction. The same approach works for sales calls and contact centers of any size, but these examples are written for support.

Spiel usually means a rehearsed speech. For phone support, keep the preparation but leave room for a real conversation. The seven examples below are separate building blocks, not a script to read from start to finish. Choose the version that fits, replace the bracketed fields with accurate details, and leave out anything that doesn’t apply. Listen to the caller before you choose the next passage.

These spiels cover the moments of a call. For situations like complaints, billing disputes, a refund request, technical issues, or escalations, see our customer service call scripts. If your team also answers chat, these live chat scripts are created for the written channel.

Call center spiels mapped to the moments of a call: opening, then listen and solve, an optional transfer, recap, survey, and closing, with a ghost call branch if there's no audio

What makes an effective call center script

An effective call center script sounds natural out loud and describes actions your team can actually take. ICMI’s tips for contact center scripts recommend writing the way you speak, in short chunks, and not making promises you can’t keep.

Check each spiel against these key components of a great call center script:

  • Call-stage fit: Use a transfer spiel for a handoff, a recap for the outcome, and a closing for the goodbye. Each has a separate job.
  • Spoken clarity: Read the wording aloud. Split any sentence that needs an extra breath or sounds like a policy document.
  • Accurate expectations: Promise an introduction, update, or callback only when that action is arranged, so you set customer expectations you can meet.
  • Relevant personalization: Add the caller’s name, the customer’s issue, and the right department, so it’s a personalized interaction rather than a template. Don’t imply familiarity you don’t have.
  • Room to listen: Stop when the caller responds. A good opening loses its value if you keep reading over the answer.
  • One core message: Each spiel does one job. If it’s carrying two, split it into two.

Keep required wording, like a recording notice or compliance scripts for verification, intact, and adapt the conversation around it to the caller.

1. Opening spiels that establish context

An opening spiel is a professional greeting that names the company and the agent, then gives the caller a clear place to start. First-time callers and new customers need an invitation to explain. A returning caller whose issue is already in your notes or CRM systems needs to hear that you have the context.

First-contact opening

“Thank you for calling [Company]. My name is [Agent name]. What can I help you with today?”

Say the company name and your own name clearly, since the first few seconds set the tone for the whole call. Then pause after the question. Don’t add questions about the account, order, and reason for calling before the caller has answered.

Opening when the issue is already known

“Hello, [Caller name]. My name is [Agent name] with [Company]. I have the notes about your delivery going to the wrong address. What’s happened since you last spoke with us?”

Use this version only when you have the notes and have read them. If you can see only a broad category, acknowledge just that much: “I can see your call is about a delivery. What’s happening with it?”

Keep the opening separate from verifying the customer’s identity and from any troubleshooting support you give later. Ask for account details only after the caller explains why they’re calling, and say why you need them, such as “for security purposes.” Once the caller responds, move into the questions their request requires. Personalization should save the caller from retelling the story. A name alone, without the issue details you can see, doesn’t do that. Callers notice the difference, especially now that so many first replies come from bots. At Jane, Amy-Lynn Taylor put it this way:

In this world of AI, it’s more important than ever that when our customers reach out to us, whether that’s on the phone or by chat, they know that they’re talking to actual people. We are an actual team of real, living human beings. And I wanted to make sure that even when we introduce an efficiency tool, that we’re holding onto that authenticity.

Amy-Lynn Taylor, Customer Insights and Enablement Expert, Jane

2. Ghost call spiels for when you can’t hear the caller

A ghost call spiel checks for a response when a call seems connected but you can’t hear anyone. The wording should describe the missing audio without assuming the caller has left.

Silence alone doesn’t tell you which end has the problem. Amazon Connect’s audio troubleshooting guide notes that dead air and one-way audio can start anywhere along the call path, so the caller may be talking even though you can’t hear them.

First response check

“Hello, you’re connected to [Company]. My name is [Agent name]. I can’t hear a response. Can you hear me?”

Wait a few moments, or as long as your team’s procedure says.

Ending the call when there’s still no response

“I still can’t hear a response, so I’ll end this call now. Please call [support number] if you still need help.”

Use the ending only when your procedure allows you to disconnect. There’s no universal number of warnings or waiting time that fits every phone system.

Keep planned pauses separate from ghost calls. If you’re looking something up, say so: “I’m checking the tracking details for your order. I’ll let you know what I find.” The caller then knows why you’ve gone quiet. Ghost call wording is for an unexplained silence, not a lookup you’re doing yourself.

3. Warm transfer spiels that keep the context

Transfer only after you’ve confirmed the issue and tried to resolve it. A warm transfer spiel explains where the call is going and prepares the caller for an introduction to the next agent. Amazon Connect’s documentation describes a warm transfer as putting the caller on hold while the agent introduces them to the next person, and a cold transfer as one with no introduction or shared context.

Repeating information is a common pain point. In Zendesk’s CX Trends 2026 research, 74% of consumers surveyed in 22 countries said they’re frustrated when they have to repeat information. A warm transfer exists to prevent that, so use two passages: one before you contact the receiving agent, and one when you introduce the caller.

Before you contact the next agent

“Our billing team handles duplicate-charge reviews. May I place you on hold while I contact them and explain what we’ve checked?”

Wait for the caller’s answer before you act. Don’t promise an immediate connection unless you know someone is available.

When the receiving agent joins

“[Receiving agent name], I have [Caller name] with me. They’re calling about two charges for the same order. We’ve checked the order number and both transaction dates. [Caller name], [Receiving agent name] will take it from here.”

The introduction should carry the useful context: the request, the checks already done, and what’s still needed. That’s enough for the next agent to pick up the customer’s concerns without asking for all the details again. Skip the full retelling. And if you can’t reach a colleague, switch to direct transfer wording instead of describing a warm handoff that didn’t happen.

4. Direct transfer spiels that set expectations

A direct transfer spiel explains where the call is going and why, without suggesting the next agent has been briefed. Use it when you transfer without speaking to the receiving team first.

Direct transfer wording

“Our billing team handles questions about duplicate charges. I’ll transfer you to that team now. Please have your order number ready for the next agent.”

Replace the last sentence with what the receiving team actually needs, or leave it out if you don’t know. If callers need a clearer picture of the handoff, add: “I’m transferring you directly, so I haven’t spoken with the next agent about your request.”

Keep it brief. The caller needs the destination and the reason, not a tour of your phone system. Avoid promising that they won’t need to repeat anything. Without a briefing, that may not be true, which is exactly why warm and direct transfers need separate wording.

Warm transfer vs. direct transfer spiels compared: when to introduce the caller, what to share, and what not to promise

5. Recap spiels that confirm the outcome

A recap spiel confirms what happened, what’s still open, and what comes next. Call Centre Helper recommends wrapping up a call by recapping the key points and explaining exactly what will happen next. A completed password reset and a submitted billing review need different summaries.

Recap when the action is complete

“To recap, we’ve reset your password, and you’ve confirmed you can sign in. Your account is accessible again. Is that what you’re seeing?”

The question checks the outcome instead of assuming that finishing your task solved the caller’s problem. It’s also the moment to confirm first call resolution.

Recap when the action is still pending

“To recap, I’ve submitted the duplicate-charge details to billing for review. The review is still pending. [Responsible team] will update you by [agreed channel] by [agreed time]. Your reference number is [reference number].”

Include an owner, channel, or deadline only when it’s confirmed. If the update will be a follow-up call, give the day and the number it will come from. If no update time has been set, say so: “The review is still pending, and there isn’t a confirmed update time yet. Your reference number is [reference number].”

Keep the summary to the result and the next action; you don’t need to repeat every troubleshooting step. Give the caller a chance to correct you. A recap is where you find out they expected a refund when you only submitted a review. The same summary also gives you a head start on your after-call work notes.

TextExpander banner: every call spiel, one shortcut away, with a ;recap chip and a button to see how support teams use it

6. Customer satisfaction survey spiels that invite honest customer feedback

A survey spiel, sometimes called a CSAT spiel, invites feedback without steering the caller toward a rating. The instructions should match the survey the caller will actually get. Survey results are often used to measure customer satisfaction and evaluate agent performance, so wording that nudges the score skews both.

The AAPOR Code of Professional Ethics and Practices treats participation as voluntary and warns against language that pushes respondents toward an answer. In practice, ask for honest feedback and never ask for a high score.

Invitation for a post-call voice survey

“If you’d like to share feedback about today’s call, please stay on the line after I disconnect. It’s up to you whether or not to take part.”

Use this only when the caller really does stay connected after you leave. Amazon Connect’s disconnect flow works this way: the agent hangs up, and the caller who’s still on the line goes into the survey. Telling that caller to hang up would stop them from taking part.

Don’t describe the survey as anonymous, promise how long it takes, or name a channel unless those details are set. Give the invitation after the caller’s questions are answered, so it never feels like a condition of getting help. Read the results alongside first call resolution, since a caller who had to call back may be rating the whole problem, not just this call.

7. Closing spiels that match the outcome

A closing spiel offers any final help and ends the call on a positive note without overstating the result. Keep it separate from the recap, so the caller can tell the outcome from the goodbye.

Closing when the issue is resolved

“Is there anything else I can help you with today?” Then, if the caller needs nothing more: “I’m glad you’re able to sign in again, [Caller name]. Thank you for calling [Company]. Goodbye.”

Closing when an action is pending

“Do you have any other questions about the review or the next step?” After answering them: “Thank you for speaking with me, [Caller name]. The billing review remains open. Goodbye.”

Tie the goodbye to the actual result, and use account-access language only after the caller has confirmed access. Offer further assistance once, then close; a specific, warm goodbye reinforces the customer relationship. Keep it short when the recap has already covered ownership and timing. If a voice survey follows, give the stay-on-the-line instruction before you leave, and don’t add a conflicting instruction to hang up. For more wording, see these call closing scripts.

More call center script examples for different scenarios

The seven spiels cover the moments every call shares. In a specific situation, adapt the spiel rather than reaching for a new script, as these call center script examples show. For a full library of situation scripts, from damaged orders to escalations, see our customer service call scripts, and these call flow scripts show how the stages connect.

Customer complaints and angry customers

Handling customer complaints changes the opening spiel: acknowledge the caller’s feelings before the fix, so an upset caller keeps working with you. Use customer-centric language that names the problem and what you’ll do about it:

“I can hear how frustrating this has been, and I’m sorry we got it wrong. Let me look at your account now so we can fix it on this call.”

With angry customers, lead with one specific line from our empathy statements for customer service, then move to the fix.

Billing inquiries

Billing inquiries often need relevant information from the account before you can answer. Ask only for what you need, and say why:

“To find that charge, could you confirm the account number and the date it appeared? I’ll check it while you’re on the line.”

If the question needs the billing department, use the warm or direct transfer spiel above, and say which one you’re doing. If the lookup takes more than a few seconds, ask for a brief hold first, and never read customer data such as a full card number back to the caller.

Holds and routine inquiries

For wording while a caller waits, use these on-hold scripts. For routine inquiries like a password reset or profile management, a self-service link in your recap can save the caller a second call.

How to train call center agents on scripts

Training call center agents on scripts is mostly about judgment. A thorough call center script gives new agents the right words for routine customer calls, so they can take calls on their own sooner. But word-for-word recitation backfires on complex tasks: agents stop listening, miss the caller’s real issue, and lose chances to build customer relationships. Five best practices are key to helping agents use scripts without sounding scripted.

Start with active listening

Active listening is what lets an agent pick the right spiel. Teach agents to listen for the issue and for customer sentiment, then confirm what they heard before they answer. In agent training, review a few call recordings together and ask what the caller needed before anyone mentions the script.

Use role-playing exercises

Role-playing exercises let agents practice script usage before a live call. Pair agents, give each pair a scenario card (a billing inquiry, a ghost call, a customer complaint), and have them pick the spiel, adapt it, and say it out loud. Then swap roles, so each agent hears how the wording sounds from the caller’s side.

Let agents adapt the wording

Allowing agents to change the free parts of a spiel keeps calls human. Encouraging agents to mention past interactions or details they can see in the account turns a template into a conversation. Only the required lines, such as recording notices and wording set by company policies, stay word for word.

Use call monitoring and quality assurance

Call monitoring shows whether scripts work in practice. In quality assurance reviews, check that agents used the required lines and adapted the rest, and score the outcome rather than word-for-word accuracy. Ask for agent feedback too, since agents notice a spiel that falls flat long before the data shows it.

Incorporate customer feedback and update scripts regularly

Regularly update scripts to match current company policies, products, and customer inquiries. Incorporate customer feedback from surveys and complaints: if callers keep asking the same follow-up question, the recap spiel is missing something. Troubleshooting scripts need the most frequent reviews, because product changes break them first.

TextExpander banner: update a spiel once, and every agent has it, with a ;xferdirect chip and a button to see how shared Snippets work

Shared phone spiels in TextExpander

TextExpander stores approved phone wording as reusable Snippets in a shared library, so call center agents deliver consistent wording across the various customer interactions in a shift. Agents type a short abbreviation, personalize the text, and use the expanded wording as a speaking guide in the help desk, CRM, or call notes.

Organize spiels by call moment

Create a shared Snippet Group with one Snippet for each moment, using abbreviations agents will remember, such as ;open, ;ghost, ;xferwarm, ;xferdirect, ;recap, ;survey, and ;close. Keep the warm and direct transfer wording separate, so agents pick the handoff they’re actually doing. Give each Snippet a label that makes the choice obvious, such as “Recap: billing review pending” rather than “Billing script.” Some teams make a Snippet the first step of every call. A manager on Amwell‘s Network Operations Center team says, “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.”

Give agents Can expand access so they use the approved wording, and give the people who maintain it Can edit or Can manage access. One shared library supports knowledge sharing without every agent keeping a personal copy that drifts.

Personalize at call time

Fill-ins prompt agents for customer details before the text expands. Use single-line fields for names, pop-up menus for departments, and multi-line fields for an agreed next step. Typing ;recap, for example, can ask for the action taken, the current status, and the next step. The agent fills them in, expands the wording, and speaks from it naturally. TextExpander supplies the words, and the agent still listens, leads the conversation, and uses their own problem-solving skills when a call goes off script.

Enabling agents to skip the search for wording frees them to focus on the caller. Kammikia Barnes described what changed for CloseKnit Health’s care team once approved answers were in one shared library:

It was all very straightforward after we got TextExpander because the answers were right in front of us. We didn’t have to go look for them. It took away the second-guessing.

Kammikia Barnes, Population Health Strategist, CloseKnit Health

Keep the wording current

Team leads can use Snippet Activity to see who changed a spiel and compare the before and after wording. Review the relevant Snippets whenever a transfer destination, follow-up process, or survey flow changes, so the wording agents use to handle customer conversations still matches how the work is done. Updates can move fast. Ty Schalamon, Technical Support Manager at SketchUp, says, “When we have a new issue come up, we’re able to create a snippet and quickly share it so that everybody has the solution and our customers get a consistent response.” See how shared Snippets work for teams.

Put your first spiel to work

To use call center scripts effectively, start with the call moment your team handles most often. Choose one example above, adapt it to what your agents can actually do, and save it in a shared Snippet Group. Add Fill-ins for the details that change, read the expansion aloud, and adjust it until it sounds like a person talking. Then add the next moment.

Give every agent the right words for every call

Save your opening, transfer, recap, and closing spiels as shared Snippets with Fill-ins for caller details. Agents expand the approved wording in seconds and still speak in their own voice.

See what changes when your best call spiels are one shortcut away.

Frequently asked questions

What is a spiel in a call center?

A spiel in a call center is a short, prepared passage an agent says at one moment of a call, such as the opening, a transfer, a recap, or the closing. Spiels are building blocks of a call center script. Good spiels sound conversational, include the caller's real details, and only promise actions the team can deliver.

What is the difference between a warm transfer and a cold transfer?

In a warm transfer, the agent puts the caller on hold, introduces them to the next agent, and shares the request and the checks already done. In a cold, or direct, transfer, the call moves to the next team without an introduction. The spiel should match: only tell the caller the next agent has the details after a warm transfer.

What should an agent say on a ghost call?

On a ghost call, the agent should name the company and themselves, say they can't hear a response, and ask whether the caller can hear them. If there's still no audio after the wait time in the team's procedure, the agent explains they'll end the call and gives the support number to call back.

What is a CSAT spiel?

A CSAT spiel is the wording an agent uses to invite a caller to a customer satisfaction survey. It should ask for honest feedback, make taking part optional, and match how the survey works. If the survey starts after the agent disconnects, the caller needs to hear "please stay on the line," not "you can hang up now."

What is a recap spiel?

A recap spiel summarizes the outcome of a call before the closing: what was done, what's still open, who owns the next step, and any reference number. It ends with a question so the caller can confirm or correct the summary, which catches misunderstandings before the call ends.

Do call center scripts limit agents' problem-solving?

Rigid scripts can. When agents have to read every line word for word, they stop listening and can't adapt to the caller's real problem. Short spiels for set moments work better: agents use approved wording for openings, transfers, and recaps, and their own judgment for the problem-solving in between. Positive language helps too. "Here's what I can do" replaces "I can't do that," so the caller hears the next step instead of a dead end.

Can call center scripts reduce training time for new agents?

Yes. Scripts give new call center agents tested wording for the moments every call shares, so they spend less time working out what to say and more time learning the product and systems. Research points the same way: in an NBER study of 5,179 support agents, an AI assistant that put best-practice responses in front of agents raised issues resolved per hour by 14% on average and by 34% for novice and low-skilled agents.

What should a call center script include?

A complete call center script covers each moment of the call: the opening, the caller's issue, identity verification when it's needed, any transfer, a recap, and the closing. Include verification steps for sensitive information, such as account or payment details, and keep required compliance wording exactly as approved. Build the script around first call resolution (FCR), a key driver of higher CSAT scores. A caller who has to call back often starts the next survey already frustrated.

Keep reading

View all posts →
Support agent on a headset call while a ;csgreet Snippet fills in a greeting script with the caller’s name Customer Support Customer service scripts your team will actually use: call script examples, templates, and best practices Customer service live chat scripts in use: a support agent at her laptop inserts a chat reply with the ;chat Snippet. Collaboration & Teamwork 50 Customer Service Live Chat Scripts (Free Templates) Focused support agent typing a chat reply that opens with empathy statements from a ;empathy Snippet Customer Support 100+ empathy statements for customer service
Call center scripts and spiels: 7 examples for clear, consistent calls