Template · Contact centre operations
Call center script template
In short
A call center script template is a written call flow that gives agents approved wording for each stage of a call: greeting, identity verification, discovery, resolution, hold and transfer, difficult moments and closing. This template covers a standard inbound customer service call, marks which lines are mandatory and which agents can say in their own words.
Inbound Customer Service Call Script template
Inbound Customer Service Call Script
Lines marked [REQUIRED] must be read as written because they carry legal, security or policy weight. Everything else is a guide: agents may use their own words as long as the purpose of each step is met. Replace every bracketed item before use. Script owner: [Name, Title]. Version: [__]. Last reviewed: [Date].
1. Greeting (first 5 seconds)
"Thank you for calling [Company Name], this is [Agent First Name]. How can I help you today?"
[REQUIRED where applicable] "This call may be recorded for quality and training purposes." (If your IVR plays this notice, the agent does not repeat it.)
If the caller's name is already on screen: "Hi, [Customer Name], thanks for calling [Company Name], this is [Agent First Name]. How can I help?"
2. Identity verification
[REQUIRED] "I'm happy to help with that. So I can access your account, can you please confirm your [full name] and [date of birth / ZIP code / last four digits of the account number]?"
If verification fails: "I'm sorry, I'm not able to match those details, so I can't discuss the account on this call. You can [verify through the app / call back with your account number / visit a branch]. Is there anything general I can help with?"
Never give hints about which detail did not match.
3. Discovery: understand the real reason for the call
Let the customer finish. Then ask one or two open questions:
"Can you walk me through what happened?" "When did you first notice this?" "What have you tried so far?"
Confirm understanding before acting: "So just to make sure I have this right, [summary of the issue]. Is that correct?"
If there are several issues: "I can help with both of those. Let's start with [most urgent issue] and then we'll take care of [second issue]."
4. Acknowledge and set direction
Use a specific acknowledgement, not a generic apology: "Being charged twice right before rent is due is stressful, I understand. Let me look into this now."
Tell the customer what you're about to do: "I'm going to check the payment history on your account, which will take about a minute."
5. Hold
[REQUIRED] Ask before placing on hold: "Would it be OK if I place you on a brief hold while I [check with billing / review the order]? It should take about [two] minutes."
Check back every [60] seconds: "Thank you for holding, [Customer Name]. I'm still working on this and need about one more minute. Are you OK to keep holding?"
Returning from hold: "Thanks so much for waiting. Here's what I found."
6. Resolution
Explain what you did and what happens next in plain words: "I've reversed the duplicate charge of [$amount]. You'll see it back in your account within [3 to 5] business days, and you'll get a confirmation email in the next hour."
If you cannot do what the customer asked, lead with what you can do: "I'm not able to waive the fee itself, but what I can do is [alternative]. Would that work for you?"
Check for understanding: "Does that make sense, or is there anything about it I can explain better?"
7. Transfer or escalation
[REQUIRED] Warm transfer wording: "The best person to help with this is our [department] team. I'm going to bring them on the line and explain everything so you don't have to repeat yourself. Is that OK?"
To the receiving agent (customer on hold or listening, per your policy): "Hi, I have [Customer Name], verified, calling about [issue]. I've already [steps taken]."
If the queue is closed: "That team is available [hours]. I've noted everything on your account, and your reference number is [number]."
8. Difficult moments
Upset customer: "I can hear how frustrating this has been, and I want to get it sorted for you. Let me [specific action]."
Customer asks for a supervisor: "I can arrange that. Before I do, may I try one more thing that might fix this now?" If they still want a supervisor, transfer per the escalation process without further pushback.
Abusive language: "I want to help you, and I'm not able to continue if the language continues. Can we keep working on this together?" If it continues, follow the [abusive caller policy] and give one final warning before ending the call.
Agent does not know the answer: "That's a good question. Let me check so I give you the right answer rather than a guess."
9. Closing
Summarize: "So to recap, [what was done] and [what happens next, with timeline]."
"Is there anything else I can help you with today?"
[REQUIRED where applicable] Survey notice: "You may get a short survey about this call. Thanks for taking the time if you do."
"Thanks for calling [Company Name], [Customer Name]. Have a good [morning / afternoon / evening]."
After the call: select the disposition code, write notes in the format [issue / action / outcome / follow-up], and complete after-call work within [__] seconds.
Script control
- Script owner
- Version number
- Approved by (compliance / legal, where required)
- Effective date
- Next review date
- Summary of changes from previous version
How to use this template
- Replace every bracketed item with your company name, verification fields, hold and after-call targets, and the departments agents transfer to.
- Have compliance or legal approve the lines marked REQUIRED, and keep everything else as guidance agents can phrase in their own words.
- Listen to 20 to 30 real calls for this queue and check the script against how calls actually go before you publish it.
- Load the script into your agent desktop or knowledge base so it sits next to the customer record, not in a binder.
- Train agents on the purpose of each step through roleplay, then let them practice until the required lines are automatic and the rest sounds natural.
- Line up your QA form with the script so evaluators score the purpose of each step and the required lines word for word.
- Review the script every quarter, or sooner after a policy change, and record each change in the script control block.
When a script helps and when it hurts
Scripts earn their place in three situations: legal or security wording that must be said exactly, new agents who need a structure until the call flow becomes habit, and repetitive call types where consistency matters more than personality. Outside those, a word-for-word script makes agents sound robotic, and customers notice within a sentence.
The template above handles that by marking a short list of mandatory lines and treating everything else as a guide. Most experienced centers run this way. New hires read closely during their first weeks; by the time they finish nesting, they should be hitting the purpose of each step in their own voice. Build the script into your call center training plan so agents practice it in roleplay before they ever take a live call.
What each part of the call is doing
Greeting. Short and fast. Callers have often waited in queue; a 20-second branded welcome on top of that annoys people. Name, company, offer to help.
Verification. This is where fraud happens. Script it exactly, and never let agents hint ("is it maybe a different ZIP?"). Account takeover often starts with a helpful agent.
Discovery. The step most often rushed. Agents who jump to a fix before confirming the problem create repeat calls, which is why poor discovery shows up later as weak first call resolution.
Hold and transfer. Ask permission, give a time, check back. Warm transfers with a handoff summary are worth the extra 20 seconds; cold transfers where customers repeat everything are a leading driver of complaints.
Closing. A recap with a timeline prevents the "where's my refund" call five days later. The disposition and notes matter as much as what was said, because the next agent depends on them.
Writing scripts that sound human
- Write the way people talk. Read every line aloud. If it sounds like a letter, rewrite it.
- Replace generic empathy with specific acknowledgement. "I understand your frustration" has been said so often that it reads as a script. Naming the actual situation works better.
- Lead with what you can do. "I can't do that" ends the conversation. "What I can do is" keeps it going.
- Keep lines short. Agents need to glance at the screen mid-conversation, and two-line prompts are easier to pick up than paragraphs.
- Give options, not one fixed phrase, for the non-required steps. Three ways to open discovery let agents pick one that fits the caller.
- Script the hard moments in detail. Agents rarely need help saying hello. They need help with the supervisor request, the abusive caller, and the question they cannot answer.
Connecting the script to QA and coaching
Your QA form and your script should describe the same call. If the script has nine steps and the call center QA scorecard scores twelve different behaviors, agents will follow whichever one affects their score. Score the required lines word for word. Score everything else on purpose: did the agent verify, confirm understanding, set expectations?
When a script change goes live, expect a short dip in average handle time stability and QA scores for a week or two while agents adjust. Brief the QA team first so they do not mark agents down for following the new version.
Managing scripts across large and multi-site teams
In a center with several programs and sites, version control is the real problem. Agents keep printed copies, team leads add their own tweaks, and six months later three versions of the refund script are in use. Keep one master version in a searchable knowledge base linked from the agent desktop, record the owner and review date on each script, and retire old versions visibly.
For outbound programs (sales, collections, appointment setting), scripts carry more legal weight. Required disclosures under the Telephone Consumer Protection Act, the FTC Telemarketing Sales Rule, the Fair Debt Collection Practices Act or state law may need specific wording and timing. Have counsel review them, and do not let anyone edit those lines locally. Rules vary by state and by the type of call, so get advice for each program.
Frequently asked questions
What should a call center script include?
A greeting, identity verification, discovery questions, acknowledgement, hold and transfer wording, resolution and expectation setting, wording for difficult situations such as escalations and abusive callers, and a closing with recap. Mark which lines are mandatory and which are guidance.
What is a good customer service script opening?
Keep it short: thank the caller, give the company name and your first name, and offer to help. For example, "Thank you for calling [Company], this is Jordan. How can I help you today?" Add the recording notice only if your phone system does not already play it.
Should call center agents read scripts word for word?
Only for lines with legal, security or policy weight, such as disclosures and identity verification. For the rest, agents sound better and resolve more when they meet the purpose of each step in their own words. New hires usually follow the script closely at first and flex as they gain experience.
How do you write an inbound call script?
Listen to 20 to 30 real calls for the queue, map the common call flow, write short spoken lines for each stage, script the difficult moments in detail, and have compliance approve the required lines. Test it in roleplay, then revise after the first two weeks of live use.
What is a good call opening and closing script?
Opening: thank the caller, give your name, offer help, and verify identity before discussing the account. Closing: recap what was done and what happens next with a timeline, ask if there is anything else, and thank the caller by name.
How often should call scripts be updated?
Review them at least quarterly and whenever a policy, product, price or legal requirement changes. Record each version with an owner and effective date so QA evaluators and agents are working from the same script.