The escalation standard
Every system should know when to stop.
Every competitor sells how much their AI can handle. This page is about the opposite: the point at which it should hand the call to one of your people, and what has to happen when it does.
The wrong measurement
Most people evaluate an AI receptionist by how much it can take off their plate. Answer, qualify, book, deflect — the more it handles without involving anyone, the better it looks.
Good automation is not defined by how long it can keep talking. Good automation knows when it should stop.
And stopping is only useful if the next action actually works.
Which is why this page covers four things together, not one: what a request for a person has to trigger, what safety-sensitive language has to trigger, what happens when a transfer fails, and what happens when nobody is reachable at all.
Six rules
When the system has to stop and a person has to start.
This is the standard an AnswerCapture response system has to meet before it answers a real customer’s call. It is also a fair checklist for judging anything else you are shown — ours included.
-
If the caller asks for a person, they must get a person.
No further qualification questions, no loop, no “let me just grab a few details first.” Technology should make contact easier, not become a wall in front of it.
-
Safety-sensitive language must exit the normal flow.
Smoke, a burning smell, gas, flooding, electrical danger. The system must not attempt diagnosis and must not continue ordinary booking. It must move to the approved escalation path.
-
Escalating anger must reach a human.
A missed appointment, a tech who did not show, a job that went wrong. Empathy, judgment and the authority to fix it matter more than efficiency at that point.
-
Existing-customer issues must be out of scope.
Billing disputes, warranty questions, damage claims, unhappiness with completed work. Different conversation, different person.
-
If it does not know, it must say so.
“I don’t have enough information to answer that correctly, so I’m getting the right person involved” beats a confident wrong answer every time.
-
Anything outside its defined authority must escalate by default.
Clear limits on what it can do, what it can promise, and the conditions under which a person automatically joins the conversation.
What an escalation does
The person who picks up should not be starting from zero.
-
Customer requests a person
-
Qualification stops
No further questions. No loop.
-
Primary transfer
-
Secondary transfer
If the first is unavailable.
-
Message, context, alert
If nobody is reachable. A good handoff carries forward what the caller already explained.
The right person is notified by the route the business chose. A transfer is attempted while the caller is still on the line, and if it does not connect, the fallback the business defined runs instead of the call simply ending.
What the caller already explained travels with the escalation, including the reason it happened, so the person picking up is not starting from zero. Where that information lands depends on how the business is set up.
The system exists to help your employee, not to compete with them.
A standard only matters if the system can meet it when the call gets difficult.
So the standard above is not a description of good intentions. It is the set of behaviours an AnswerCapture response system is built and configured to meet, and the thing to hold us to.
You can talk to Riley in a browser and ask for a person yourself. The phone line is the same conversation over the full telephone path.