Escalation and ambiguity resolution

When to escalate

• The customer asks for a human.
• Policy is ambiguous or does not address the request.
• The agent cannot make meaningful progress.

Note what is absent. Complexity is not on the list. An agent that escalates because a case is complicated escalates constantly and resolves nothing.

Explicit requests are honored immediately

If a customer asks for a human, escalate without first attempting investigation. Investigating first is well-intentioned and reads as ignoring what they asked for.

There's an important distinction here. If a frustrated user hasn't asked for a person, acknowledge the problem and offer to solve it when the agent can do so safely. Escalate if the user then asks for a person. Frustration deserves a response, but it doesn't always require a handoff.

Do not use sentiment or confidence alone

Sentiment-based escalation treats tone as difficulty. An angry customer with a simple problem gets escalated; a polite one with an intractable one doesn't.

Self-reported confidence is no better as a trigger. It doesn't track case complexity reliably, and using it means the agent decides how hard its own job is.

Use explicit criteria instead, with few-shot examples showing escalation versus autonomous resolution — the 4.2 technique applied to a judgment call.

Policy gaps

A clear reason to escalate is a request the policy doesn't cover. If the policy addresses price adjustments on your own site but says nothing about matching a competitor, the agent should escalate instead of inventing a rule.

Multiple matches mean ask

When a lookup returns several possible customers, request an additional identifier. Do not select by heuristic — most recent, closest name match. A wrong pick here means acting on the wrong person's account, and the customer can disambiguate in one question.

Reading all three records to work out which one is meant isn't a safer version of guessing. It opens two uninvolved people's account details in order to answer one person's question, and read-only access doesn't make that acceptable. Ask for the identifier.