How to write a voice agent script that does not sound like a robot

To write a voice agent script that does not sound like a robot, write for the ear, not the page: short sentences, one question at a time, everyday words, and rules the agent follows instead of lines it recites. Then test it aloud and on real calls.

This guide covers what a modern script actually contains, how to word it for the phone, and the parts most scripts forget: interruptions, mishearing, and the handover to a person.

Why most voice agent scripts sound robotic

Most scripts are written like emails or brochures, then read aloud. What looks fine on a page sounds stiff on a call. Three habits cause most of it.

• Sentences built for reading. Long sentences with several clauses are easy to follow on a screen, where you can glance back. On a call, the listener has to hold the whole thing in their head.
• IVR thinking. Scripts inherited from old phone menus list every option up front: “For bookings, say booking. For timings, say timings.” It made callers wait when it was press 1, and it does the same now.
• Formal register. “Kindly furnish your registered mobile number” is how forms speak, not how your front desk speaks, and callers hear the difference.

The other cause is structural. Many teams write one fixed path, word for word, and expect the call to follow it. Real callers do not. They answer the question you have not asked yet, interrupt, go quiet, or change their mind. A script that only works when the caller behaves sounds robotic the moment they do not.

Write goals and rules, not lines to recite

A modern AI voice agent does not read a script from top to bottom. A language model works out what the caller wants and picks the next step within the script, rules, and knowledge you approve. So the useful script is less like a screenplay and more like a brief for a well-trained new receptionist.

For each type of call, write down:

Part of the script	What to write
Goal	What a successful call ends with, such as a booked slot or a qualified lead
Must collect	The details the agent needs, in rough order
Must confirm	What it reads back before acting
Approved facts	Hours, locations, services, and policies it may state
Never says	Topics it must not answer, such as medical or legal questions, or prices you do not publish
Hands over when	The triggers for transferring to a person
Sample phrases	A few lines in your own voice, so the agent knows the tone

The sample phrases matter more than people expect. They set the register: how formal, how warm, how brief. But they are examples, not lines to recite. That lets the agent respond to what the caller said, not what the script assumed.

Write for the ear, not the page

Read every line aloud before you approve it. If you run out of breath or stumble, the caller will struggle too. A few rules cover most of it.

• One idea per sentence. “Your appointment is on Thursday. It’s at six thirty in the evening.” works better than one long sentence carrying both.
• One question at a time. “Can I take your name, your number, and which branch you’d like?” invites a jumbled answer. Ask for each in turn.
• Offer two or three choices, not five. Long lists are hard to hold in your head on a call. If there are more options, ask a question that narrows them down first.
• Use everyday words. “Book”, not “schedule an appointment at your convenience”. “You’re booked in”, not “your reservation has been successfully processed”.
• Say numbers the way people say them. “Half past six” or “six thirty in the evening”, not “eighteen thirty”. “This Thursday” or “the ninth”, not a date read out in numerals.
• Keep acknowledgements short and varied. A brief “Got it” or “Sure” sounds natural. Opening every reply with “Thank you for sharing that information” does not.

Language matters too. If your callers speak Hindi, Gujarati, or a mix of either with English, write the key phrases natively in each language rather than translating the English script. Our guide to Hindi, Gujarati, and Hinglish voice agents covers how to do that.

Get the opening line right

The opening line decides whether the caller relaxes or braces. It has four jobs: say who is answering, say it is an AI assistant, say what it can help with, and make clear a person is available. Do all four in a few short sentences.

“Hello, you’ve reached [business name]. I’m the AI assistant. I can help with bookings and timings, or put you through to the team. How can I help?”

We recommend saying it is an AI in that first line. In our deployments, disclosure raises trust and does not reduce completion rates. It also spares the caller working it out halfway through.

Avoid opening with a long disclaimer, a list of options, or a language menu. Let the caller speak and follow their lead.

Plan for interruptions, skipped questions, and mishearing

Real calls rarely follow the order you wrote. Script for that.

Interruptions. The agents we build support barge-in: the caller can interrupt at any point, as they would with a person. That means the important information goes first in every sentence. If the agent says “You’re booked for Thursday at six thirty” and the caller cuts in after “Thursday”, the key point has still landed.

Answers out of order. A caller who says “I’d like to book Thursday evening for a check-up” has answered several questions at once. The agent should take what it has been given and ask only for what is missing. Asking “What day would you like?” straight afterwards is the quickest way to sound like a machine.

Mishearing. Names, phone numbers, dates, and locality names are easy to get wrong on a phone line. Have the agent read the important details back once, in one natural sentence, before acting on them:

“So that’s Thursday the ninth at six thirty, for [name], on the number ending 4521. Is that right?”

If the caller corrects it, the agent should rephrase rather than repeat the same question word for word. For anything that must be spelled exactly, send a WhatsApp confirmation the caller can check.

Script the exits as carefully as the main path

The moments that most often sound robotic are the ones nobody scripted: the caller who wants a person, the question the agent cannot answer, and the end of the call.

Handing over. Every deployment we build ships with escalation rules from day one. The agent transfers when the caller asks for a person, when it is not confident it has understood, when the caller sounds frustrated, or when the request falls outside its scope. Write the handover line so it sounds like help, not refusal:

“I’ll put you through to someone from the team now. They’ll have the details of our call, so you won’t need to repeat anything.”

That promise has to be true. The person who picks up should receive the transcript with the call.

Saying “I don’t know”. If the answer is not in the approved facts, the agent should say so plainly and offer to connect someone or take a message. A confident wrong answer does far more damage than an honest handover.

Repeated misunderstanding. Set a simple rule, such as transferring after two failed attempts to understand, so no caller gets stuck in a loop.

Ending the call. Close with what happens next, then stop: “You’ll get a WhatsApp confirmation in a moment. Thanks for calling.” Do not loop through “Is there anything else?” three times.

Test it out loud, then on real calls

A script that reads well can still sound wrong. Test it in three rounds.

1. Read it aloud. Have someone who speaks the way your customers do read every sample line. Rewrite anything they trip over.
2. Role-play awkward callers. Interrupt mid-sentence, give three details at once, mumble a phone number, ask for a person straight away, and ask something off-topic. Note every point where the agent sounds stiff or gets stuck.
3. Review real transcripts. Once the agent is live, read a sample of calls every week. Look for questions callers had to answer twice, transfers that came too late, and phrases callers clearly did not understand.

This is how the tuning phase of every deployment works: we watch transcripts, sentiment, and resolution rates, then refine the script and rules.

Where to start

Pick your single most common call type, usually bookings or new enquiries, and write its goal, the details to collect, the read-back, the handover triggers, and a handful of sample phrases. Read it aloud, fix what sounds stiff, then test it against your own recorded calls. You can see how scripting fits into the full build on our AI voice agent development page, and how a clinic applies the same ideas in our AI receptionist setup guide. If you want to hear what your callers actually ask before writing a word, book a free call audit.