An AI receptionist that will answer anything is not more capable. It is less finished.
The questions a line declines, and how it declines them, is most of what separates a built system from a configured one.
There are questions a receptionist should not answer, and they are the same questions whether the receptionist is a person or a system. Whether a treatment is safe for a particular patient. Whether someone has a case. Whether an insurance plan covers a procedure. What a job will cost before anyone has seen it. Each of these has a correct answer that the phone does not have, and the failure mode is not that the receptionist says nothing; it is that it says something plausible.
Which categories should a line decline?
Four recur across every industry we build for: clinical judgement, legal advice, coverage and eligibility, and firm pricing on unseen work. What they share is that a confident wrong answer is worse than no answer, and that the caller cannot tell the difference at the time.
Pricing is the one businesses argue about most, and the distinction that resolves it is between published prices and estimates. A med-spa's per-unit price is a fact the phone should state confidently. What a specific patient will pay for a treatment plan is not, and a line that blurs the two produces both lost bookings and awkward conversations at the counter.
| Category | The question | Cost of answering it anyway |
|---|---|---|
| Clinical | "Can I have this with my medication?" | Practising medicine, and a caller acting on it |
| Legal | "Do I have a case?" | Advice from an unlicensed source, potentially relied on |
| Coverage | "Is this covered by my plan?" | A patient billed for something they were told was free |
| Firm pricing | "What will it cost to fix?" | A quote the business has to honour or retract, both bad |
In each case the caller experiences a helpful answer. The damage arrives later, to the business.
How should a line refuse?
By capturing and routing, not by deflecting. The difference between "I can't help with that" and "that's a question for the doctor - let me take your details and have them call you" is the difference between a lost caller and a captured one, and it costs nothing.
The wording is not cosmetic. A caller told that the clinic cannot discuss medication interactions over the phone, and that a nurse will call them back within the hour, has been served. The same caller told "I'm not able to answer that" has been dismissed, and the underlying fact was identical.
- Never say what it cannot do without saying what happens next.
- Capture what the caller said, so the person who calls back is not starting cold.
- Sound like care, not like policy. A refusal that sounds bureaucratic reads as evasion.
- Never apologise for being a system. The caller wants their problem handled, not your architecture explained.
Why does refusing well make a line more useful, not less?
Because it is what lets the receptionist answer everything else confidently. A system with clear boundaries can quote prices, book appointments and answer policy questions without hedging, because it is not trying to cover cases it should not be in.
The alternative, a line that attempts everything with soft language, ends up hedging on the questions it should be answering crisply. Callers hear uncertainty everywhere and trust none of it. Boundaries are what make confidence credible.
It is also the honest answer to the objection this category attracts most, which is that an AI will say something it should not. It will, if nobody decided what it should not say. That decision is the work, and it is the difference between configuring a product and building a line.
A line that will answer anything is not more capable, it is less finished - clear boundaries are what let it quote prices and book appointments confidently, because it is not hedging to cover cases it should never have been in.
What your line must never say is a conversation we have before we build it, and it is usually the most useful hour of the project.
Start free pilotQuestions this raises
- What should an AI receptionist never answer?
- Clinical judgement, legal advice, insurance coverage and eligibility, and firm pricing on work nobody has seen. Each has a correct answer the phone does not have, and a plausible wrong one it can easily produce.
- Can it quote prices at all?
- Published prices, yes, and confidently; refusing them costs bookings for no benefit. What it should not do is quote a total for unseen work or a specific person's treatment plan.
- Isn't refusing things just a limitation?
- It is a design decision. Clear boundaries are what allow the receptionist to be confident everywhere else; a system trying to cover everything hedges on the questions it should answer crisply.
- How should the refusal be worded?
- As a handoff, never a dead end. Name who will handle it and when, capture the caller's details, and pass on what they already said so nobody has to start again.
- What if a caller pushes for an answer?
- The line should hold the boundary and offer the person. A system that can be argued into a clinical answer has the boundary as a suggestion rather than a rule.
Sources
- Recording of Customer Telephone Calls: guidance for organizationsOffice of the Privacy Commissioner of Canadaupdated 2018-04-18, consulted 2026-08-09
Want an AI receptionist built around these rules rather than despite them?
We build a working receptionist on your calls, your booking rules and your escalation rules, and you call it yourself before committing to anything. About 14 days, no call limit during the pilot.
Start free pilot