Because the most dangerous AI answer is not an invented one. It is a true fact that quietly expired, and this article answers the question most business owners never think to ask: how do you know when your AI is reading something that used to be right?
Suggested SEO meta title tag: AI Gave a Customer the Wrong Price? Fix Expired Facts
Your AI Is Not Lying to You. It Is Quoting You.
Here is the sentence that has been rattling around my head for two days. It came from a builder on r/AI_Agents who goes by u/codecoradev:
"Almost every wrong answer we've traced came from facts that were true when they were written and false by the time an agent reused them."
Read that again, and then think about the last time you raised a price.
Candidly, this one stung. Earlier this year I raised a price, updated the sales page, and felt good about myself. Three weeks later I found the old number still sitting in a proposal template, an old email sequence, and a PDF a client had downloaded. My AI assistant was not hallucinating when it quoted that number. It was reading. It was reading something I wrote, that was accurate the day I wrote it, and that I had forgotten existed.
So here is the direct answer to the question in the headline. Your AI gives customers outdated prices and policies because somewhere in your business a document, page, template or CRM field still holds the old version, and nothing in your setup tells the AI that the old version stopped being true. The fix is not a better model and it is not a better prompt. The fix is giving every customer-facing fact two things it almost certainly does not have right now: a date, and the name of the single place that holds the real version.
That is the whole thesis. Everything after this is how to actually do it.
Key Takeaways
- The AI failure that costs you money is rarely invented; it is a fact that was accurate when written and expired without anyone noticing.
- Research shows outdated evidence can override a model's correct answer, and the model delivers the stale version with full confidence.
- A date stamp alone is weaker than you think; models respond far better when told the condition under which a fact stops applying.
- Every customer-facing fact needs exactly one source of truth, and that source cannot be the AI itself.
- You own what your chatbot tells a customer, which a Canadian tribunal established in 2024.
The Problem Nobody Audits For
Everybody talks about hallucination. Hallucination is the fun failure. It is the AI inventing a court case, a citation, a statistic, a product that does not exist. It is embarrassing and it is obvious, which is exactly why it is the less dangerous one. You catch it. You laugh. You fix it.
Expired facts do not announce themselves.
An expired fact looks exactly like a good answer. It is specific. It has a number in it. It matches the tone of everything else your AI produces, because it came from your own material. When your assistant tells a prospect your turnaround is ten business days, there is no red flag, no hedge, no weird phrasing. It reads like competence. The only person who can catch it is someone who already knows the current number, which means the error travels straight past every reviewer who is not you.
And here is the thing about small businesses specifically. We are the worst-positioned people on earth for this problem, and it is not because we are sloppy. It is because our facts live everywhere. The price is on the sales page, in the proposal template, in the onboarding email, in the pinned post in the group, in last quarter's lead magnet, and in a Google Doc somebody made in 2024 that nobody has opened since. A company with a real data team has one system of record. You and I have eleven places and a vibe.
I am not going to pretend this is easy to fix. Auditing every piece of content you have ever published is not a realistic Tuesday afternoon. I have tried. You get four hours in, you find the old number in three more places, and you quit.
So we are not going to audit everything. We are going to audit the handful of facts that can actually cost you a customer or a refund, and put a system around those. That reframe is what made this tractable for me, and the research explains why it works.
What the Research Actually Shows
Four findings changed how I think about this, and one of them is genuinely counterintuitive.
First, stale documents can beat a model's correct answer. A preprint posted to arXiv in September 2026 by Md Shamim Ahmed and colleagues names the failure "stale-document poisoning." They built a benchmark of 317 verified knowledge reversals across medicine, law, software and platform policy, grounded in dated official sources. Outdated retrieval flipped 30 percent of Llama answers and 37 percent of Qwen answers with no instruction to trust the document. Tell the model to follow the document, which is what every "use my knowledge base" setup does, and those rates jumped to 66 percent and 75 percent. Matched up-to-date evidence was followed in 97 to 100 percent of trials. This is a preprint, not yet peer reviewed.
Second, and this is the counterintuitive part: a date alone is not enough. The same team kept the historical evidence identical across 50 reversals and changed only the evaluation date. Dates by themselves produced only modest adaptation. But when the models were explicitly told when the old evidence stopped applying, the larger ones switched to the correct answer almost perfectly. So "last updated March 2026" helps less than "this price was replaced on March 1, 2026." The expiration condition does the work, not the timestamp.
Third, stale text does not just confuse the model, it crowds out the truth. The HoH benchmark, published by Jie Ouyang and six co-authors in the ACL 2025 proceedings, measured what outdated information does to retrieval systems. Their result is the one I would tape to your monitor: even when current information was successfully retrieved, the mere presence of outdated information caused at least a 20 percent performance drop, with some models doing worse than random guessing. Models become "highly prone to generating confident but incorrect responses when encountering outdated information."
Fourth, the confidence is a design outcome, not a personality quirk. Adam Tauman Kalai, Ofir Nachum, Santosh Vempala and Edwin Zhang published work in Nature in May 2026 arguing that hallucinations persist largely because of how we score models. Nearly all major benchmarks use binary right-or-wrong grading, under which "I don't know" earns exactly zero, so guessing becomes a dominant strategy. Your AI sounds certain because certainty scores better than honesty.
Now the part that makes this concrete. In February 2024 the British Columbia Civil Resolution Tribunal decided Moffatt v. Air Canada. The airline's chatbot told a customer he could apply for a bereavement fare retroactively. He could not. The detail that should keep you up at night is that the chatbot's own answer hyperlinked to Air Canada's bereavement travel page, which said the opposite. The source of truth existed. The bot linked to it. The tribunal found Air Canada "did not take reasonable care to ensure its chatbot was accurate," called the argument that the chatbot was responsible for its own actions "a remarkable submission," and ordered it to pay C$812.02.
In July 2026, closer to our scale, SmartCompany reported that Australian company Who Gives A Crap suspended its AI customer agent after it confirmed a wrong price. One email had a typo: it said a toilet paper subscription was going from $66 for 48 rolls to $69.50 for 24 rolls, when the real new price was $69.50 for 48 rolls. The customer pushed back. The AI reassured them the wrong number was correct, and apologized for the "unclear messaging" while doing it.
One typo. One unsourced number. The AI defended it.
The System: Give Every Fact an Expiration Condition
Three products that launched on Product Hunt today are all selling the same thing, and it is not answers. It is evidence.
OfinTech Desk founder Mohammed Ahmed put the problem in one line: "Every finance team I've worked with asks the same question about every report: 'where did this number come from?' Most AI tools answer with confidence, not evidence." His architecture is the part worth stealing. "Deterministic code does the math, same input, same answer. A classifier makes closed decisions, with a measured probability. The AI only explains. It never invents a number." Click any figure and it opens the computation, the ledger rows, the document and the exact page.
Every Signal, built by Michael Jones, labels every figure as verified, estimate, inferred or rumour, because "I kept getting research that blended what was measured with what was guessed."
You do not need to buy those tools. You need to copy the posture. Here is the system I run, and it is five columns in one spreadsheet.
Column one: the fact, written exactly as a customer would hear it. Not "pricing info." The actual sentence. "The AI Insiders Membership is $247 a month." If you cannot write it as a sentence a customer would hear, your AI cannot say it correctly either.
Column two: the date you last personally verified it. Not the date the document was edited. The date a human laid eyes on it and confirmed it.
Column three: the single place that holds the real version. One place. Not two. If the price lives in both the sales page and the proposal template, one is a copy, and you write down which one is the original. This is the discipline u/open_is_free named in that same thread: a real check needs a source of truth that is not the agent, "otherwise the agent is grading its own homework."
Column four: the re-check date. Pick a cadence that matches how fast the fact moves. Price, quarterly. Service area, twice a year. Staff names, monthly if you are hiring.
Column five: the expiration condition. This is the column the research says matters most, and the one nobody builds. Not a date. A trigger. "This turnaround time is false if we add a second project to the queue." "This price is false the day the next cohort opens." You are writing the sentence that tells a future reader, human or machine, when to stop trusting the row.
Then the superseding rule, which u/codecoradev called embarrassingly low-tech, and which is the most valuable thing in this article. Every fact your AI may rely on lives as a dated entry. Answers cite which entries they used. When one entry turns out to be wrong, you re-check everything that cited it. No new software. A spreadsheet and a habit.
For tooling, keep it boring. A single Google Sheet as the ledger. A Claude Project or ChatGPT Project whose instructions say to answer customer-facing questions only from that ledger, and to say "I need to check that" when a fact is not in it. Then trim your knowledge base so old versions are deleted, not archived in the same folder, because the Ahmed research is clear that the stale copy sitting next to the current one is the whole problem.
Seven Steps to Build the Fact Ledger
-
List the five facts your AI is allowed to state to a customer. Price, turnaround time, guarantee or refund window, availability, and service area. Five, not fifty. If you cannot name them in two minutes, that is your first finding.
-
Find every place each one currently lives. Search your site, email platform, proposal template, CRM fields, pinned posts and Google Drive for the actual number. Write down the count. Most people find four to seven copies of their own price.
-
Pick the one that wins and delete the rest. Not archive. Delete, or rewrite it to point at the winner. An old version sitting in the same searchable folder as the new one is exactly the condition the research measured.
-
Build the five-column ledger. Fact, last verified, single source, re-check date, expiration condition. Fill the expiration condition column even when it feels obvious, because that is the column the model actually responds to.
-
Run this prompt to pressure-test it. Use the Perfect Prompt Framework 2.0 and fill in the brackets:
[The Job]
Create a fact ledger for the [NUMBER] statements my AI is allowed to make to a customer.
This is for: [MY BUSINESS NAME], a [TYPE OF BUSINESS] serving [WHO I SERVE].
It matters because: a customer who is quoted an expired price or an expired turnaround time will hold my business to it.
[The Background]
Here is what you need to know: my current customer-facing facts are [PASTE PRICES, TURNAROUND TIMES, GUARANTEE, AVAILABILITY, SERVICE AREA]. The places those facts currently live are [LIST EVERY PAGE, TEMPLATE, EMAIL, CRM FIELD AND DOCUMENT]. Today's date is [TODAY'S DATE].
Do not use: anything you know about my industry from training data, any benchmark or average, or any number I did not give you.
[The Deliverable]
Return: a table with one row per fact and five columns, the fact written exactly as a customer would hear it, the date I last verified it, the single place that holds the real version, the date it should be re-checked, and the condition that would make it false.
Must include: a flagged list of every fact that appears in more than one place, and every fact I gave you without naming a source.
Optimize for: accuracy.
[The Questions]
Ask me any questions you have.
-
Test your own assistant with the five questions. Ask it your price, turnaround, guarantee, availability and service area in a fresh chat with no context. Compare each answer to the ledger. Note which ones it got right for the wrong reason.
-
Put the re-check on a calendar, with a name on it. Not "review AI content." A recurring appointment titled "verify the five customer facts," owned by a specific human, with the ledger link in the body. Rachel Woods of AMP made the point this week that once nobody opens the screen, nobody looks.
Frequently Asked Questions
Is my business liable if my AI chatbot gives a customer the wrong price?
Assume yes. In Moffatt v. Air Canada, 2024 BCCRT 149, a British Columbia tribunal held the airline responsible for wrong bereavement fare information from its own website chatbot and rejected the argument that the chatbot was a separate entity. Commentators broadly treat a chatbot's statements as the company's own representations.
Does connecting my AI to my website fix outdated answers?
Only if the website itself is current and the old versions are gone. The Air Canada chatbot linked to the correct policy page and still gave the wrong answer. Research on outdated retrieval found that stale documents sitting alongside current ones degrade accuracy by at least 20 percent even when the current version is retrieved successfully.
How often should I re-check the facts my AI tells customers?
Match the cadence to how fast each fact actually moves. Prices and promotions quarterly, availability and capacity monthly, service area and credentials twice a year. HubSpot's own decay model puts business contact data at roughly 2.1 percent spoilage per month, which compounds to about 22.5 percent a year. That is a vendor model, not peer-reviewed research.
Why does AI sound so confident when it is wrong?
Because confidence scores better than caution. Work published in Nature in May 2026 by Kalai, Nachum, Vempala and Zhang found that nearly all major benchmarks use binary right-or-wrong grading, where "I don't know" earns zero points. Under that scoring, guessing is the dominant strategy, so models are trained toward certainty.
What is the simplest version of this I can do today?
Open a spreadsheet. Write your price, turnaround time, guarantee, availability and service area as full sentences a customer would hear. Next to each, put today's date and the one place that holds the real version. That ten-minute spreadsheet catches more real errors than any guardrail prompt you will write this year.
The Question You Should Be Asking
I opened with a price I raised and forgot to finish raising. I want to close there, because the lesson was not about the price.
The lesson was that I trusted my own material. I assumed that because I wrote it, and because it was true when I wrote it, it was still working for me. It was not. It was out there, in my own voice, with my own authority behind it, telling people something I no longer meant.
That is what an expired fact is. It is not the AI betraying you. It is your past self, speaking with perfect confidence, to a customer who has no way to know they are hearing from 2024.
So stop asking whether your AI hallucinates. That is the easy question, and you will catch those. Start asking the question Mohammed Ahmed says every finance team asks about every report: where did this number come from? Ask it about your price. Your turnaround time. The guarantee on your sales page. If the answer is "I think it's on the site somewhere," you do not have a source of truth. You have a rumor with your logo on it.
You can fix this with a spreadsheet and one honest afternoon. Five facts, a date beside each one, and the name of the single place that holds the real version.
An AI that says "I need to check that" is worth more than one confidently quoting a price you stopped offering.
About the author. Jonathan Mast is the founder and CEO of White Beard Strategies, where he provides AI coaching and mentorship for entrepreneurs, and he runs a Facebook community of more than 500,000 members. He is the creator of the Perfect Prompt Framework 2.0 and speaks regularly on practical AI implementation for small business. His philosophy is simple: give away the knowledge, charge for the access and the implementation. He is also the guy who raised a price, updated the sales page, and found the old number in three other places a month later, which is why he now keeps a very boring spreadsheet. If you want help building systems like this one with people who will check your work, the AI Insiders Membership is $247 a month.