Most AI receptionists fail for a boring reason: nobody wrote the script.
The technology is rarely the problem. The problem is that a business turns it on with a generic greeting, no rules about what it can promise, and no plan for what happens when a caller asks something it does not know. Then someone gets a weird call transcript, decides "AI does not work for us," and turns it off.
A good script takes about an hour to write. Here is how to do it.
Start with the five calls you actually get
Before you write a word, pull your last two weeks of calls and sort them into buckets. Most small businesses find that four or five call types cover the large majority of the phone: new customer asking for a price, existing customer checking on a job or appointment, someone rescheduling, a vendor or salesperson, and a wrong number.
Write your script around those buckets. You are not building something that handles every conceivable call. You are building something that handles the calls you get every day, and hands off the rest cleanly.
Write the greeting like a person would say it
The greeting sets expectations for the whole call. Keep it short, say the business name, and get to a question fast.
Something like: "Thanks for calling Ridgeline Plumbing, this is the scheduling line. Are you calling about a new job or an existing one?"
Two things are happening there. The caller knows where they landed, and the first question immediately routes them into one of your buckets. Long greetings that list five menu options make people hang up or mash zero.
Decide what it is allowed to say
This is the part most people skip, and it is the part that causes trouble. Your script needs explicit boundaries:
- Can it quote prices? If yes, give it exact ranges and the conditions attached. If no, tell it to say so plainly and take the details instead.
- Can it book on the calendar? If yes, define your real availability rules, including buffer time and service area.
- What does it never promise? Same-day service, warranty coverage, legal or medical advice, discounts. Write the list down.
- What triggers an immediate handoff? Emergencies, angry callers, anyone who asks for a human twice, anything involving money already paid.
Write these as instructions, not hopes. "If the caller asks for a price on a repair, say we quote after a technician sees the job, and offer the next available visit" is a rule. "Be helpful about pricing" is not.
Give it your real answers, not marketing copy
The single biggest quality jump comes from feeding it the actual answers to your actual questions: hours, service area by zip or town, what you charge for a diagnostic visit, whether you take a particular insurance, how long a typical job takes, parking instructions, what a customer should have ready.
If a question comes up on the phone every week, it belongs in the knowledge base. This is the same content that makes website chat useful, so writing it once pays off twice.
Define the handoff, in writing
Decide exactly what happens when the AI cannot help. Warm transfer during business hours? Text the on-call number? Take a message and trigger instant lead follow-up so a human calls back within a few minutes?
Any of those work. What does not work is leaving it undefined, because then the caller gets a dead end.
Test it with your own worst calls
Before it goes live, call it yourself and run the hard scenarios: mumble, interrupt it, ask for a discount, ask for something you do not offer, ask a question that is not in the knowledge base. Then have someone who does not work for you try it.
You are looking for two failure modes. Does it make something up? Does it trap the caller in a loop with no way to reach a person? Fix both before launch, and keep reading transcripts weekly for the first month.
A script skeleton you can copy
- Greeting with business name plus one routing question
- Branch for each of your top call types
- The three to five questions you need answered for each branch
- Confirmation read-back of what was captured
- Handoff rules and the exact escalation path
- Closing that tells the caller what happens next and when
That is the whole thing. It is closer to a good front-desk training document than to software.
FAQ
How long should the script be? Long enough to cover your common calls and your boundaries, short enough that you can read it in one sitting. Most end up a few pages.
Do I have to write it myself? You know the answers, so your input matters most. Drafting and structuring it is the easy part to hand off.
How often should I update it? Review transcripts weekly at first, then monthly. Every question the AI fumbles is a line you are missing.
What if callers hate talking to AI? Some will. That is why the escalation path matters, and why an AI receptionist should be measured against a phone ringing unanswered, not against a perfect human.
Where this fits
A script is one piece. If you are trying to figure out which parts of your operation to hand to software at all, start with the broader picture in AI for small business, or look at how this plays out in home services, where missed calls translate directly into missed jobs. Once calls are handled, the same documented answers feed customer support automation and the routine follow-ups in workflow automation.
Want help writing yours? Book a short call and we will go through your last two weeks of calls together.