A customer service script is prepared wording customer service agents use for the moments that repeat on every call: the greeting, the hold, the refund explanation, the close. The scripts teams keep using are short building blocks.
They fix the facts and required lines, fill in the customer’s details, and leave the rest to the agent. Below you’ll find more than 40 call script examples, each marked with what to keep word for word and what to say your own way.
Key takeaways
- Customer service scripts work best as building blocks. Fix the facts, policy, and required lines, insert customer details as fill-ins, and leave greetings and empathy to the agent so calls sound like a person.
- Required wording needs one owner and one current version. When every agent keeps a personal copy of a script, old policy language keeps reaching customers long after the policy changes.
- New agents learn faster from a small starter set. A handful of scripts for the greeting, hold, transfer, and close builds habits before the library grows.
- Script adherence means using the required lines, not reading every word. QA reviews should check disclosures, verification, and accuracy, and give agents credit for adapting the rest to the caller.
First, a quick definition, because “script” means different things to a phone team, a chat team, and a compliance team.
What is a customer service script?
A customer service script is pre-written wording that agents use for predictable parts of a customer conversation, such as greetings, identity verification, holds, policy explanations, and closings. Good scripts cover routine inquiries and harder moments, like a refund request or technical issues, across the entire interaction. A call center script is the same idea for phone teams, often built from short spiels for each moment of a call.
Scripts sit alongside two related tools. A call flow is the order of steps in a call; a script is the words for each step. Canned responses are saved written replies for email and help desk tickets. If most of your volume is chat, start with our live chat scripts, and see these customer service call flow scripts for how the stages connect.
Scripts help most when the same question comes up every day across various customer interactions, when the wording carries risk (refunds, recordings, disclosures), and when new team members are still learning your products.
How to write scripts agents will use: fixed, flexible, and free
Long word-for-word scripts get dropped because callers hear them as read. No shared wording at all lets answers drift from agent to agent. The way through is to split every script into three layers.
- Fixed: Words that must be the same every time. Policy terms, refund windows, required notices, troubleshooting steps.
- Flexible: Details that change per caller, inserted as fill-ins. Name, order number, date, plan.
- Free: The agent’s own words. Warmth, empathy, small talk, and how they explain the reason behind a policy.
| Layer | What goes in it | Who owns it | Example from a refund call |
|---|---|---|---|
| Fixed | Policy, required lines, steps | Support ops or the policy owner | “Refunds go back to the original payment method within {Fill-in: refund window} business days.” |
| Flexible | Customer details | The agent, during the call | Customer name, order number, refund amount |
| Free | Tone, empathy, rapport | The agent | “I’m sorry this one arrived broken. That’s frustrating right before a weekend.” |
Keep the fixed layer short and focused on one core message. Short fixed lines are easier to keep current and easier for agents and callers who speak English as a second language. Fullscript’s support team works this way: organizational Snippets hold the non-negotiables, such as approved language for sensitive situations, and personal Snippets hold each agent’s greeting and sign-off.
If you want a robot, hire a robot. If you want a human, you need to give them access to be themselves. And TextExpander is a great way to do that.
Rachel Montgomery, Director of Knowledge Management, Fullscript
Tools like TextExpander store the fixed and flexible layers as one shared Snippet with Fill-ins, so the free layer is the only part an agent writes from scratch.
Examples of customer service call scripts
These customer service call script examples follow the stages of a call and show the key components of a great customer service script. Fill-ins appear in braces, and fixed lines (the ones to keep word for word) are in bold. Everything else is a starting point for the agent’s own words.
Greeting a new caller
Script 1: “Thanks for calling {Fill-in: company name}, this is {Fill-in: agent name}. How can I help today?”
Script 2: “Good {Fill-in: morning or afternoon}, you’ve reached {Fill-in: company name}. I’m {Fill-in: agent name}. What can I help you get started with?”
Script 3 (with a short introduction): “Thanks for calling {Fill-in: company name}, where we help with {Fill-in: one-line description}. I’m {Fill-in: agent name}. What brings you in today?”
A professional greeting works for first-time callers and new customers alike. Keep the opening under 15 seconds. For warmer openers, borrow from these customer service phrases.
Welcoming a returning customer
Script 4: “Welcome back, {Fill-in: customer name}. Good to hear from you again. Are you calling about {Fill-in: last order or ticket}?”
Script 5: “Hi {Fill-in: customer name}, it’s {Fill-in: agent name}. I can see we spoke about {Fill-in: last issue} on {Fill-in: date}. Is that what you’re calling about, or something new?”
Referencing past interactions from your CRM systems shows a loyal customer they don’t have to start over.
Handling complaints
Script 6: “I’m sorry to hear that, {Fill-in: customer name}. Let’s sort this out together. Can you tell me a bit more about what happened?”
Script 7: “Thanks for telling me. I’ve logged this as case {Fill-in: case number}, and our team responds to complaints within {Fill-in: response time}. While you’re on the line, let’s see what I can fix right now.”
More customer complaints wording: customer complaint scripts.
Frustrated customer
Script 8: “I can hear this has been frustrating, and I’m here to help. Let’s go over what’s happened so far so I don’t ask you to repeat anything you’ve already explained.”
A generic “I completely understand” adds little here. Lead with one specific empathy statement, then move to the fix.
Angry customers
Script 9: “I understand why you’re upset, and I’m sorry for the frustration this has caused. Let’s work together to get this resolved as quickly as possible. Can you tell me what happened?”
Script 10: “It sounds like this has been a challenging experience, and thank you for bringing it to us. I’m going to take care of this personally. May I ask a few questions so I understand it fully?”
Script 11 (if your policy has a boundary line): “I want to help you, and I can do that best if we keep this conversation respectful. Let’s look at what I can do next.”
For de-escalation in more detail, see these scripts for angry customers.
Apologizing to customers
Script 12: “I’m sorry about {Fill-in: what went wrong}. That’s on us. To make it right, I’ve {Fill-in: remedy}. Is there anything else this affected that I should look at?”
Call recordings
Script 13: “{Fill-in: your approved recording notice, word for word} How can I help today?”
The recorded-line notice is a fixed line. Use the exact wording your compliance or legal team approves for your region.
Late or missed deliveries
Script 14: “I’m sorry your delivery hasn’t arrived. Let me check order {Fill-in: order number} now. It’s showing {Fill-in: carrier status}, with a new delivery date of {Fill-in: date}. If that doesn’t work for you, here’s what I can do.”
Damaged or missing products
Script 15: “I’m sorry your order arrived {Fill-in: damaged or missing items}. We’ll send a replacement or a full refund, whichever you prefer. Could you share a photo of the item so I can start it right away?”
Incorrect orders
Script 16: “Sorry about the mix-up. Can you confirm what you received? I have {Fill-in: item ordered} on the order. I’ll email a prepaid return label today, and your correct item ships once it’s scanned.“
Billing and payment
Script 17: “Let me look at your account so we can go over the charge together. I see {Fill-in: amount} on {Fill-in: date}. {Fill-in: billing cycle or dispute terms, as approved}.”
For security purposes, ask only for the last four digits of a card, never the full number.
Coverage and policy questions
Insurance, warranty, and subscription contact centers answer the same coverage questions daily. The coverage language is a fixed line; everything around it can be conversational.
Script 18: “Thanks for calling {Fill-in: company name}, this is {Fill-in: agent name}. Are you looking for coverage details or questions about your benefits?”
Script 19: “I can check the status of that claim. Could you give me your policy number and claim ID? {Fill-in: claim status and next step, as shown in the system}.“
Script 20: “For {Fill-in: treatment or item}, your {Fill-in: plan name} plan says: {Fill-in: coverage language exactly as the policy states it}. Would it help if I explained what that means for your visit?”
Script 21: “I can update your address. Could you confirm your policy number and the new address? Changes take effect on {Fill-in: effective date}.“
Documentation or resource-sharing
Script 22: “I’ll send you our guide to {Fill-in: topic}. Would email work, or would you like the link to the online portal? Here’s the short version while you’re on the line: {Fill-in: one-line summary}.”
Account management
Script 23: “Happy to help with your account details. What would you like to change? Your {Fill-in: account field} will update to {Fill-in: new value} {Fill-in: effective timing}.”
Use the same script for profile management requests, like a new email address or phone number, after you confirm the customer’s identity.
Escalating to a manager
Script 24: “I understand this is important, and I want it handled the right way. I’m escalating this to {Fill-in: team or manager}, who will call you back within {Fill-in: callback window}. I’ve added everything we discussed so you won’t have to repeat it.”
Technical troubleshooting
Script 25: “Thanks for flagging this. Let’s walk through a few quick steps together. Take your time. First, {Fill-in: step 1}. Then {Fill-in: step 2}. Tell me what you see after each one.”
For troubleshooting support, keep each step to one action, and give the caller a few moments to try it before you move on.
Transferring a call
Script 26: “I’m going to connect you with {Fill-in: name} on our {Fill-in: team} team. I’ve shared that {Fill-in: issue summary} and that you’ve already {Fill-in: steps tried}, so you won’t need to repeat anything.”
A warm handoff matters, because it carries all the details of the customer’s issue to the next person. In Zendesk’s CX Trends 2026 research, 74% of consumers surveyed in 22 countries said they’re frustrated when they have to repeat information. For separate wording for a briefed handoff and a transfer without one, use these warm and direct transfer spiels.
Putting a caller on hold
Script 27: “Let me check that with {Fill-in: team}. It’ll take about {Fill-in: minutes} minutes. Is it OK if I place you on a brief hold? I’ll check back with you in {Fill-in: minutes} minutes either way.“
Script 28 (coming back): “Thanks for waiting, {Fill-in: customer name}. I have an answer for you.”
Script 29 (needs more time): “Thanks for holding. I need about {Fill-in: minutes} more minutes to confirm this. Would you like to keep holding, or should I call you back at {Fill-in: number}?”
More examples: on-hold scripts.
Sensitive issues
Script 30: “I understand this is a sensitive matter, and I’ll handle it with care. {Fill-in: approved privacy line} Can you tell me a little more so I can help?”
Asking for sensitive information securely
Script 31: “For your security, before I pull up the account, can you confirm the {Fill-in: verification item 1} and the {Fill-in: verification item 2}?“
Identity verification steps are fixed lines. Think of them as compliance scripts: the wording doesn’t change from call to call. Agents type answers into the account system during the call; they never read back full card or account numbers.
Upsell or cross-sell at call conclusion
Script 32: “Before we wrap up, since you use {Fill-in: product}, you may find {Fill-in: add-on} useful because {Fill-in: specific reason}. Would you like me to send details?”
Only offer what fits this customer’s reason for calling. Sales calls need their own scripts; on a support call, the offer comes after the customer’s concerns are resolved.
Follow-up and closure
The closing spiel leaves the last impression, so end on a positive note. Recap, confirm the next step, then sign off in your own words.
Script 33 (recap): “To recap, {Fill-in: what was done}, and {Fill-in: next step}. Your case number is {Fill-in: case number} if you need us again. Is there anything else I can help with today?”
Script 34: “Before we wrap up, I want to make sure everything you called about is covered. Is there anything else? Thanks for calling {Fill-in: company name}.”
Script 35: “I’m glad we could sort this out. We’re here by phone, email, or chat at {Fill-in: contact details} if anything else comes up.”
Script 36: “Thanks for your time today. You’ll get a short survey by email. Your feedback helps us improve.”
More options: call closing scripts.
Successful resolution
Script 37: “Great, {Fill-in: what was fixed} is working now. Thanks for your patience while we got there. Anything else on your list?”
Unresolved issue
Script 38: “I’m sorry we couldn’t resolve everything today. I’ve escalated case {Fill-in: case number}, and you’ll hear from us by {Fill-in: date}. If anything changes before then, call us and mention the case number.”
If the next step is a follow-up call, tell the caller the day and the number it will come from.
Feedback requests
Script 39: “How did we do today? Is there anything we could have done differently?”
Script 40: “We’ll email a two-question survey in {Fill-in: timing}. If you have a minute, it tells us what to fix next.”
See these follow-up scripts for after the call.
Agents use these most when they can insert them without searching. Try a few in the demo below.
Best practices for developing and implementing call scripts
Call scripts work best when they guide the conversation. Here’s how to build an effective customer service script your team will use, and how to use scripts effectively once they’re live.
Use scripts as flexible frameworks
Outline key talking points and the fixed lines, then give agents freedom to personalize the rest based on the customer’s tone and needs, so every call is a personalized interaction.
Involve your team in script creation
Frontline agents know what callers say and where scripts fall flat. Draft with them, and test the wording on real calls before it becomes the standard.
Update scripts based on real feedback
Review CSAT, call length, and agent comments regularly. When the same question keeps breaking a script, rewrite that script first.
Use plain, empathetic language
Avoid jargon and internal terms. The best scripts sound like a person talking: clear, kind, and specific.
Train for tone, not just words
Agent training should cover pacing, pauses, and reading the customer’s mood. Emotional intelligence and problem-solving skills decide how a line lands.
Use positive scripting
Positive scripting phrases a limit around what the agent can do. The facts stay the same; the caller hears a next step.
- Before: “We don’t have that in stock.”
- After: “That one’s back in stock on {Fill-in: date}. I can reserve one for you now, or show you a similar option that ships today.”
Write escalation paths into every script
Each script should say when to escalate and to whom. Agents shouldn’t have to guess mid-call whether an issue is theirs to solve.
Start new agents with a starter set
Give new team members five scripts first: greeting, verification, hold, transfer, and close. A manager on Amwell‘s Network Operations Center team describes the same habit: “When we train new agents, one of the first things we do is show them TextExpander. It makes onboarding so much easier.” Habits form faster with a small set, and agents don’t hunt for wording mid-call. Add scenario scripts once those are second nature.
Give every script an owner and a review date
Name one person to approve each script and set a date to review it. Scripts without owners are the ones that quietly go out of date. To see how teams handle this, watch how teams stay consistent.
How to keep required wording current in every script
Call script compliance means agents use required wording, such as recorded-line notices, identity verification, and required disclosures, exactly as approved, every time. Those lines belong in the fixed layer, with one named owner and one shared version.
This section isn’t legal advice. Have your compliance or legal team approve required lines for your industry and region.
Where required wording shows up
- Recorded-line notices at the start of a call
- Identity verification before account changes
- Disclosures for refunds, cancellations, renewals, or financial products
- Coverage or warranty language that must match the policy
Why scripts drift
Drift is usually a copy problem. Agents save scripts in personal docs, sticky notes, and old emails. A policy changes, the team gets an announcement, and half the copies stay as they were. The older wording keeps reaching customers for weeks.
Build scripts for secure information handling
Explain why information is needed, ask only for what you need, and never ask for full card numbers or passwords over the phone. Fill-ins for verification answers are typed during the call and never saved in a script.
Get required lines approved by your compliance team
If your company works under PCI DSS, GDPR, HIPAA, or similar rules, your compliance team should approve the fixed lines and their wording. Then:
- Name one owner for each required line.
- Keep one shared version that updates for everyone.
- Put a review date on every script.
- Take change requests through one channel, not ad hoc edits.
Here’s how it plays out. When the refund window changes from 30 days to 14, the policy owner edits one shared line, and every agent’s next call uses the new window. With shared Snippet libraries for teams, that edit reaches everyone at once.
One current version of every script
Save your fixed lines as shared Snippets with Fill-ins for caller details. When a policy changes, update the Snippet once and every agent’s next call uses the new wording, in your help desk, CRM, or email.
See what changes when your required lines update everywhere at once.
Benefits of using call scripts
Well-built scripts help call center agents deliver consistent service and meet customer expectations, no matter which agent answers.
Consistency in messaging
Callers get the same correct answer from every agent, which builds customer trust and cuts repeat calls caused by mixed messages. CloseKnit Health’s care team saw this once approved answers lived 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
Faster resolutions
Enabling agents to skip the hunt for wording or policy details mid-call frees them to listen and move the conversation forward.
Easier training and onboarding
New team members learn common scenarios, policies, and the tone you expect from the scripts themselves.
Accurate required wording
Verification steps and disclosures come out the same way every time, which reduces errors when details matter.
Drawbacks of over-reliance on scripts
Scripts stop working when they try to cover everything.
Robotic conversations
Callers can tell when someone is reading. Keep the fixed layer short and leave the free layer to the agent.
Limited flexibility in complex situations
Complex or emotional calls need judgment, not a longer script. Give agents the facts and the escalation path, then trust them with the conversation.
Reduced agent engagement
Agents who only recite lines disengage. Involving them in writing scripts and crediting good improvisation in QA keeps them invested.
Empathy, personalization, and active listening
A script lands when the agent connects with the caller as a person and can handle customer conversations that don’t follow the plan.
Train agents to adapt their tone
Teach agents to read whether a caller is frustrated, confused, or in a hurry, and adjust their pace. A calm, steady voice lowers tension.
Weave empathy naturally into scripts
Add empathy cues agents can say in their own words: “That sounds frustrating, and I’m here to help.” “Thanks for your patience while I look into this.”
Empower agents to go off-script
Sometimes the best response isn’t written down. Encourage agents to use judgment when a call needs it. Shared wording buys the time to do that, as You Need a Budget’s support team found:
By using TextExpander to repeat common directions or explanations, we save an hour a day for each team member… More importantly, it means we can use that reclaimed time to help the next customer sooner, and slow down to make each response personal.
Todd Curtis, Chief Customer Officer, You Need a Budget
Saved wording only helps when agents can make it their own. Amy-Lynn Taylor, Customer Insights and Enablement Expert at Jane, put it this way: “The responses were in someone else’s voice, and you almost spent more time fixing that reply to sound like you, or to match the issue that you were trying to solve.” Jane now splits its library into expert-owned shared Snippets for technical answers and personal Snippets for each rep’s introductions and check-ins.
Practice active listening
Reflect what the customer said before responding. “Got it, you’re seeing an error when you sign in. Let’s take a look.”
Using CRM and AI tools to enhance scripts
Technology makes scripts more personal when it brings the right customer details to the agent.
Tailor scripts with CRM data
Show customer details and past interactions next to the call flow. Instead of “How can I help you today?” an agent can say, “Hi {Fill-in: name}, I see you recently ordered {Fill-in: product}. Are you calling about that order?”
Use AI to suggest next steps
AI is good at drafting a script for a new issue or suggesting a next step during a call. A person reviews the suggestion, and the approved version joins the shared library. AI creates. TextExpander deploys: AI drafts the new wording, and the approved version goes where every agent types, so the next caller hears the same answer.
Self service can handle simple questions, but callers still want people. In a Gartner customer survey published in September 2026, 87% said access to a human agent is essential when companies use GenAI in customer service. See how TextExpander works as an AI text expander.
Save approved answers once and reuse them
When agents can see the order number in the CRM, they skip the question: “I see order {Fill-in: order number} is still in transit. Let me check the status.”
Measuring script effectiveness
A good script should change results, not just sound good.
Track key performance indicators (KPIs)
- First call resolution (FCR): Are callers getting answers without calling back?
- Customer satisfaction (CSAT): Are customers happy with the support experience?
- Average handle time (AHT): Are calls efficient without feeling rushed?
- Escalation rate: Are scripts helping agents resolve issues, or are too many calls going up the chain?
Use quality assurance tools
Quality assurance reviews of recordings and transcripts show whether agents use the fixed lines and personalize the rest, which makes them a fair way to evaluate agent performance. They also show which scripts agents never use; retire those.
Measure script adherence the right way
Script adherence means agents use the required lines (recording notice, verification, disclosures, accurate policy terms), not that they read every word. Score those lines on your QA scorecard, and give credit for adapting the free layer to the caller.
Collect agent and customer feedback
Agents often spot a script problem before the data does. Ask what feels unnatural, and watch post-call surveys for comments that the call felt scripted.
Test and refine continuously
Try different phrasing for the same step and compare results. Small changes, like softening a greeting, can make a difference.
Where TextExpander fits: one current version of every script
Scripts work when agents can find the current version in the moment. TextExpander saves the fixed and flexible layers as Snippets agents expand with a short abbreviation in the help desk, CRM, softphone notes, or email, so the same script works in Zendesk, Salesforce, and Gmail.
| Capability | Workflow change | Outcome |
|---|---|---|
| Shared Snippet Groups | The fixed layer of each script lives in one shared Group instead of personal docs | A policy owner updates a line once, and everyone’s next call uses it |
| Fill-ins | Agents type the caller’s details into prompts as the Snippet expands | The flexible layer is fast, and no customer data is stored in the library |
| Personal Snippets alongside shared ones | Agents keep their own greetings and sign-offs | The free layer stays in each agent’s voice |
| Inline Search | Agents find a script by typing a word instead of remembering an abbreviation | Less hunting mid-call |
| Snippet Requests (Business and Enterprise) | Agents suggest a better line, and an editor reviews it before it’s shared | The right people edit, and everyone else uses the approved version |
Here are six starter Snippets. Fill-ins are typed during the call, so no customer data is saved.
- ;csgreet Thanks for calling {Fill-in: company name}, this is {Fill-in: your name}. {Fill-in: your approved recording notice} How can I help today?
- ;csverify Before I pull up the account, can you confirm the {Fill-in: verification item 1} and the {Fill-in: verification item 2}?
- ;cshold Let me check that with {Fill-in: team}. It’ll take about {Fill-in: minutes} minutes. Is it OK if I place you on a brief hold? I’ll check back with you in {Fill-in: minutes} minutes either way.
- ;csrefund I’ve started your refund for order {Fill-in: order number}. Refunds go back to the original payment method within {Fill-in: refund window} business days, and you’ll get an email confirmation today.
- ;cstransfer I’m going to connect you with {Fill-in: name} on our {Fill-in: team} team. I’ve shared that {Fill-in: issue summary} and that you’ve already {Fill-in: steps tried}, so you won’t need to repeat anything.
- ;csclose To recap, {Fill-in: what was done}, and {Fill-in: next step}. Your case number is {Fill-in: case number} if you need us again. Is there anything else I can help with today?
Small teams see the effect quickly. At SketchUp, Technical Support Manager Ty Schalamon 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.”
Start with the five scripts your team says most often, then grow the library as habits form.
TextExpander is free. Your time isn’t.
Create shortcuts for the things you type most and start saving time everywhere you type. Use it solo or build a shared library with your team.
Free forever, no credit card required.
Frequently asked questions
What is a good opening script for customer service?
A good opening script for customer service names the company, gives the agent's first name, and asks one open question, such as "Thanks for calling Northwind, this is Jordan. How can I help today?" If calls are recorded, the approved recording notice belongs in the opening, worded the same on every call. Keep the opening under 15 seconds, and let agents add a friendly remark in their own words.
What is the basic structure of a customer service script?
A customer service script has three layers. The fixed layer holds wording that must stay the same every time, such as policy terms, required notices, and verification steps. The flexible layer holds the caller's details, inserted as fill-ins. The free layer is the agent's own words for tone and empathy. Keep each script short and tied to one situation, and for phone teams, pair it with call center spiels for each moment of the call.
What is positive scripting in customer service?
Positive scripting in customer service means phrasing a reply around what the agent can do. "We don't have that in stock" becomes "That one's back in stock on March 3, and I can reserve one for you now." The facts stay the same, but the caller hears a next step. It doesn't mean hiding bad news: agents state the limit clearly, then pair it with an option.
What is call script compliance?
Call script compliance means agents use required wording exactly as approved on every call, such as recorded-line notices, identity verification steps, and required disclosures. The wording depends on your industry and region, so your compliance or legal team should approve it. Problems usually come from drift: personal copies stay the same after a policy changes. One owner, one shared version, and a review date keep required lines current.
How do agents insert scripts quickly without searching a macro list?
Agents insert scripts quickly by saving them as text expansion Snippets with short abbreviations, such as ;cshold for a hold script. Typing the abbreviation expands the full script in the help desk, CRM, or email, and Fill-ins prompt for the caller's details. Inline Search finds a script by keyword when an agent forgets the abbreviation. TextExpander for customer support shows how teams set this up.