Set up a Zendesk AI agent (Advanced tier) and configure an API call step within the agent's flow to trigger the handoff to a human agent when a specific condition or user intent is detected.
In the API call step, POST to a backend endpoint you control, passing the conversation session context (session ID, collected variables, conversation transcript) as the request payload.
From your backend, use the Zendesk Messaging or Support API to create or update a ticket with the conversation context attached, and set the ticket's group or assignee to route it to the appropriate human team.
Optionally use the Zendesk Sunshine Conversations switchboard pattern: POST to .../passControl with switchboardIntegration set to the target integration name to transfer conversation control from the bot to a human agent workspace.
Subscribe to AI agent conversation events via webhooks to detect when a session ends or an escalation is triggered, enabling your backend to initiate the transfer without relying on the in-flow API call alone.
Validate the handoff by confirming the human agent receives the full conversation history before the transfer completes; avoid designs where context is only available in the bot session and not surfaced to the human UI.
Known gotchas
The legacy Answer Bot builder, intents, and flows were deprecated as of February 2025 and are now considered legacy functionality; new integrations should target the Advanced AI agent APIs, not the legacy Answer Bot API.
The Sunshine Conversations handover to a human uses POST .../passControl with a switchboardIntegration field — there is no /handover endpoint; using an incorrect endpoint path will return a 404.
Session variables and collected metadata live in the bot session context; unless explicitly extracted and written to a ticket or passed in the handoff payload, the human agent will not have access to them after the transfer.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp