Hallucination
An AI model confidently generating false information, the single biggest production risk for customer-facing AI, mitigated by grounding, guardrails, and supervision.
A hallucination is what happens when a language model generates an answer that sounds correct but is not true. The model invents a citation that does not exist, quotes a price that is wrong, references a policy the company never wrote, or attributes a quote to a person who never said it. The output reads with the same confidence as a correct answer because the model has no internal signal for "I do not actually know this." Probability over the next token is the only thing the model optimizes, and probable text is not the same as true text. Hallucination is the defining failure mode of language models in production.
Hallucinations cause real damage in customer-facing roles. A support bot that invents a refund policy creates a refund obligation the company never agreed to. A sales agent that quotes pricing the model imagined leads to deals priced wrong. A medical-adjacent assistant that invents a drug interaction creates legal liability that no insurer wants to underwrite. This is why every production AI system at funded scale layers three defenses. Grounding via RAG forces the model to answer from retrieved source documents instead of training-data recall. Guardrails filter outputs against hard rules before they reach the user. Human supervision catches what the first two layers miss and feeds corrections back into the loop.
No production stack eliminates hallucinations entirely. The honest goal is to push the rate low enough that the remaining failures are caught by review before reaching the customer. The AI Support Department and AI Sales Department both ship with citation-required output, confidence scoring on retrieval, and human review queues for low-confidence answers. Teams that skip these layers and deploy raw LLM output to customers learn the lesson the expensive way. The hallucination problem is the reason "we built an AI chatbot in a weekend" rarely survives contact with paying customers.
- A support bot without RAG tells a customer they qualify for a refund under "section 4.2 of our policy," a policy section that does not exist in the company terms.
- A research assistant cites a 2021 Stanford paper that the model invented, complete with plausible author names and a fake DOI, before a reviewer catches the fabrication.
- A sales engineering copilot quotes a competitor integration the product does not actually support, because the model pattern-matched on similar SaaS feature sets in training data.
Why do language models hallucinate at all?
Does RAG eliminate hallucinations?
How do I detect hallucinations in production?
Which models hallucinate less?
EOI runs fractional AI departments for funded teams under 50. Sales, Content, Ops, Support. Live in 14 days on a monthly retainer.