How it works
Why Most AI Chatbots Hallucinate (and How RAG Fixes It)
Here's a scenario that's probably happened to you as a customer, even if you didn't clock it at the time: a chatbot answered your question fast, sounded completely sure of itself, and was wrong. Maybe it quoted a return policy that doesn't exist. Maybe it gave you a phone number that just rings out. Either way, you trusted it a little less afterward — and so did the company that put it there.
That failure has a name (hallucination) and a specific, fixable cause. Worth understanding if you're about to put one of these on your own site.
Why a language model makes things up in the first place
A model like GPT or Gemini doesn't "look up" answers. What it actually does, underneath the conversation, is predict the next most likely word, then the next, then the next — based on patterns it picked up during training. There's no little voice inside going "wait, I'm not sure about this one." It just keeps predicting, fluently, whether or not the thing it's saying is true. Fluency and accuracy aren't the same job to the model, even though they look identical from the outside.
For a general chat assistant, that's a reasonable trade. Nobody expects ChatGPT to know your company's internal refund policy. But drop that same model behind a chat bubble on your pricing page, let it answer as if it speaks for your business, and the trade stops being reasonable. Say your refund window is 14 days. Most companies use 30. Ask a generic model and there's a real chance it tells your customer 30 — not because anything broke, but because that's the statistically likely answer given everything it's ever read.
What retrieval-augmented generation changes
RAG doesn't make the model smarter. It changes the question you're asking it. Instead of "what's the answer to this," the system asks "here are the actual passages from this company's docs — summarize what they say." That's a much smaller, much safer job. The model isn't recalling anymore. It's reading and paraphrasing something that's sitting right in front of it.
Retrieve
Search your indexed content
Augment
Inject the exact passages found
Generate
Write a grounded reply
Three moving parts, run fresh on every message a visitor sends. Retrieval turns the question into a search over your indexed content — your docs, your PDFs, your site — and pulls back the handful of passages that actually match. Augmentation drops those passages straight into the prompt, along with an instruction to stick to them. Generation is the model writing the reply — grounded in what it was just handed, with permission to say "I don't know" if the passages don't actually cover it.
Same question, two very different setups. Here's the difference in practice:
“What's your refund window?”
“Most companies offer a 30-day refund window, so you should be covered if it's within that period.”
Sounds confident. Company policy is actually 14 days.
“What's your refund window?”
“You can request a refund within 14 days of purchase — see our refund policy page for the exact steps.”
Pulled directly from the policy page it was trained on.
Want to check if a chatbot is doing this for real? Ask it something you know isn't on your site — a competitor's pricing, a feature you haven't built yet. A properly grounded bot will say it doesn't know. One that's just a model with your logo on it usually won't resist guessing.
RAG helps a lot. It doesn't make hallucination impossible
Worth being honest about this part, since it's easy to oversell. Three ways a "RAG-powered" chatbot can still go wrong:
- The search step misses. If retrieval pulls the wrong passages — bad chunking, or a question phrased differently than the docs — the model is still grounded, just in the wrong material. Garbage in, confident garbage out.
- Nobody told it "I don't know" is allowed.Some setups retrieve context but never explicitly permit the model to admit a gap. Under pressure to sound helpful, it'll stitch together a guess from whatever partial context it has rather than say so.
- The index is stale.Changed your pricing last week and the crawler hasn't run since? It'll confidently, grounded-ly quote you the old number. Being grounded only helps if what it's grounded in is current.
What's actually worth checking before you trust one
Doesn't matter which platform — Ontroz or anyone else's. Same three questions apply. Does it search your content before answering, or is it just a general model wearing your branding? Is there a real, visible fallback for questions it can't cover? And how often does the index actually refresh?
Ontroz answers only from what you've trained it on — your site, your docs, your PDFs — and falls back to a message you write yourself (usually a way to reach a human) instead of guessing when something falls outside that. If you'd rather see it than take my word for it, the free chatbot demo tool builds one from your homepage in under a minute. No account needed.
See it work on your own content
Train a chatbot on your site or docs and get an embed code in under 5 minutes. Free plan available, no credit card.
Build your chatbot free