Customer service chatbot vs human handoff, when the bot should step back
A customer service chatbot should answer repeat questions and step back on three signals: the visitor asks for a person, it is unsure, or the topic is sensitive.
Try it on your own site, the bot is built from your pages in about a minute
A customer service chatbot should handle repeat questions on its own and hand the conversation to a person on three signals: the customer asks for a human, the bot is not confident, or the message touches a sensitive topic such as a refund or complaint. Getting those rules right matters more than the model.
The debate is often framed as bot versus human. In practice the best support teams use both, and the quality of the service is decided at the moment one passes the conversation to the other. This article explains where that line should be and how to make the handoff feel seamless to the customer.
What the bot should do and what people should do
| Conversation type | Bot | Person |
|---|---|---|
| Policy and how to questions | Answers with a link to the source page | Not needed |
| Order status | Looks up the order through your API | Only if the order is stuck |
| Troubleshooting with documented steps | Walks through the steps from your help articles | When the steps fail |
| Refunds, disputes, complaints | Acknowledges, collects details, opens a ticket | Decides and replies |
| Questions your content does not cover | Says it is unsure, offers a person | Answers, then the content gets updated |
| Upset or confused customers | Offers a person early | Takes over |
The pattern is simple. Anything that has one correct answer written somewhere belongs to the bot. Anything that needs judgment, discretion or empathy belongs to a person.
The three handoff triggers every bot needs
The customer asks for a person
Phrases like "talk to someone", "real person" or "call me" should end the bot's attempts immediately. Nothing frustrates a customer more than a bot that keeps answering after they asked for a human. ChatBotWidget recognizes these requests and moves the visitor to handoff straight away, collecting an email so your team can reply.
The bot is not confident
When the retrieved content does not answer the question, the bot should say so honestly and offer the team. A guessed answer is the most expensive mistake in customer service, because the customer acts on it. Low confidence handoff is on by default in ChatBotWidget.
The topic is sensitive
Some topics should reach a person even when the bot could technically answer them: refunds, chargebacks, cancellations, legal threats, safety issues, complaints about staff. You define these as a keyword list in the bot settings. A message containing any of them goes to handoff without an attempt to answer.
What a good handoff looks like
A handoff is not a dead end with a contact form. A good one has four parts.
- The customer knows what happens next. "A member of the team will reply to you by email" is better than "Please contact support".
- Contact details are collected once. The bot asks for an email in the chat, so the customer does not fill in a separate form.
- The team sees the whole conversation. The handoff lands in the inbox with the history, the question and the reason for the handoff (visitor request, keyword or low confidence).
- Somebody actually replies. Set a response time your team can keep, and say it in the greeting or the handoff message.
In ChatBotWidget, handoffs land in the panel inbox. If your team works in a helpdesk, the create ticket action sends the case to it through a webhook, so it appears in the queue your agents already use.
Handoff vs ticket, two ways to pass the baton
The two are related but not the same, and it helps to use both.
| Handoff | Ticket action | |
|---|---|---|
| Triggered by | Request for a person, low confidence, keyword | The bot deciding a case needs follow up |
| Lands in | Panel inbox with the conversation | Panel inbox or your helpdesk through a webhook |
| Typical use | Questions the bot cannot answer | Known processes such as a return request or a fault report |
| Details collected | Email and the question | The fields you define, such as order number and problem |
Measuring the balance
Two numbers tell you whether the line is in the right place.
- Handoff rate. The share of conversations passed to a person. If it is very high, your content has gaps or the keyword list is too broad. If it is close to zero, check that the bot is not guessing.
- Unanswered questions. The list of questions the bot could not answer from your content. Each one fixed in your content lowers the handoff rate for good.
Read a sample of handed off conversations every week. If the person who took over answered from a page that exists, the bot should have found it: check whether the page is in the knowledge list. If the answer was not written anywhere, write it down on the site, and the next customer will get it from the bot.
Mistakes that make customers hate support bots
- Hiding the way to a person behind several questions.
- Letting the bot answer refund and complaint messages with policy quotes.
- Handing off into a queue nobody reads at weekends without saying so.
- Asking the customer to repeat everything after the handoff.
- Pretending the bot is a person. Name it as an assistant and let it be good at what it does.
Handoff rules differ by industry
The three triggers apply everywhere, but the keyword list changes with the business. An online store flags refund, damaged, chargeback and missing parcel. A software company flags cancel, data deletion, security and outage. A clinic flags emergency, pain, side effect and prescription, and should tell the visitor to call emergency services where appropriate. A law or finance firm flags almost every case specific question, because general information is fine but advice on a particular situation belongs to a qualified person. Write the list with the people who handle these cases every day. They know which words signal trouble long before a customer says "complaint".
Writing handoff messages that keep trust
The wording of the handoff decides whether the customer feels helped or dismissed. Three short examples show the difference.
| Situation | Weak message | Better message |
|---|---|---|
| Bot is unsure | "I cannot help with that." | "I could not find that on our site. Leave your email and a member of the team will reply." |
| Customer asks for a person | "Please use our contact page." | "Of course. Leave your email here and someone from the team will reply to you directly." |
| Refund request | A quote from the refund policy | "I will pass this to the team so they can look at your order. What is your order number?" |
The better messages share a pattern: they acknowledge the request, say who will act and ask for the one detail the team needs. Nothing more.
Handoff outside office hours
A handoff at eleven at night will not get a reply at eleven at night, and that is fine as long as the customer knows. Add your reply times to the handoff instructions, for example "We reply on weekdays between nine and five", so the bot can tell the customer what to expect. Customers accept waiting when they know how long. What they do not accept is silence after being promised a person.
For businesses with weekend demand, a rota of one person checking the inbox twice a day often covers most handoffs. The bot handles the repeat questions in between, which is exactly what makes a small rota enough.
Setting up handoff in ChatBotWidget
- In the bot settings, keep "hand off when unsure" and "hand off on request" switched on.
- Add your sensitive keywords, separated by commas, for example refund, chargeback, cancel, complaint, lawyer.
- Make sure the panel inbox has an owner, and invite them as a team member.
- If you use a helpdesk, add a create ticket action with its webhook address.
- Test with the three triggers in the test chat before going live.
For the full product view, see the customer service chatbot page and the AI customer support chatbot page for documentation heavy teams. If the bot is not installed yet, the guide on adding a chatbot to your website takes a few minutes to follow.
Frequently asked questions
Can a chatbot replace customer service staff?
It can take over repeat questions with documented answers, which frees staff for cases that need judgment. It should not replace the people who handle refunds, complaints and unusual problems.
When should a chatbot transfer to a human?
When the customer asks for a person, when the bot cannot find the answer in your content, and when the message contains a sensitive topic you flagged, such as a refund or complaint.
Where do handed off conversations go?
Into the inbox in your ChatBotWidget panel with the full history, or into your helpdesk through a ticket webhook if you prefer to work there.
Does the customer have to repeat the question?
No. The person who takes over sees the whole conversation and the reason for the handoff, so they can answer directly.
Can I turn off handoff on some topics?
Yes. Each trigger can be switched on or off per bot, and you control the keyword list yourself.
