3 posts tagged with "escalation"

Every agent architecture diagram has the same three boxes. There's the happy path, where the model answers and the user leaves satisfied. There's the automatic fallback, where a low-confidence answer triggers a retry, a different tool, or a canned "let me look into that." And there's a third box, usually drawn last and smallest, labeled escalate to human. Everyone nods at that box in the design review. It looks like closure — the safety valve that makes the whole system defensible. "Don't worry, if the agent can't handle it, a person takes over."

Then you ship, and you discover the box was a lie. Not a technical lie — the code works, the ticket gets created, the conversation gets flagged. A staffing lie. The arrow labeled escalate to human points at a queue that nobody owns, has no service-level agreement, and appears on no one's on-call rotation. The agent did exactly what it was told. It handed the problem to an organization that never agreed to catch it.

The escalation tool was the safety net. The agent's confidence dropped below threshold, it called escalate_to_human, and the request slid into a ticket queue with a polite "a specialist will follow up shortly" reply to the user. Engineering closed the loop on the launch checklist. The on-call calendar listed humans on the receiving end.

Six months later, an audit walked the path. The escalation tool opened a Zendesk ticket. The Zendesk queue was triaged by a triage agent the support team had stood up to keep response times within SLA. The triage agent, finding no policy match it could resolve directly, called its own delegate_to_specialist tool — which routed the case to a specialist agent. The specialist agent, when uncertain, called escalate_to_human. The trace was a closed circuit. No human had touched any of the escalations the audit sampled. The human-in-the-loop the launch doc described did not exist.

The escalation interface had not failed. It had been honored at every hop. What failed was the assumption that the receiving system was a person.

Your support agent pages a human at 2 a.m. The human has been out for a week. The OOO message lives in the same inbox the agent is reading. The agent pings the human anyway. The auto-reply lands. The agent thanks it politely and pings again, because the reply did not contain the resolution code it was waiting on. Twelve cycles in, somebody on a different team notices the unread thread is now sixty messages deep and goes manually wake up the on-call.

The agent did exactly what the prompt told it to do. The prompt told it to escalate to a person. The person was a string, not a role. The string did not know about PTO.