HIL-END-01Tier IIHuman-in-the-Loop Checkpoints

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.

Runtime: TerminateAgentOps: Operate & MonitorSee on the matrix →
STRUCTURED HANDOFF TO HUMAN Blockedout-of-scope ·low-conf Briefrequest ·attempted · Routenamed queue Tell Usertransparency HumanstartsinformedStructured briefing — "I cannot help" is not an acceptable terminal state.
In Plain English

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.

Placement

Where this pattern acts in the two lifecycles

Runtime Cognitive
01Perceive
02Reason / Plan
03Decide
04Act
05Observe
06Reflect / Learn
07Terminate

07 Terminate. Exit conditions, HITL escalation, handoff. 6 of 61 catalogue patterns act at this stage.

AgentOps Lifecycle
01Design & Scope
02Build & Integrate
03Evaluate & Red-Team
04Deploy
05Operate & Monitor
06Iterate & Adapt
07Decommission

05 Operate & Monitor. Runtime telemetry, drift detection. 18 of 61 catalogue patterns act at this stage.

Stages and counts from the catalogue data. The Runtime lens is the loop the agent runs each turn; the AgentOps lens is the lifecycle the team runs the agent through. See the Matrix for every pattern at each stage.

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