Guide · Updated · 5 min
Should your support bot say “I don't know”?
Yes. An AI support assistant that admits when your docs don't cover a question is more useful than one that always has an answer. The refusals protect customers from invented answers, and they give you an exact list of the articles you still need to write.
Short answer
A support bot should say “I don't know” whenever your docs don't support an answer, then offer a person and record the question. Guessing feels helpful in a demo and costs you in production. A good refusal is short, honest, and useful: it says what it couldn't find, points to the closest article if there is one, and hands off with the conversation attached.
Why would you want a bot that refuses?
Because the alternative is a bot that guesses, and guesses about your product sound exactly as confident as facts. A customer can't tell an invented plan limit from a real one. They act on it, it turns out to be wrong, and now you have a refund conversation instead of a support question.
A refusal costs one handoff. A confident wrong answer costs the customer's time, possibly their money, and their trust in every future answer. For product support, “I don't know” is the cheaper outcome by a wide margin.
Why do support bots guess in the first place?
Language models are built to produce a plausible answer, not to check whether your docs support it. When retrieval comes back with nothing relevant, a model without a refusal rule fills the gap with what similar products usually do, or with what sounds right. Why Docs Chatbots Hallucinate (and How to Stop Them) covers the mechanics.
The fix isn't a cleverer prompt. It's a rule enforced in the system: answer only from retrieved sources, and when the sources are weak or missing, refuse.
What does a good refusal look like?
A good refusal is short, honest, and still useful. It says the docs don't cover the question, points to the closest related article if one exists, and offers a person, ideally without making the customer repeat themselves. Compare two answers from Ledgerloop, the invoicing SaaS we use in examples:
| Bad: a guess | Good: an honest refusal |
|---|---|
| “Yes, you can bill clients in multiple currencies from Settings, Billing.” | “I couldn't find anything in our docs about billing in multiple currencies, so I don't want to guess. Here's how currency works on invoices today: Set your invoice currency. Want me to pass this to the team?” |
The good version admits the gap, still gives the customer something relevant, and keeps the conversation moving.
When should a bot refuse?
A bot should refuse when no retrieved article supports the answer, when the sources conflict, and when the question needs account data or a decision it shouldn't make. Everything else, documented and the same for every customer, it should answer with a link to the source.
- No relevant source found: refuse and hand off.
- Sources found but they don't actually answer the question: refuse, link the closest article.
- Sources conflict: say so, link both, hand off.
- Account specific question (a charge, an outage affecting them): hand off.
- A decision (an exception, a discount, an extension): hand off.
Won't refusals make the bot look bad?
Only if it refuses things the docs clearly cover, or refuses without helping. A bot that answers documented questions well and declines the rest earns trust quickly, because customers learn that when it answers, it's right. A bot that answers everything teaches customers to double check everything, which defeats the point.
If refusals are frequent, that's not a bot problem. It's a docs problem, and a precise one: the refused questions are the articles you haven't written yet.
How do you tune when the bot refuses?
Tune with real questions, not settings. Take recent tickets, including some your docs don't cover, and check two things: does the bot answer every covered question with the right source, and does it decline every uncovered one? If it refuses covered questions, the article is probably hard to retrieve (vague title, answer buried, wrong vocabulary). If it answers uncovered ones, the refusal rule is too loose.
| Symptom | Likely cause | Fix |
|---|---|---|
| Refuses a documented question | Article hard to find | Retitle in customer words, answer up top |
| Answers an undocumented question | Refusal rule too loose | Require a supporting source |
| Cites the wrong article | Two articles overlap | Merge them or sharpen headings |
| Refuses a lot overall | Docs are thin | Write the refused topics |
How do refusals become better docs?
Every refusal is a question your docs couldn't answer, in the customer's own words. Collect them, group them by the article that would have answered them, rank by how often they come up, and write the top ones. Within a few weeks, the bot refuses less because the docs cover more. How to find what's missing from your help center walks through the grouping.
This is the part most teams skip. They tune the bot to refuse less, which means guessing more, instead of writing the missing articles, which means answering more, correctly.
How does usedocs handle refusals?
The usedocs assistant answers only from your published articles and links the source on every answer. When the match is weak, it says the docs don't cover the question instead of guessing, and offers a handoff to your team by email, with alerts in Slack, Discord, or Teams. Each refused question becomes part of a ranked gap with a drafted article, so the next customer who asks gets an answer.
FAQ
Should an AI support bot ever guess?
Not about your product. It can be friendly and general about how to phrase a question, but facts about features, limits, and prices should come from your docs or not at all.
How often should a good support bot refuse?
It depends on how complete your docs are. A rising refusal rate after launch is normal; it should fall as you write the articles the refusals point to.
What should happen after a refusal?
Offer a person, pass along the conversation, and record the question so it can become an article.
Do citations make refusals unnecessary?
No. A bot can cite a page that doesn't actually support its answer. Citations make answers checkable; refusals stop the answers that shouldn't exist.
Will customers be annoyed by “I don't know”?
Less than by a wrong answer. A refusal that still points to a related article and offers a person usually lands well.