An AI receptionist should not quote prices it has no rule for, diagnose equipment it cannot see, hand out advice that belongs to a licensed tech, or make judgment calls that are yours alone. When a call crosses those lines, the right move is fixed: book a visit, or get you on the phone. The limits are the feature.
01What does it refuse to answer, and why is that good?
Every sales pitch in this category lists what the system does. Here is the list that matters more, the questions a well-built system declines on purpose.
Prices outside the rules. If you have a written rule, the caller gets the number, exactly as you set it. If you do not, the system offers what the honest answer usually is anyway: a visit from someone who can see the problem. How rule-based quoting works is worth reading, because the mechanics are the whole guarantee. No rule behind it, no number on it.
Diagnosis over the phone. "It's making a clicking sound, what is it?" has a dozen possible answers, and a machine picking one is guessing with your license on the wall behind it. Symptoms get collected, carefully. Verdicts wait for eyes.
Anything a licensed tech has to say. Whether the caller can bypass a safety switch. Whether the smell is fine to ignore until Monday. No.
Your calls. Warranty exceptions, discounts for the angry customer, whether to fire a no-pay client. A receptionist, human or otherwise, who makes those decisions is running your company without asking.
Each refusal converts to the same two outcomes: a booked visit or an escalation to you. Neither one is a dead end for the caller. Both are dead ends for the improvised answer.
02The calls that still need you
Some calls should reach a human every time, and any vendor should be able to show you exactly how the handoff works.
The furious customer belongs with you or your best person. A machine can take the details calmly at 11 PM and put the callback at the top of your morning, but the apology and the make-good are owner work. The commercial negotiation, the property manager with 40 units talking terms, is sales, not intake. The tricky repeat customer, the one with history only you carry in your head, needs that head. And the call from your own tech, your supplier, or the inspector was never a receptionist call at all.
The system's job on these calls is to recognize them fast, capture what was said, and get them to the right person with the context attached, so nobody starts over. Handling them stays yours. When a call needs you, it gets you.
03Why a bounded system beats a confident guesser
Put two receptionists side by side. One answers every question, fluently, whether or not it knows. One answers what it knows, books eyes for what it does not, and never leaves the map you drew.
The first one sounds better on a demo. The second one is the only one you can leave alone with your phone at 2 AM, and that is the entire job description.
Here is the math of it. The confident guesser is wrong some fraction of the time, and every wrong answer ships under your name: a price you have to eat or walk back, a diagnosis that turns into "but the phone said." You will not be on the call when it happens. You will hear about it after, from the customer.
The bounded system pays a real cost too, and it is only fair to name it: it will sometimes decline a question that a sharp human at the desk could have fielded, and that caller gets a visit instead of an instant answer. That trade is deliberate. An occasional extra truck roll is a cost you can see and price. Improvised answers under your name are a cost you find out about at the worst time.
Bounded does not mean feeble. Inside the map, the system should be fast and complete: full intake, real quotes from your rules, booked jobs on your actual calendar. The boundary is where invention would start, not where usefulness ends.
04How to read a vendor who claims no limits
Ask one question: "Tell me three things your system will not do." Then listen.
A serious vendor answers immediately, because the limits are design decisions they made on purpose and can defend. An unserious one pivots back to the feature list, and that pivot tells you the system's edges were never mapped, which means you will map them yourself, live, on your customers.
Push further. Ask what happens, word for word, when a caller asks something outside the rules. Ask how the escalation to your phone actually fires and what you receive. Ask to see the log of a call where the system declined to answer. Show-me beats trust-me on every one of these.
This article is the three-things answer for our receptionist, in long form. It does not guess prices, does not diagnose blind, and does not make your calls. It answers, books, and escalates, by your rules. If you want the full walkthrough of where the edges sit for your trade, get in touch. Twenty minutes. We look at your call volume and tell you straight whether this pays for itself.
QUESTIONSCommon questions
What can an AI receptionist not do?
It should not guess a price it has no rule for, diagnose a system it cannot see, or make a judgment call that is yours. The right answer to those is booking a visit or getting you on the line.
Why would limits be a selling point?
Because the alternative is a machine that improvises with your name on it. A system that knows its edges is the one you can leave alone with your phone.
Twenty minutes. We look at your call volume and tell you straight whether this pays for itself. If the math does not work for your shop, we say so on the call.
Get in Touch