Skip to content
Home › Escalation to Human

Structured handoff summary

Escalation to Human

Definition

The structured context payload an agent must pass to a human when escalating — never a raw transcript dump.

Key points

  • Required fields (all five):
    1. Customer ID + verified identity
    2. Root cause
    3. What was attempted + outcome
    4. Relevant amounts / order numbers / policy
    5. Recommended action
  • Do NOT dump raw transcripts — pass a compact structured summary. Escalating with no context is a failure pattern.
  • Playbook example payload (from The Escalation Handoff): customer_id: "CUST-847392", root_cause: "Duplicate charges due to gateway timeout.", amount: "$47.00 USD", recommended_action: "Approve refund for $47.00 USD and notify customer."
  • For the Complex Policy Issue branch, account-context tools (e.g. get_customer) are called first so the summary carries verified identity and details.

Why it matters for the exam

  • Scenarios ask which handoff is correct; the answer is the structured, minimal, decision-ready summary — not "forward the whole chat" and not "escalate with just the complaint."

Common gotchas

  • Missing recommended action, or missing verified identity, makes the handoff incomplete.
  • Raw transcript = wrong; empty escalation = wrong.

See also

Sources

Referenced by