What an AI receptionist can do, and what it should never be allowed to touch
Yes, an AI can answer your business phone — for a specific, listable set of calls, and not for the ones that decide whether the customer stays. Here is how to draw the line.
The honest answer to "can an AI answer my business phone" is: yes, for a specific list of calls, and no for the ones that decide whether the customer stays. Most write-ups skip the second half because the second half doesn't sell anything. This one leads with it.
I have put AI receptionists in front of restaurants, clinics, estate agents and home-services businesses. The pattern is consistent: they are excellent at the boring, repetitive, quotable calls, and genuinely dangerous at anything emotional, commercial or regulated. The job is not to decide whether AI is good. It is to draw the line in the right place and keep it there.
What it genuinely handles well
These calls share a property: the correct answer already exists in writing, and the caller just needs it said back clearly.
- Hours, location, parking and directions. Fixed facts, asked all day.
- Booking, rescheduling and cancelling. Contained, reversible, confirmed against a real calendar.
- After-hours capture. The alternative is voicemail, which most callers do not leave. An agent that takes a message with a callback number beats a beep.
- Standard FAQ. Services offered, insurance plans accepted, lead times, what to bring.
- First-response for new enquiries. A polite, immediate reply that captures what the caller wants and routes it to a human.
The common thread is contained work: one question, one quotable answer, no judgement required.
What it should never do
These calls share the opposite property: a wrong answer creates a commitment, an emotion or a liability that cannot be undone.
- Price negotiation. Never. A discount is a commercial decision the agent has no authority to make.
- Complaints. An apology is a promise. A machine cannot make one on your behalf.
- Anything legal, medical or financial. Out of scope, full stop. Liability sits with a person and a licence.
- Angry or distressed callers. Emotion needs a human. Pushing an agent harder tends to make it double down, not back off.
- Relationship-critical calls. A key account, a long-standing client, a sensitive family matter. Some calls are worth a person precisely because they cost you the most if handled badly.
- Anything that requires judgement between two reasonable answers. If the agent has to choose what's right, it has already left contained work.
How to decide where the line goes
Three questions sort almost any call:
- Is the answer a stated fact, or a judgement? Facts go to the agent. Judgements go to a person.
- Is the action reversible? Rescheduling is reversible. Promising a refund is not.
- Does it carry a relationship or a liability? If yes, a human owns it.
Notice that none of these are about how smart the AI is. They are about the shape of the call.
Task to route
| Task | AI | Human | Either | Why |
|---|---|---|---|---|
| Opening hours, address, parking | Yes | A fixed, quotable fact. | ||
| Book, reschedule or cancel (calendar-confirmed) | Yes | Contained and reversible. | ||
| After-hours new-enquiry capture | Yes | Better than a voicemail nobody leaves. | ||
| Standard FAQ (services, plans accepted, lead times) | Yes | Quotable from the facts file. | ||
| Price negotiation or discount request | Yes | A commercial decision, not an answer. | ||
| Complaint about a previous visit | Yes | An apology is a promise. | ||
| Anything legal, medical or clinical | Yes | Out of scope; liability needs a person. | ||
| Angry or distressed caller | Yes | Emotion needs a human. | ||
| Key account or sensitive relationship | Yes | Worth a person by definition. | ||
| Simple message-taking when nobody is free | Yes | Fine either way — if the payload lands somewhere. |
The baseline file every receptionist agent needs
Even a general receptionist needs a facts file. This is the minimum, adapted to your business.
[FACTS]
Business hours: Mon-Fri 08:00-17:00. Closed weekends and public holidays.
Address: 12 Oak St. Free parking at the rear.
Main line: 555-0100.
Services: [list the three or four things you actually do].
Booking lead time: 2 hours minimum, 30 days maximum.
Cancellation: free up to 24 hours before. Inside 24 hours a $[X] fee applies.
Payment accepted: card and bank transfer. No payment is taken over the phone.
Urgent or emergency: [what counts as urgent, and who to call].
[RULES]
Quote only facts listed in [FACTS]. If a fact is not listed, say a team member will confirm.
Never negotiate price, fees or terms. Never offer a discount.
Never take a complaint or issue an apology beyond the facts.
Never give legal, medical or financial advice.
Never pretend to be human. Say you are an automated assistant when asked.
Take a message, capture a callback number, and route it using the rules below.
[ESCALATE IF]
Caller is angry, distressed, or asks to speak to a person.
Caller wants to negotiate price, fees or terms.
Caller has a complaint about a previous job, order or visit.
Caller raises anything legal, medical or insurance-related.
Caller is a key account or an existing relationship worth more than the call.
The caller's question is not covered by [FACTS].How to tell whether it is working
Do not measure how many calls it "handled". That number rewards the wrong thing. Track these instead:
- Containment that held. Calls resolved without a human and with no follow-up complaint. A contained call that left the caller misinformed is a loss, not a win.
- Wrong-promise rate. Read the transcripts and count replies that contained a claim not in the facts file. This should be zero before you scale.
- Escalation quality. Did the human reply in one pass, using only the payload? If they needed the transcript, the payload is missing a field.
- Customer sentiment on escalated threads. Not the "satisfaction score" on the bot — read what people said after the handoff.
- Human time saved versus time spent cleaning up. The real number is minutes returned minus minutes spent fixing what the agent got wrong.
In the deployments I have run, the businesses that trust an AI receptionist most started by measuring the second and fifth lines above, not the first. Containment looks great right up until you read the transcripts.
Three mistakes
- Measuring containment instead of outcomes. "80% handled without a human" is meaningless if a third of those calls left the caller with the wrong idea. Read the transcripts before you believe the dashboard.
- Putting the agent on the number angry customers call first. The line that takes complaints should reach a human. Automate the boring queue, not the emotional one.
- Letting it improvise under pressure. Without a facts file and a quote-only rule, a pushed agent will invent a discount, an apology or a policy. The rules prevent more of this than a better model does.
What to do today
- Write the baseline
[FACTS]and[RULES]blocks, even in rough form. - Colour one week of real calls as AI, human or either, using the three-question test above.
- Move every complaint, negotiation and anything legal or medical call to a human-owned queue today.
- Add the "I'm an automated assistant" line, and check your local rules on disclosing it.
- Start reading a handful of transcripts each week. The wrong-promise rate is the number that matters.
An AI receptionist is a good colleague for the calls nobody wants to repeat all day. It is a bad one for the calls that decide whether a customer ever comes back. Draw the line with the second group in mind, not the first.
Know what to automate — and what never to
The routing table and the baseline facts file are available as a fill-in pack in our store, if you'd rather edit than build it from scratch.
See the Facts-File Template Pack →