VIII · Safety & ControlMature★★

Conversation Handoff to Human

also known as Escalation, Live-Agent Handoff, Human Takeover

Transfer the entire conversation thread from agent to human operator, with state transfer and return primitive.

This pattern helps complete certain larger patterns —

  • specialisesHandoff★— Transfer the active conversation from one agent to another, carrying context across the switch.
  • used-byMandatory Red-Flag Escalation★★— Maintain a deterministic set of high-risk triggers so that on any match the agent immediately aborts its workflow and hands off to a human, without weighing whether to escalate.

Context

A team runs a customer-facing chat agent — support, sales, billing — that handles most conversations end to end, but some threads exceed what the agent can responsibly do alone: a refund above a policy threshold, a complaint with regulatory implications, a confused customer who explicitly asks for a person. The customer is mid-conversation, the agent has accumulated context across many turns, and the team needs a clean way to bring a human operator in without dropping the thread.

Problem

Approving or rejecting a single tool call does not solve this case, because the whole conversation needs to change owners, not just one action. If the agent simply tells the customer to call a support line, all the accumulated context is lost and the customer has to start over with a person who knows nothing. If the agent stays in the loop and parrots whatever the human says, accountability gets muddy. Without a structured transfer of the whole thread, escalation either destroys continuity or smears responsibility between agent and operator.

Forces

  • Handoff loses context fidelity.
  • Sticky routing (return to same operator on follow-up) needs auth + session plumbing.
  • Return primitive (back to agent) requires re-grounding.

Example

A customer-support agent has been resolving a billing issue for ten turns when it hits a refund threshold that requires a human. Approving a single tool call doesn't capture the situation — the operator needs the whole context. The team uses Conversation Handoff: the entire thread, plus a short hand-off note from the agent, transfers to a human operator's queue with a primitive to return ownership later. The customer keeps the same chat window; the operator picks up where the agent left off.

Diagram

Solution

Therefore:

On escalation trigger (low confidence, explicit user request, policy violation), the agent emits a structured handoff envelope with conversation summary, ticket number, and human operator queue assignment. Operator takes ownership; agent disengages. On return, agent resumes with operator's note in context.

What this pattern forbids. Once handed off, the agent does not generate to the user; the operator owns the thread until explicit return.

And the patterns that stand alongside it, or against it —

  • alternative-toHuman-in-the-Loop★★— Require explicit human approval at defined points before the agent performs an action.
  • complementsApproval Queue★★— Queue agent-proposed actions for asynchronous human review while the agent continues other work.
  • complementsInterrupt-Resumable Thought·— Preserve multi-step reasoning across interrupts by supporting paused-and-resumed thought frames so a new message handles cleanly without clobbering in-flight work.
  • complementsDecentralized Swarm Handoff★— Agents in a swarm decide handoffs to peers based on a shared protocol with no central coordinator; specifically about agent-initiated handoff protocols, not topology.
  • complementsScope-of-Practice Boundary Gate★— Block requests and responses that perform license-gated professional activities unless a licensed human is in the loop, enforcing the boundary in code outside the reasoning loop.
  • complementsSLA-Aware Triage Scoring★— Order the work queue by a single fused score that blends each ticket's time-to-SLA-breach, the requester's entitlement tier, and sentiment trajectory, and surface items predicted to breach before they do.

Neighbourhood

Click any neighbour to follow the language. Scroll to zoom, drag to pan.

Used in recipes

Used in frameworks

Show 3 more

References

Provenance