Chatbot human handoff does not have to mean a live agent jumping into the chat. When a chatbot can't answer, the most practical option for a small team is asynchronous escalation: a contact form routed to your CRM, a support ticket with a summary of the problem, or a booked call on real free slots. The visitor never hits a dead end, and your team replies when it is actually available, with the context already attached.
This guide covers the four ways to handle chatbot escalation to a human, the moments that should trigger it, message templates to copy, and what to track afterwards. Every sample conversation below is fictional and meant as an illustration, not as measured results.
Quick answer
- No one online all day: contact form, ticket or booking, with a stated response time
- Team answering in real time: a live chat tool such as Crisp, LiveChat or Intercom is the right fit
- Core triggers: the visitor asks for a person, the answer is missing from your knowledge base, or the topic is sensitive
- Golden rule: never leave the visitor stuck, and never promise an instant reply if nobody is there
Table of Contents
Why the Handoff Matters as Much as the Answer
A chatbot that handles most questions well is doing its job. The remaining ones shape what visitors remember about your business. Two things are at stake.
Trust. A bot that improvises instead of admitting a gap commits your company to whatever it says. In 2024, a British Columbia tribunal held Air Canada liable for wrong bereavement-fare information given by its chatbot; the Moffatt v. Air Canada ruling is a clear reminder that a company remains responsible for what its chatbot says. "I don't know, here is how to reach someone" beats a confident guess. The guardrails side of this is covered in our piece on AI chatbot hallucinations and reliability.
Lost leads. Visitors who ask a specific question about a quote, a lead time or an edge case are often close to deciding. If the bot says "I don't have that information" and offers nothing next, they leave, and you never find out.
There is also a transparency angle. Article 50 of the EU AI Act requires that people be told when they interact with an AI system. Labeling the bot clearly and showing how to reach a person fits that spirit.
4 Ways to Hand a Conversation to a Human
"Handover" suggests a live agent taking over mid-conversation. For a small business where nobody watches the site all day, that is neither the only model nor the most realistic one. Here are the four options and when each fits.
| Method | Staffing needed | Best for | What to ask the visitor |
|---|---|---|---|
| Form / CRM | Reply within hours | Quotes, sales questions, edge cases | Name, email, need in one sentence |
| Support ticket | Deferred handling | Technical issues, complaints, after-sales | A reviewed summary, order or product reference |
| Booked call | Scheduled slots | Advice, demos, complex topics | Slot, reason, contact details |
| Live chat | Real-time presence | Teams answering all day | Nothing: the chat simply continues |
1. A contact form wired to your CRM
This is the simplest and most universal option. In Heeya (Standard and Premium plans), the agent displays the contact form right inside the chat when the visitor wants to talk to a person. It also offers the form on its own when it can't find the information in the knowledge base.
On Premium, submissions can be sent to a webhook, HubSpot or Pipedrive, with a notification email. If your site passes the logged-in visitor's identity to the widget, the form can be prefilled with their email, one less step for them. The webhook route is explained in our Zapier and HubSpot webhook guide.
What to ask: as little as possible. An email, a first name and a sentence describing the need. Every extra field lowers completion.
2. A support ticket
Tickets suit problems that need real investigation: a fault, a defective part, a blocked order. In Heeya (Premium), the agent drafts a summary of the problem from the conversation. The visitor reads it and validates it themselves before sending. The ticket then lands in the dashboard, on the Tools page.
The benefit: your team gets a readable case file, not a forty-message transcript, and the visitor does not have to explain everything twice. For the broader picture of reducing ticket volume, see customer self-service and ticket deflection, and for the product side, the AI ticketing chatbot page.
What to ask: the validated summary, plus whatever identifies the case: model, order number, purchase date.
3. A booked call
When a topic deserves a conversation, a time slot beats "we'll call you back". In Heeya (Premium), the agent shows a card with the real free slots. The visitor picks one and confirms; emails with an .ics file follow. The appointment replaces an immediate handoff with a dated commitment, which reassures more than a vague promise. Our appointment booking chatbot page explains how it works.
What to ask: the slot, a one-line reason, and a way to reach them.
4. Human live chat
If your team answers in real time through the day, a live chat tool such as Crisp, LiveChat or Intercom is a full option in its own right: a person picks up the conversation where the bot left off. It is the best handoff there is, provided someone is actually there. Outside staffed hours, the bot needs a second exit, otherwise the visitor waits for nothing. To pick a live chat tool, see our roundup of LiveChat alternatives.
Heeya is designed so the agent answers on its own and hands over through a form, a ticket or a booking. The two approaches suit different organizations; our AI chatbot vs live chat comparison helps you choose.
When to Trigger the Handoff
A good chatbot that can't answer does not wait for three failed attempts. Three situations justify handing over.
An explicit request
"I want to talk to someone", "agent", "human". The visitor has decided: don't make them argue with the bot. Offer the exit straight away, with no unnecessary questions first.
Information missing from the knowledge base
The question is about a special price, an undocumented case, an unpublished lead time. The agent should say so plainly and offer the next step. These moments are also a signal: each unanswered question points to content you should add.
A sensitive topic
Complaints, disputes, personal data requests (access, deletion), legal or medical questions: even if the bot finds a relevant passage, these deserve human eyes. List these themes in the agent's instructions and define the exit to offer. For regulated professions the logic is the same: the bot points the way, the professional answers.
What should not trigger a handoff by itself: small talk, or a question your documentation already covers. Escalating too early defeats the point of the chatbot and floods your team.
Message Templates to Copy (Fictional Examples)
The conversations below are made up to illustrate tone. Adapt them to your business and your real response times.
Missing information. For example, on the site of a fictional bike shop:
Visitor: Is my e-bike compatible with a 2019 battery?
Assistant: I can't find that in our documentation, and I'd rather not guess. Leave your email and bike model, and one of our team will reply within one working day.
Request for a person.
Visitor: I want to speak to a real person.
Assistant: Of course. Here is a short form: add your email and your question, and the team will reply within one working day.
Problem to investigate (ticket).
Assistant: Here is the summary of your issue as I understood it. Please read it, correct anything that's off, then confirm: it goes to our team together with your order reference.
Sensitive topic.
Assistant: This is something only our team can handle. I can offer you a slot to discuss it directly: here are the available times.
Three rules apply to all of them: acknowledge the limit without over-apologizing, state the real response time (not "very soon"), and say what happens next.
What to Measure Afterwards
A well-tuned handoff is steered with a few simple indicators. Formulas and reference points are in our guide to ticket deflection; here is what matters for this topic.
- Form completion rate: of the visitors offered the form, how many send it? A low rate suggests too many fields or an unclear message.
- Unanswered questions: review them weekly. Each one is content to add to your knowledge base. Our guide to the questions customers ask a chatbot helps you anticipate them.
- Human response time: if you promise one working day, keep it. That is the promise visitors remember.
- Answers to review: in Heeya's Analytics tab, each answer carries a reliability indicator (for example "information probably not found"). It helps the owner spot answers worth checking and fill gaps in the knowledge base. It is a review aid, not a handoff trigger.
The goal is not to push handoffs down at any cost. It is to make sure the right cases reach your team with the right context, and that avoidable ones disappear as the knowledge base grows.
FAQ: Chatbot Human Handoff
How does a chatbot hand off to a human?
Depending on your setup, it can open a live conversation with an agent, show a contact form, create a support ticket or offer a booking. When nobody is online all day, the last three save the visitor from waiting.
What happens when a chatbot can't answer?
A well-built chatbot says so clearly, does not improvise, and offers an exit: form, ticket or booking. You then log the question and add the missing content to the knowledge base so the gap closes.
Do I need live chat to escalate to a human?
No. Live chat makes sense if a team answers in real time through the day. Otherwise a form wired to your CRM, a ticket or a booking is enough, as long as you state a realistic response time.
When should a chatbot hand over to a person?
Three main cases: the visitor explicitly asks for a person, the information is not in your knowledge base, or the topic is sensitive (complaints, personal data, legal, medical).
How do I stop customers repeating themselves to the agent?
Pass the context along with the request. A visitor-validated summary in a ticket, or a form prefilled when the visitor is identified on your site, avoids starting from scratch.
Must a chatbot say it is an AI?
It is good practice, and the EU AI Act (Article 50) sets a transparency obligation for systems that interact with people. State it in the welcome message, together with how to reach a person.
How do I know if my chatbot escalates too much or too little?
Look at unanswered questions and form completion. Many requests on documented topics point to an incomplete or poorly structured knowledge base; few requests despite uncertain answers suggest the exit is not visible enough.
Conclusion
Handing over to a human does not require a team online around the clock. A form wired to your CRM, a ticket with a validated summary or a booking on real slots cover most cases, and live chat remains the right answer for teams that respond in real time. What matters is that the visitor never gets stuck, and that every unanswered question improves your knowledge base. To see how these flows behave on your own content, the 7-day trial with no card required lets you test them.
