Escalation & Handoff to Human
When the agent detects it is out of scope, uncertain, or blocked, it hands off to a human with a structured briefing — not a dead-end apology.
This page is the complete instruction page for one pattern called "Escalation & Handoff to Human." It explains the problem this pattern solves, the idea behind the solution, when you should (and should not) use it, and what happens afterward — both the good effects and the costs.
This matters because building AI agents is not just about making them clever. It is also about making them safe and predictable. Following a well-tested pattern like this one helps avoid common mistakes, and shows you exactly which safety rules and regulations it connects to, listed under "Standards Mesh" on this page.
Context
Agents will encounter requests they cannot safely handle. The difference between a good and bad handoff is what the human receives: a summary of what was tried, what is known, and what is blocked — or nothing.
Problem
Silent failure or vague apology destroys user trust and wastes human time.
Forces
- Agent autonomy vs user wellbeing
- Briefing quality vs handoff latency
Solution
On escalation, the agent produces a structured briefing: original request, steps attempted, current state, specific blockers, suggested next actions. Routes to a named queue. User is told they are being handed off and why.
Applicability
- Customer support agents
- Internal help-desk agents
- Any agent in regulated customer-facing flows
Anti-Patterns
- "I cannot help with that" as the terminal state
- Handoff without context, forcing the human to start over
Consequences
- +Graceful failure preserves trust
- +Human starts informed
- −Briefing pipeline to build
- −Bad briefings worse than none