Detect
Identify a situation that needs a human.
Move calls or messaging conversations to your team when a customer needs judgement, empathy, authority or a more personal interaction.
A strong AI workflow knows its boundary. Human handoff is part of the product architecture so the AI can stop when the conversation should belong to a person.
The useful part is context: the reason for the call, relevant answers and the conversation history can help the human continue without making the customer repeat everything.
Identify a situation that needs a human.
Preserve useful conversation context.
Move the call or messaging conversation.
Let the human take ownership.
Use escalation as a deliberate workflow outcome, not as a failure state.
This page is the handoff itself: define which situations need people, how the customer is told, and what context the team receives.
The goal is not to force every interaction through AI. The goal is to make the automated part useful, preserve context and make the human transition clear.
Explore human handoff โUse the product visual as a starting point. Replace it with your final workflow recording or dashboard capture before launch.
Yes. Human call transfer is a supported capability.
Yes. Human messaging handoff is supported.
The business should define the escalation rules based on its workflow.
Map the conversation, action and handoff before you scale it.
Talk through your workflow โ