Human handoff with context
Closes the AI side of the conversation with a clear acknowledgment to the customer and produces a structured handoff packet — summary, intent, what was tried, what is needed.
Use as the terminal step on every workflow that can escalate. It guarantees humans never inherit a half-conversation.
It does not assign the ticket or set queue priority. Routing belongs to the helpdesk; this workflow only produces the packet.
- handoff
- close
Provisioning the MCP URL for Human handoff with context is part of Pro.
Free accounts can read the YAML, run the Live Preview, and provision one starter URL. Pro provisions URLs for the whole catalog.
Open YAML. Read it before you subscribe.
The harness that enforces this YAML is closed and hosted. The YAML is what you can audit, fork, and reason about.
1# human-handoff-with-context.yaml2name: human-handoff-with-context3version: 1.0.04category: escalation5description: Closes the AI conversation; produces handoff packet.6 7harness:8 - step: handoff9 emit:10 summary: <one_paragraph>11 intent: <last_classified>12 what_was_tried: <list>13 what_is_needed: <one_line>14 open_questions: <list>15 - step: close16 say_to_customer: handoff_acknowledgment17 Need human handoff with contexttuned to one client’s voice, escalation logic, and required fields? That’s a $99 personalization.
One-shot fee. Turnaround stated up front. The result is yours, with the deterministic harness already wired.
- Tier-2 engineering escalationConfirms the issue is engineer-grade, collects the technical context, and writes the escalation note.
- Manager escalationCaptures the reason for manager-level attention with structured grounding.
- Outage coordination handoffRoutes incident-related messages into the active incident channel with context.