What should a support chatbot do when it doesn't know the answer?
Quick answer
It should share what it does know, say plainly what it doesn't, offer to pass the question to a person, and ask where that person can reply. It shouldn't guess, and it shouldn't promise a reply time nobody set. If the customer asks for a person at any point, it should hand over straight away.
A chatbot that hands over too often is a smaller problem than one that guesses. A handover costs you a reply. A guess can cost you a refund, a chargeback or a review, and the customer never knows it was a guess.
Why a chatbot that guesses costs more than one that says "I don't know"
An AI chatbot writes the most likely answer, even when the real one isn't in what it was given. To a customer, a confident wrong answer about a refund reads exactly like a right one.
The business owns those words. In February 2024, a Canadian tribunal held Air Canada responsible for all the information on its website, its chatbot included, after the chatbot described a refund rule that the airline's own policy page contradicted (Moffatt v. Air Canada, 2024 BCCRT 149; a small-claims tribunal decision, not binding precedent).
Customers notice the other half of the problem too. In a Gartner survey of 5,728 customers in December 2023, 64% said they would prefer companies didn't use AI for customer service, and their top concern was that it would get harder to reach a person. Gartner's advice was that chatbots tell customers they will connect them to an agent when the AI can't solve the problem.
What a good "I don't know" from a support chatbot looks like
I build AI support agents, and our own testing caught ours getting this wrong. In October 2026 we tested it on a real store's public pages, in a test account. Asked whether an order placed on December 18, 2026 would arrive before Christmas, it called December 18 a Monday (it's a Friday), said it should arrive on a Sunday, a day the store doesn't deliver, and didn't offer a person.
After we fixed it, the same question got the store's own shipping days, no date, and this: "I can pass this to our team so they can confirm the exact date for you. Would you like me to do that?"
That second answer gives what it does know, names what it can't confirm, and lets the customer choose whether a person follows up.
Checklist: what a support chatbot should do when it doesn't know the answer
Use this for any support chatbot, whoever makes it.
- Admit it specifically. "I don't have your discount code details" is better than "I can't help with that."
- Offer a person each time it can't answer, and stop offering once the customer says no.
- Hand over at once when asked. "Can I talk to a real person?" should never get one more try at an answer.
- Stop asking after three tries. Siemens' conversational design guidelines say a chatbot shouldn't ask for clarification more than three times before handing off.
- Collect a reply address inside the chat, so the customer doesn't have to start again somewhere else.
- Send the whole conversation along, so nobody asks the customer to repeat themselves.
- Promise only times you've set. If you haven't set a reply time, it shouldn't name one.
- Make sure the question reaches you, somewhere you actually look: your email, usually.
- Fix the source. When the same question gets handed over twice, write the answer on a page the chatbot reads. Then it knows next time.
How to test whether a chatbot admits it doesn't know
Ask it five questions before customers see it:
- A question your pages answer. It should answer.
- A question your pages don't answer, such as a discount code. It should say so and offer to pass it on.
- "What exact day will my order arrive?" Check every date and weekday it gives against a calendar and your written cutoffs.
- A refund question. Compare the answer word for word with your policy.
- "Can I talk to a real person?" It should ask for an email address you can reply to, and the message should reach you.
If question 2 or 3 gets a confident made-up answer, don't put it in front of customers.
When handing the customer to a person isn't enough
A handover only works if someone reads it. If nobody will answer handed-over questions for days, say how long it takes in the chat's reply, or use a contact form with an honest reply time. A promise to "get back to you" that nobody keeps is a broken promise too.
DeskClone AI: an AI support agent that says when it doesn't know
We make DeskClone AI, so read this part with that in mind. It builds an AI support agent from your own website. Your agent answers only from what you've written. When it can't, it says so, offers to pass the question to you, and you get it by email with the conversation. You can read every conversation and switch it off anytime. It's on the Shopify App Store and the Wix App Market, with a free plan of 10 conversations a month and no card.
FAQ
Ready to let DeskClone handle your support?
See DeskClone in action. Book a live demo or start on the free plan. DeskClone can be up and running today.
No credit card required. Setup takes minutes, not weeks.
Questions? Reach out at hello@deskclone.ai