What should happen when a chatbot can't answer

Every chatbot eventually hits a question it can't answer

This is not a flaw. It's inevitable. No chatbot, however well-trained or carefully built, has been given every possible piece of information about every situation. Your company's knowledge base has gaps. Your documentation doesn't cover every edge case. Your internal systems don't contain every answer. What actually matters is not whether a chatbot ever reaches a question it can't answer. What matters is what happens next.

The bad version: a dead end

You've asked your chatbot a genuine question. It searches through what it knows. It finds nothing that fits. And then this happens:

And that's it. Nothing else. No suggestion for what you should do instead. No way to ask someone who might know. No offer to escalate. Just a wall, and you're back where you started, except now you've also spent time getting nothing.

This is worse than it seems. You didn't just fail to get an answer. You got confirmation that nobody's set up a system to handle your question when it falls outside the standard FAQ. You're stuck, and stuck quietly. You might email support hoping someone sees it. You might give up and try a different product. You might make a guess and hope it's right. The chatbot has created a problem, not just failed to solve one.

The good version: a real handoff

Same situation. Same question the chatbot can't answer. But this time:

Notice what changed. The chatbot still admits it doesn't know. But it also gives you a specific next step. An actual email address or ticket system you can use right now. A timeframe for getting a real answer. You're not stuck anymore. You have a path forward.

The honesty ("I don't know") and the handoff (a real path forward) both have to be there. Either one alone isn't enough. Honesty without a handoff leaves you abandoned. A handoff without honesty might send you toward a resource that can't actually help either, just with more layers of confusion.

Why guessing is worse than saying "I don't know"

Here's the temptation: a chatbot could try to guess. Maybe the answer is probably yes, based on how similar features work. Maybe it's unlikely the question matters for your use case anyway. Why not offer something instead of nothing?

Because a chatbot that guesses instead of admitting it doesn't know creates a worse outcome than any dead end. You don't just fail to get information. You get false information, delivered with confidence. You act on it. You make decisions based on it. You maybe move forward with a project or a workflow or a configuration that won't actually work.

That bad answer doesn't get discovered immediately. It gets discovered later, when it's more costly to fix. When you've already gone down a path that doesn't work. When you've wasted more time and possibly money. When you've lost trust in the system that misled you.

Being honestly stuck is recoverable. You reach out to a real person and get unstuck. Acting on confident wrong information often stays hidden until the damage is already done. That's why a chatbot saying "I don't know" is actually the responsible choice, not the failure state.

What good escalation actually includes

When your chatbot doesn't know the answer, the handoff should have three things:

Immediate. Not making you ask twice. Not saying "you can contact support" and leaving you to find the support form. You get a clear path right now, in that conversation.

Specific. A real email address, not "contact our team." A link to actually open a ticket, not a vague reference to a system you'd have to hunt for. A phone number if that's available. Something you can actually act on in the next 30 seconds.

Honest about why. Briefly saying it's outside what the chatbot has been given information about, not just refusing vaguely. You understand it's not that the answer is secret or gatekept. It's that the chatbot genuinely doesn't have it.

How we handle this

When our agent can't answer something from the real material it has, it says so plainly and hands you off to a real person rather than guessing. That's a deliberate rule we test for, not something left to chance. We're not perfect at it, and we don't claim to be. But we'd rather say "I don't know" than guess. That's the rule we've built and the one we hold the agent to.

You get to decide if that's good enough

The real test of how a chatbot handles failure is whether you'd rather have it in the first place. If a chatbot that admits when it doesn't know and hands you to real help is more useful than no chatbot at all, then the tool is working. If it's creating more friction than it's solving, then it shouldn't exist.

We built this one because we think admitting limits and actually connecting you to someone who can help is the whole point. Not because we solve every question. Because we solve the questions we can, get out of the way on the ones we can't, and do our best to make sure you're not left stranded.