How do you stop a voice agent from inventing answers?

Ground it in a real knowledge source, keep its scope narrow, and give it explicit permission to say it does not know instead of guessing.

An admin approves every new account by hand. Nothing is created until then. We reply by email; no newsletter, no sequence.

app.salescrew.io/inbox
The unified reply inbox with classified threads

The short answer

  • A voice agent inventing plausible but wrong answers is the same failure as hallucination in any language model: a fluent response with no verified source behind it. Voice makes it worse, because the caller hears it stated confidently in real time.
  • Grounding the agent's answers in a real knowledge source, a documented FAQ, a product spec, real pricing, cuts invented answers a lot compared with letting the model answer from general training alone.
  • Restricting the agent's scope, defining clearly what it is and is not expected to answer, reduces the surface area where it might reach beyond what it knows.
  • None of this fully works without explicit permission to say 'I don't know' or 'let me connect you with someone who can help'. A model without that option will often produce its best guess rather than admit uncertainty.

Why this matters more on a phone call than in a chat window

A chatbot that states something incorrect leaves text on a screen. A person can pause on it, question it, or check it against another source before acting. A voice agent stating the same incorrect thing does so in the flow of a live conversation. It is delivered with the same confident tone whether it is right or wrong, and the caller has no visual cue that anything is off. That is why grounding and scope control matter more in voice than in most other AI interfaces. The format itself removes the natural pause a reader gets.

The fix starts with what the agent draws from when it answers. An agent connected to a real knowledge base, actual pricing, actual policies, actual hours, and told to answer from that source rather than general knowledge, produces far fewer invented answers. One relying on whatever the underlying model happens to know or assume produces more. Narrowing the agent's defined scope, being explicit about what topics it should and should not attempt, further reduces the chance it wanders into territory where no real source exists.

What reduces invented answers

TechniqueWhat it does
Grounding in a real knowledge sourceAnswers pull from documented facts rather than general model knowledge
Narrow, defined scopeReduces the surface area where the agent might guess
Explicit permission to say 'I don't know'Gives the model an honest alternative to a confident wrong answer
Escalation path to a humanConverts an uncertain moment into a handoff instead of a guess

What to check before trusting a voice agent with real callers

Test the agent with questions genuinely outside its knowledge source and see what it does. Does it admit uncertainty and offer a next step, or produce a confident-sounding guess? Review a sample of real call transcripts periodically. Look for moments where the agent stated something as fact that was not verifiable from its source material.

Disclosure: SalesCrew is our product, and voice agents are on our roadmap and not shipped today. This page describes general practice for evaluating any vendor's voice AI rather than a SalesCrew feature. The knowledge base pattern described here, grounding, scope, and honest uncertainty, is the standard worth holding any voice agent to.

A confident wrong answer is worse than an honest 'I don't know'

A caller cannot tell the difference between a correct answer and a fluent invented one just by listening. Test explicitly for what the agent does when it does not know, and treat that as a core evaluation criterion, not an edge case.

Questions

Is this the same problem as hallucination in a chatbot?
Yes. The mechanism is the same: a language model generating a plausible-sounding answer with no real source behind it. Voice makes the problem more visible. A caller hears a confident wrong answer in real time rather than reading text they might double-check.
Does grounding the agent in documentation fully solve it?
It reduces the problem a lot but does not eliminate it. A model can still misapply or misread a real source. Combining grounding with explicit permission to say 'I don't know' catches more cases than grounding alone.
Should the agent guess if it is close but not certain?
No. A wrong but confident-sounding answer is worse than the agent admitting uncertainty and offering to connect the caller to a human or follow up. The caller has no way to know the agent is unsure unless it says so.