When handoff happens
By default, handoff is triggered in any of these situations:Explicit request
The customer asks to speak with a human agent.
AI decision
The AI determines it cannot properly resolve the situation.
Frustration
The customer shows signs of frustration during the conversation.
Forbidden topic
The conversation touches a topic configured for mandatory handoff.
Handoff across channels
Handoff works the same way conceptually on every channel — the AI stops responding, a human takes over, and the full conversation history is preserved. The surface differs per channel.Web chat
- AI stops responding in the same thread.
- A human agent takes over from the inbox.
- Full history is preserved for the agent and the customer.
Phone calls
- The AI transfers the call to a fallback phone number configured on the phone agent itself.
- Call history and context (including the AI-generated summary) are preserved on the session.
Phone uses a per-agent handoff configuration rather than the org-wide Handoff Settings. The preset levels, office hours, and data collection toggles on that page apply to text-based channels (web, email, WhatsApp, SMS, Slack) — not voice calls.
- The AI assigns complex threads to a human agent.
- A conversation summary and the full thread context are attached.
Slack
- The AI posts the conversation into your designated Slack support channel.
- Your team replies from Slack and the customer receives the response on their original channel.
- The AI stops responding in the same WhatsApp thread.
- A human agent continues the conversation. No additional setup required.
SMS
- The AI stops responding on the same phone number.
- A human agent takes over the thread seamlessly.
Next steps
Handoff Settings
Configure handoff levels, office hours, data collection, and more.
Forbidden topics
Define topics that always trigger a human handoff.