Call Centre Scripts in Sri Lanka: How to Write Scripts Your Agents Will Actually Use

Most Sri Lankan call centre teams already have a script. It usually lives in a Word file someone wrote years ago, it was translated in a hurry, and half the agents quietly ignore it. Customers can hear the difference. A stiff script makes a good agent sound like a recording, and no script at all means every caller gets a different answer.

This guide is for supervisors and team leads who run inbound or outbound teams in Sri Lanka, whether that’s six agents in a Colombo office or forty across two branches. It covers how to write call centre scripts that agents actually use, how to handle Sinhala, Tamil and English on the same line, and what a good outbound or cold calling script looks like.

What a call centre script is really for

A script is not a speech. Its job is to make sure three things happen on every call:

• The customer is greeted and identified the same way every time.
• The agent gives the correct, approved answer to the common questions.
• The call ends with a clear next step, logged in your system.

Everything between those points can be flexible. The best scripts read more like a guide with fixed checkpoints than a word-for-word text. Agents keep their own voice, and you keep control of the parts that matter: compliance lines, prices, policies and promises.

The five parts of a good inbound script

1. Opening

Keep it short. Callers in Sri Lanka often start talking before the agent finishes, so a long greeting gets cut off anyway.

“Good morning, [Company], this is Nimali. How can I help you?”

If you need to confirm identity (for an account, an order or a booking), add one line straight after: “May I have your mobile number or reference number, please?”

2. Understanding the request

Give agents two or three open questions and one confirming line, rather than a fixed sequence:

• “Can you tell me a little more about what happened?”
• “When did you place the order?”
• “So you’re calling because the delivery hasn’t arrived and it was due on Tuesday. Is that right?”

That confirming line is the most useful sentence in any script. It cuts repeat explanations and shows the caller they’ve been heard.

3. Approved answers

This is where most of your script lives. Build it as a short library of answers to your top 15 to 20 questions, not one long document. Each answer should include:

• The exact facts the agent must say (delivery times, return rules, branch hours).
• What the agent must never say or promise.
• When to transfer, and to which team or extension.

Review this library monthly. Prices, offers and policies change, and an out-of-date script is worse than none.

4. Handling difficult moments

Write short, tested lines for the moments where agents freeze:

• The customer is angry: “I understand this is frustrating. Let me check exactly where it is right now.”
• The agent doesn’t know: “I want to give you the right answer, so let me confirm with my team. Can I call you back by 3pm today?”
• Hold: “May I put you on hold for about a minute while I check?” Then come back and thank them, even if it took longer.
• Transfer: Tell the caller who they’re going to and why, and pass the details on so they don’t repeat themselves.

5. Closing

Every call should end with a summary and a next step:

“So I’ve booked a technician for Thursday morning and you’ll get an SMS confirmation today. Is there anything else I can help with?”

The closing is also the right place for any short satisfaction question or follow-up offer, never the opening.

Writing scripts for Sinhala, Tamil and English callers

This is where Sri Lankan teams differ from the foreign templates that dominate search results. Many callers switch languages mid-sentence, and a script translated word for word from English often sounds unnatural.

A few practical rules:

• Write the meaning, not the words. Give your Sinhala and Tamil speaking agents the key facts and the required lines, and let a native speaker on the team write natural phrasing. Then have a second person check it.
• Keep fixed terms consistent. Product names, plan names and policy terms should stay the same in all three languages so reports and CRM notes match.
• Offer the language early. A simple “Sinhala, Tamil or English?” at the start, or a language choice on your phone menu, saves the awkward switch two minutes in.
• Test with real calls. Listen to recordings in each language for a week after any script change. You’ll quickly hear which lines agents skip or rephrase, and those are the lines to rewrite.

If you already use a phone menu, the same language order should carry through from the menu to the agent greeting. Our guide to IVR for small business covers menu greetings and prompts in more detail.

Outbound and cold calling scripts

Outbound calls need a different structure because the customer didn’t ask to talk to you. Whether your team does sales follow-ups, payment reminders, renewals or cold calling, the first 15 seconds decide the call.

A simple outbound structure:

1. Who and why, in one breath. “Hi Mr. Perera, this is Kasun from [Company]. I’m calling about the quotation you requested last week for your office.”
2. Permission. “Is now a good time for two minutes?” If not, agree a callback time and log it.
3. One relevant question. “Have you had a chance to look at it?” or, for cold calls, a question about a common problem in their industry.
4. The point. One clear benefit or update, not a full pitch.
5. A specific next step. A meeting, a demo, a callback date or a WhatsApp message with details.

For cold calling in particular:

• Call business numbers during business hours, and keep a do-not-call list that agents check and update.
• If someone asks how you got their number, have an honest, approved answer ready.
• Remember that Sri Lanka’s Personal Data Protection Act, No. 9 of 2022, applies to how you collect and use personal data, so check your calling lists and consent with whoever handles compliance in your company.
• Never script false urgency or claims you can’t back up. It damages your brand and your agents’ confidence.

Keeping scripts alive (and useful)

A script only works if agents can reach it in the moment. A printed sheet taped to the desk doesn’t scale past a handful of answers.

• Put scripts where agents work. Many call centre setups can show call notes, customer history and guided answers on the agent’s screen during the call. What’s possible depends on your system and CRM, so confirm it before you plan around it.
• Link scripts to your numbers. If first call resolution drops or average handle time jumps after a script change, you’ll know where to look. See our guide to call centre KPIs for the metrics worth tracking.
• Use call recordings for coaching. Pick two calls per agent per week: one that went well and one that didn’t. Compare both with the script and update whichever side was wrong, the agent or the script.
• Give agents a say. The people on the phones know which lines don’t work. A short monthly review with two or three agents keeps the script honest.

Teams with heavy seasonal peaks, like hotels during the tourist season, often keep a separate short script for busy periods. Our hotel call center guide covers that kind of overflow planning.

A simple script checklist

Before you roll out a new or updated script, check that it:

• Opens in under ten seconds.
• Has one confirming line agents can use on any call.
• Covers your top 15 to 20 questions with approved answers.
• Says clearly when and where to transfer.
• Works naturally in Sinhala, Tamil and English, checked by native speakers.
• Ends with a summary and a next step.
• Has an owner and a review date.

How Digital Urgency can help

The Digital Urgency Call Centre service is built around the way your team already handles enquiries. We start with your agent numbers, queues and reporting needs, then look at CRM integration, agent screen options and optional AI overflow for busy hours. Supported features, dialler modes and supervisor tools are confirmed in your written proposal before anything is set up.

You can choose a Standard, Premium or Enterprise starting point, and pricing is confirmed in your quote. Request a quote for Digital Urgency Call Centre and tell us how your team handles calls today.

Frequently asked questions

Should call centre agents read scripts word for word?
Only for compliance lines, identity checks and approved facts like prices or policies. For the rest, a guided script with fixed checkpoints sounds more natural and gets better results.

How long should a call centre script be?
The core flow should fit on one screen. Put detailed answers in a searchable library that agents open only when they need it.

How often should we update our scripts?
Review approved answers monthly, and immediately whenever a price, offer or policy changes.

Do we need separate scripts for Sinhala and Tamil?
Yes, but written for meaning rather than translated word for word, and checked by native speakers on your team.