Most call scripts get written by listing everything the business would like to know.
That produces a long script that collects a lot of detail, takes a while, and still manages to leave out the one thing the person doing the work actually needed. The fix is to write it backwards.
Start from the next person, not the caller
Before you write a single question, answer this one: when this call is over, who picks it up, and what do they need in front of them to act without ringing the customer back?
That is the whole brief. Every question on the script exists to fill a gap in that answer, and any question that doesn’t is call time you are paying for.
It is the same discipline as mapping a process before you automate it, applied to sixty seconds instead of a fortnight. Write down what the outcome needs to contain, then work out the shortest set of questions that produces it.
The four almost everyone needs
A callback number, first. Not last. First.
This is the single most important design decision in the script and the one most often got wrong. Calls drop. People realise they are late for something. Systems occasionally mishear a whole sentence. If the number is captured in the first fifteen seconds, every one of those failures is recoverable, because you can ring back. If it is the last question, a call that ends early leaves you with a beautifully detailed description of a job and absolutely no way to reach the person who wanted it.
Confirm it by reading it back. Digits are what these systems mishear most.
Who is calling. A name, and whether they are an existing customer. The second half matters more than people expect, because it changes which pile the enquiry goes in and often changes the answer.
What they need. Open, in their words, not yours. Do not make callers pick from a menu of your service categories, because they don’t know your categories and choosing wrongly sends the job to the wrong place. Let them describe it and let the system classify afterwards.
Where, if where matters. Trades, mobile services and anything with a travel component need this early, because it can rule the job out entirely. There is no point collecting six more answers about a job two hours outside your area.
Four questions. Most businesses need one or two more. Very few need eight.
The ones that earn their place
A question stays on the script if a different answer would change what you do next. That is the test.
Urgency, when you actually triage. If a burst pipe jumps the queue and a dripping tap doesn’t, ask. If everything gets booked in the order it arrives, don’t ask, because you are collecting a number you will ignore.
Preferred times, when you are booking rather than calling back. Two or three offered slots beat an open question every time. “When suits you?” produces answers your diary cannot honour.
How they found you, if you spend money on marketing and will genuinely read the answer. If nobody looks at it, it is thirty seconds a call for nothing.
Access details, for anything on site. Parking, gates, dogs, someone home. These are the details that turn a scheduled job into a wasted trip, and they are trivially easy to ask on the phone and very annoying to chase afterwards.
What to leave out
Anything you would rather not have recorded. Card numbers, dates of birth, health details. These calls get transcribed and stored somewhere, and the cheapest way to secure a piece of data is not to collect it. If a deposit is genuinely needed, send a payment link afterwards.
Things you already know. The caller’s number is on the screen. Their name is in your records if they have rung before. Asking a returning customer to spell their surname again is a small insult that costs you nothing to avoid.
Your terminology. Don’t ask a caller whether they need a service, a repair or a callout if those words mean something specific to you and nothing to them. Ask what is happening.
Anything that invites a long answer you won’t use. Every extra minute is billed on most voice products, and it is the line people underestimate when they work out what one of these actually costs.
What it should say, not just ask
Two things belong in the script that aren’t questions.
That it is an automated system. At the start, plainly. Most callers work it out anyway, and hearing it up front reads as normal rather than as a discovery.
What happens next, with a time. “Someone will call you back before five today” is a complete answer. “Someone will be in touch” is not, and the difference shows up in how many people ring you again an hour later.
The limits are part of the script
The important half of the design is what the system must never do without a person.
Never quote above a set figure. Never promise same-day. Never handle a complaint. Never commit to a date the calendar cannot support. These are business decisions rather than technical ones, they belong with the rest of your AI guardrails, and if a product cannot be configured to respect them then you are trusting a language model’s judgement with decisions that carry real money.
Write that list before you shop, then check each product against it. It is one of the features genuinely worth insisting on.
Order matters more than the list
Given the same eight questions, two scripts can perform completely differently.
Number first, because it makes everything else recoverable. Disqualifying questions early, so you don’t collect six answers about a job you were never going to take. Open description before any structured detail, because callers explain the situation better when they haven’t already been funnelled. Confirmations at the end, all at once, rather than after every single field.
That last one matters more than it sounds. Reading back every answer as it arrives doubles the call length and makes the whole thing feel like a form. One clean summary at the end catches the same errors and sounds like a person.
Test it by trying to break it
Write the script, then ring it yourself and misbehave. Give a suburb that sounds like another suburb. Change your mind about the day. Mumble the last two digits of the number. Ask something the script has no route for.
You are not checking whether it sounds convincing. You are checking whether the thing that lands in your inbox afterwards is something anyone could act on without ringing the customer back. That is the only measure that matters, and it is the one the demo never tests.
If you want a second opinion on a script before it goes live, send me what you have and I’ll tell you what I think it is missing. Usually it’s the callback number in the wrong place.
Frequently asked questions
What questions should an AI receptionist ask?
At minimum: a callback number, who is calling, what they need, and where the work is if location matters. Ask for the number first, before anything else, because it is the one answer that makes every other failure recoverable. Everything beyond those four should earn its place by changing what you do next.
Why should an AI receptionist ask for the phone number first?
Because calls drop, people run out of time, and systems occasionally mishear. If the number is captured in the first fifteen seconds, every later failure is recoverable by ringing back. If it is the last question, a call that ends early leaves you with a detailed description of a job and no way to reach the person who wanted it.
How many questions should an AI receptionist ask?
Fewer than most scripts contain. Every question adds call time, adds cost on per-minute billing, and adds a chance to mishear something. A good rule is that a question stays only if a different answer would change what you or your team does next. Anything that would not change your next action is being collected out of habit.
What should an AI receptionist never ask?
Card numbers, dates of birth, health details, or anything else you would rather not have transcribed and stored. Also avoid asking for things you already know from the caller's number, and avoid asking a caller to diagnose their own problem in your terminology. Ask them to describe what is happening instead.
Should the AI receptionist give a price on the call?
Only for work where the price genuinely is fixed, and only within a limit you have configured. For anything variable, let it explain how pricing works and what happens next. A confident quote that turns out to be wrong costs more than a missed call, and it is the failure mode most worth designing out.
Wondering what this would look like in your business? A short chat is usually enough to tell.
Let’s chat