A chatbot keeps trust only while its answers stay accurate and honest. Once it is unsure, money is involved or someone asks, it should pass the customer to a person.
Rising frustration belongs on that list. So does disclosure: several states now require many bots to disclose they are not human.
The handoff from bot to person works best when the agent picks up the conversation with its full history in view.
The handoff to a person is where that trust is won or lost. A bot that solves the problem is deflecting demand. A bot that hides the exit is protecting a queue, and customers notice.
Disclosure is also becoming a legal duty. Cooley notes that Maine’s Chatbot Disclosure Act, in force since September 24, 2025, requires businesses to tell consumers they are not talking to a live human whenever a reasonable consumer could not tell the difference.
I would treat that duty as the floor. Above it sit the harder calls, such as when a wrong answer, a frustrated customer or a billing dispute should end the bot’s turn.
A chatbot should stop talking and bring in a person once it can no longer move the customer toward a resolution. Nearly one-third of customer communication leaders have adopted chatbot technology or plan to, according to research by Chen and Gascó-Hernandez. Adoption is the easy part. Deciding where the bot ends and the person begins is the harder call, and it starts with an honest look at why bots answer wrongly.
Top 3 questions this article answers
- Why do AI customer service chatbots give wrong answers?
- How much customer support can a chatbot handle on its own?
- When should a chatbot hand a customer to a human agent?
Why do support chatbots give wrong answers?
Support chatbots give wrong answers when they work beyond a narrow scope, rely on thin or stale knowledge, and state guesses as flatly as facts.
- Scope: list the few jobs the bot may finish, and route everything else to a person.
- Knowledge: confirm that the documents it answers from are current before you blame the model.
- Over-assertion: read sample transcripts for confident claims that no source supports.
Forrester noted in 2017 that Facebook had reported its chatbots failing 70% of the time, and it named an undefined purpose among the main reasons. Stale knowledge does similar damage, because a bot can only answer from the documents it was given, so an AI customer support assistant should draw only on content your team keeps current.
Over-assertion is harder to spot. In an experiment reported by the Linguist in the Wild Substack in August 2026, Roz Hirch asked ChatGPT and Claude for “some book or reading.” Both returned long lists stated as flat assertions, while the people she asked generally offered 1 title, often hedged with “I think.”
The stakes are significant. A peer-reviewed study published on PubMed Central on 9 February 2026 found that cognitive trust in support chatbots rests on accuracy, transparency, responsiveness and data security.
Read together, these sources point to one flaw: nothing tells the bot to stop. Each cause above is a design choice, not a model limit. After two decades in customer engagement and support outsourcing, I judge a bot by whether it knows where its competence ends. When it cannot tell, the signal to stop must be built around it.
Accuracy is one of the foundations of customer trust in a support chatbot, and it starts with the content the bot is allowed to draw on.
How much of the workload can a chatbot realistically carry?
A chatbot can realistically carry simple, repeatable jobs such as account actions, policy look-ups and order updates, measured by resolved contacts rather than by how many it keeps from people.
Adoption has outrun value. Call Centre Helper’s 2025 research found chatbot use at 49% of contact centres, up from 43% a year earlier, yet only 8% of leaders picked chatbots as their best value for money in customer experience.
The same research names the jobs a bot can complete on its own:
- simple account actions
- policy look-ups that draw on live data
- order and delivery updates
That research also argues for judging a bot on resolution rate rather than containment, since containment without closure “simply shifts cost downstream.”
A practitioner in a June 2026 r/CustomerSuccess thread proposed a sharper test: if 40% of chats end in “talk to a human,” the problem lies in upstream content or product friction, not in the bot.
The trade-off is real. A tightly scoped bot looks weaker on a dashboard because it passes more conversations to people. I would still accept that over a queue of customers who return angry.
Which four signals mean it is time to bring in a person?
Bring in a person when the bot is failing, the customer is frustrated, money or regulated matters arise, or someone asks for a human.
Bots rarely notice their own limits. Each signal should therefore be written in as a rule.
- Uncertainty or repeated failure: One chatbot vendor, NineTen, advises escalating once the bot has failed “within two or three tries.”
- Frustration: Forrester observed in 2019 that customers grew more frustrated when a failing bot offered “no easy escalation to a human for help” within the same session.
- Money, accounts or regulated topics: Wiley Law notes that Utah requires licensed professionals to disclose generative AI use at the start of any “high-risk” interaction involving healthcare, law or finance.
- An explicit request or distress: A typed request for a person should end the automated flow, and signs of distress should end it at once.
| Trigger | What you will see | What the bot should do |
|---|---|---|
| Uncertainty or repeated failure | Off-target answers, or the same question asked again | Admit it cannot resolve the issue and offer a person |
| Frustration | Rephrased questions, sharper wording, complaints about the bot | Transfer in the same session with the conversation attached |
| Money, accounts or regulated topics | Charges, refunds, account changes, health, legal or financial questions | Say it is automated and route to a qualified person |
| Explicit request or distress | A typed request for a person, or signs of a personal crisis | Transfer at once and, for distress, point to crisis help as well |
Each trigger helps only if the person who takes over can see what has already been said, which is what keeping the human touch in AI customer service depends on.
Where is the bot-to-human handoff heading next?
Handoffs are moving from judgment calls to fixed triggers: a request for a person, rising frustration, money or regulated questions, and a legal duty to disclose the bot.
Cooley reports that at least six states enacted new AI chatbot laws in 2025, and California’s SB 243 allows $1,000 per violation. Bots used only for customer service are exempt from its companion chatbot definition, but I would not lean on that exemption.
In summary, a narrow scope, honest resolution figures and four clear triggers decide whether a bot earns that trust. This week, ask your own chat widget for a person outside staffed hours. Then time how long a human takes to reply, and make that wait the next number you fix.
Frequently Asked Questions
What else do people ask about chatbot handoffs?
Readers who run support teams, and readers stuck in a bot loop, tend to ask the same few things about when a chatbot should step aside.
Should a chatbot transfer the moment a customer asks for a person?
In most cases, yes. In a June 2026 r/CustomerSuccess thread, one practitioner called every extra loop after an explicit request “a trust tax you pay later in churn or angry tickets.” I agree once a customer has plainly said what they want.
Can a chatbot replace human support agents?
Not for most teams, in my judgment. A 2019 analyst report urged brands to augment their agents instead, with bots that gather context before a handoff or suggest replies an agent can send with one click. The same report found that most customers would rather call a contact center than sit through a poor chatbot interaction.
What should a bot say when no person is available?
The truth, with a time attached. In a 2025 r/mildlyinfuriating thread about a bot that refused a handoff, 5 of 8 comments blamed contact outside staffed hours. I would also capture a callback number or email address so the request survives the night.
Written by
Michael Kansky
Founder at LiveHelpNow
Michael Kansky is a serial entrepreneur, software founder, and AI-driven business operator with more than two decades of experience building companies at the intersection of customer engagement, automation, software, digital services, and data-driven growth.