How do you write a call script?

Write it the way people talk

Marco calls Sophie Martin and reads her the script from head office.

Marco: "Good morning, my name is Marco and I am calling from [company] Customer Care regarding your maintenance agreement, contract number 20-41-77. Our records indicate that the annual inspection of your alarm system is now due. Regular inspection ensures the correct functioning of all sensors and helps prevent false alarms. The inspection fee amounts to EUR 79.00. Could you please confirm whether you would like to schedule an inspection, which day and time would suit you, and whether the installation address on file is still correct?"

Sophie: "What's this about?"

Marco goes back to the top of the page and reads it again, a little faster.

Sophie listened to about 30 seconds of contract number, fee and questions, and still had to ask what the call was about. Marco said exactly what the page told him to say.

Marco is one of four reps on Hana's team at [company], which installs and services alarms in homes and small shops. They call customers to book the yearly check, a paid visit from a technician. The people, the calls and the counts in this post are an example, not real data.

A call center script like this one is written at a desk, by someone who won't be saying it on the phone, so it comes out as a letter.

A call script that works is written to be said, not read. It holds the steps of the call in order, what each one is for, one question per turn, and the answers customers really give, each with the rep's next line. Only the lines that must not change are word for word, and in Hana's new script there are two, the price and the recap. You build it from recorded calls and test it before the whole team uses it.

Why do reps stop using the script?

The technicians noticed first. Customers kept hearing the price for the first time at the door, so Hana, the team lead, played back 30 recorded calls from last month, from all four reps.

In 8 of the 30, the rep read the script as written, and in 6 of those 8 the customer's first words were "What's this about?" or a question like it.

In the other 22, the rep said a shorter version of their own. Those calls sounded better, but every rep's version was different, and in 9 of them the price never came up.

Both habits come from the same page. Reps who read it sound like they're reading, because they are, and the rest rebuild the call from memory and lose lines like the price. Before you rewrite yours, play back recent calls from every rep and listen for both.

What goes in a call script?

Hana put the old script aside and asked what had to happen, in what order, for a customer to end up with a visit they could be home for and no surprise at the door. The answer was four steps, on one page a rep can glance at during a call.

These lines are for Sophie; with each customer, the name, the day and the address change. Marco first checks he has the right person: "Hello, is that Sophie Martin?"

If your team makes cold calls, the first turn of those calls is a subject of its own, covered in our post on how to open a cold call.

Hana made only two lines word for word. One is the price, missing from 9 of the 22 calls where reps used their own words. The other is the recap, because the customer has to hear the day, the time and the address exactly, and the same way on every call.

The rest is a goal with a line to start from. If Marco asks "Which day is better for you?", the Day and time step still does its job, and he sounds like himself.

What does a good line sound like?

Here are four lines from the old script and what Hana wrote instead.

Asked three things at once, a customer answers the last one they heard, or none; Sophie asked what the call was about. The new script splits them into three turns, one question each.

Before Marco asks to book, he gives Sophie a reason in her terms: it's been a year since her alarm was last checked. A contract number means nothing to her. Cut any reason only the company needs, like "so I can update our records", and keep the ones that help the customer, like the technician calling about 30 minutes before.

Say days, times and prices the way people say them: Thursday, "between eight and twelve", "79 euros". People plan their week by day names, so Marco leaves the date out. Phone numbers go in small groups of digits. Use the customer's words, "check" and "visit", where the old script said "inspection" and "schedule". Phrases like "regarding", "amounts to" and "on file" only tell the customer the rep is reading.

Every sentence in the new script fits in one breath, unlike the last sentence of the old one. If a sentence needs a second breath, make it two. When a customer doesn't follow, don't read the line again, a little faster, as Marco did. Say it shorter: "It's about your alarm. It's due for its yearly check."

The new call went like this.

Marco: "Hello, is that Sophie Martin?"

Sophie: "Yes, speaking."

Marco: "Hi Sophie, this is Marco from [company]. It's been a year since we last checked your alarm, so it's due again. Could we come next week?"

Sophie: "It works fine. Does it need a check?"

Marco: "It's working now, and the check keeps it that way. The technician tests every sensor and the battery. Shall I find you a morning next week?"

Sophie: "All right. Which days do you have?"

Marco: "We have Tuesday or Thursday morning. Which suits you better?"

Sophie: "Thursday."

Marco: "Is it still 14 Park Road?"

Sophie: "Yes."

Marco: "The check is 79 euros, the same as last year."

Sophie: "That's fine."

Marco: "So we'll see you on Thursday between eight and twelve at 14 Park Road. The technician will call you about 30 minutes before."

Sophie: "Great, thanks. Bye."

Marco: "Thanks, Sophie. Bye."

Count the question marks: none of Marco's turns has more than one. He answers Sophie's question about the check before going back to booking, and says goodbye after she does.

Which answers do you write down?

In the same 30 calls, Hana wrote down what each customer said when the rep asked about booking, the question that is now "Could we come next week?"

Four answers came up three times or more and cover 28 of the 30 calls. The first three lead to Visit booked once the customer agrees on a day, and "Call me next month" leads to Callback booked.

"Does it need a check?" came up in 8 of the 30 calls. The old script did answer it, but in the middle of a 30-second first turn, before anyone had asked, and nobody heard it there. When customers asked, each rep made up their own answer. Now the script has one.

The other two were one-offs, a question about adding a camera and a customer moving house. A script that tries to cover every answer turns back into the letter, so those stay with the rep.

How do you test a new script?

Before anyone tried the new script on a customer, Hana and Marco read it aloud to each other, Hana playing the customer with the four answers from the recordings. On paper the old script had looked fine, but its first turn took about 30 seconds to say, and the new one took under ten.

Then Marco used it on his own for a day, and Hana listened to his first 12 calls. No customer asked what the call was about, and the price came up in all 12. Three customers asked how long the check takes, so the recap got one more sentence: "The check takes about an hour." The recap is still one of the two word-for-word lines.

The whole team started with it the next week. Every month, Hana plays back 30 calls again. An answer that keeps coming back gets a line, and a line nobody needs comes out. She changes one line at a time, so she knows which change did what.

Where does DRING come in?

DRING does the same kind of work for AI agents. In Agent Factory, that work starts from your recorded calls and your workflow, and your customers' answers become tests in 1,000 to 10,000 simulated conversations, built for your company, before the first real call. You never write a prompt.

After launch, live calls show what to change next, and each change ships only after it passes the tests and you approve it. When a customer wants a call next month, Reach calls back at the time they asked for.