Kairox Arch Prep
STUDY NOTES · LESSON 4 OF 12 · 5 MIN READ

Escalation and handoff: when an agent should pass to a human

Escalation triggers, clarifying ambiguous requests, and what a useful handoff packet contains — illustrated for customer support agents.

In 30 seconds

  • Escalate on clear triggers: a request for a person, repeated contact, policy thresholds, out-of-scope or stuck cases.
  • Ambiguous but answerable? Ask one specific question before acting.
  • A good handoff is a structured summary plus the transcript, so nobody repeats themselves.
  • Escalation is a designed path, not a failure.
Escalation from the agent to a human with a structured handoffAgentworks the caseTrigger?see list belowHandoffstructured packetHumanacts at onceyesno — keep workingasks for a personrepeated contactpolicy thresholdout of scope / stuckwho + issuewhat was triedwhat they wantwhy escalated+ transcript link
Escalate on clear triggers, and hand over a packet the human can act on immediately.

Triggers worth designing for

The customer asks for a person. Honour it, especially after repeated attempts. Pushing a retention offer or questioning first adds frustration.

A policy threshold is reached. Refunds above a limit, account closures or legal topics can require a human by rule — and that rule should be enforced in code.

The agent is stuck. A turn or cost limit reached, repeated tool failures or a request outside the agent's scope all mean the case should move on, with the work done so far.

Ambiguity is different

"Cancel my order" from a customer with two open orders is not an escalation; it is a question. When the request is ambiguous and the action matters, the agent should ask one specific question — showing both orders — before doing anything. Guessing by recency risks an irreversible mistake.

What the human should receive

customer: verified account #48213 (from session)
issue:    duplicate charge on invoice 2219
tried:    looked up both charges; refund tool blocked (above limit)
wants:    refund of $640 and a call back
why:      refund exceeds automatic approval limit
transcript: link

A structured summary like this lets the human act at once. A raw transcript forces them to re-read everything; a one-line note forces the customer to explain again.

Errors travel the same way

The same thinking applies between agents. When a subagent fails, it should report what it attempted, any partial results and the gap left, so the coordinator — or a person — can decide what to do next instead of discovering the gap later.

Part of Domain 1: Agentic Architecture & Orchestration (27% of the exam). Explanations are our own, checked against Anthropic's documentation on November 22, 2026.

Common traps

TrapWhy it failsDo this instead
Offering a discount before honouring "talk to a person"Ignores an explicit request and increases frustrationHand off with a summary
Cancelling the most recent order when unsureIrreversible guessAsk which order, then act
Escalating with "customer needs help"The human starts from zeroSend who, issue, tried, wants, why + transcript

Check yourself

Two original practice questions on this lesson. Try them before opening the answers.

Check yourself 1

Scenario: Customer support resolution agent

A customer writes: "This is the third time I am asking. I want to cancel my account and talk to a person." The agent could technically process the cancellation itself. What should the system do?

  1. A. Process the cancellation right away, because completing the request is the fastest resolution
  2. B. Offer a retention discount first and only escalate if the customer declines it a second time
  3. C. Ask the customer for their reason before acting, so the cancellation is recorded accurately
  4. D. Hand off to a human agent with a summary of the conversation and the cancellation request
Show answer and explanation

Answer: D. An explicit request for a person, repeated contacts and frustration are standard escalation triggers. A good handoff carries a structured summary so the customer does not repeat themselves. Acting unilaterally ignores the stated preference, and questioning or retention scripts before honouring the request increase frustration.

Check yourself 2

Scenario: Customer support resolution agent

A customer asks to "cancel the order" but has two open orders, and nothing in the conversation says which one. What should the agent do?

  1. A. Escalate to a human immediately, because the request cannot be completed
  2. B. Cancel the most recent order, since that is usually the one customers mean
  3. C. Ask which order they mean, showing the two orders, before taking any action
  4. D. Cancel both orders, since the customer clearly wants to stop buying
Show answer and explanation

Answer: C. When a request is ambiguous and the action is consequential, the agent should resolve the ambiguity with a short, specific clarifying question before acting. Guessing — by recency or by cancelling both — risks an irreversible mistake, and escalation is for cases the agent cannot resolve, not for a question one message can settle.

Keep going