Designing an "I don't know" that doesn't lose the user
The hardest state for an AI assistant is the moment it has no answer. Design that moment badly and every bit of trust you built disappears with it.
Every team building a chatbot spends its time on the happy path: clear question, precise answer, satisfied user. That path is a smaller share of real traffic than you would guess. What determines whether people come back is how the system behaves when it has nothing to say.
Three ways to fail
- Invent an answer — the worst option. The user cannot tell, and acts on something false.
- Apologise and stop — "Sorry, I can't help with that." A dead end with no next step.
- Deflect vaguely — "Please contact support" without saying how.
What we do instead
When no chunk clears the confidence threshold, the agent shows three things at once: a plain admission that it does not know, the nearest topic it does have material on, and one specific control that reaches a human. None of the three is sufficient on its own.
Users do not get angry that the system did not know. They get angry that they got stuck.
Those unanswered questions are also the most valuable product data you will collect. We group them and surface the clusters in the dashboard as knowledge gaps — a to-do list which, once worked through, means the answer exists next time.