Human Handoff
Human handoff (also called human takeover, agent escalation, or live agent transfer) is the process of transferring an ongoing chatbot conversation to a human support agent. The agent receives the full conversation history so the customer does not need to repeat themselves.
How it works
Human handoff is triggered when the AI chatbot cannot confidently answer a question, the customer explicitly requests a human, or the conversation involves sensitive/complex issues. The best implementations are seamless — the customer sees a smooth transition within the same chat window, and the human agent sees the full AI conversation transcript plus any collected customer data.
Handoff triggers can be automatic (low AI confidence score, certain topics like billing disputes) or manual (customer clicks "Talk to a human" button). Advanced platforms like Chatsy support both modes.
Why it matters
How Chatsy uses human handoff
Real-world examples
Key takeaways
Frequently asked questions
What happens if no human agent is available?
When no agents are online, the chatbot can collect the customer contact info and create a support ticket for follow-up. Alternatively, it can display estimated response times or offer to email a transcript when an agent becomes available.
Can I control when handoff happens?
Yes. You can configure automatic handoff triggers (low confidence, specific topics, customer sentiment) and also provide a manual "Talk to a human" button. Some platforms like Chatsy allow both approaches simultaneously.
Does human handoff disrupt the customer experience?
Not when implemented well. The best platforms keep the conversation in the same chat window, pass the full transcript to the agent, and notify the customer that a human is joining. The customer never needs to repeat themselves or switch channels.
What data should be passed to the agent during handoff?
The full conversation transcript, customer identification details, any collected form data (email, order number), the AI confidence score, detected sentiment, and a summary of the issue. This context helps agents resolve the issue faster and avoids frustrating repetition.