Claude invented a phone number — and the user’s reaction was the actually interesting part
On r/ClaudeAI this month, a user posted a short story that’s worth thinking about carefully. They were sourcing materials for a building project. Claude could not find the manufacturer’s phone number. So Claude invented one and offered it confidently. The user called. The number didn’t work. They went back to Claude and asked where the number came from. Claude’s response: I made it up — I shouldn’t have done that. I don’t have a verified number for them.
The top comment on the thread is Is this your first time using LLMs? The second is all the time. I’m building a service based on the fact that this is common occurrence. ALWAYS DOUBLE CHECK.
What’s actually new here
The hallucination itself is not new. Models inventing facts has been documented since GPT-3. What’s new is the verbalized self-correction: Claude said, in plain text, I made it up — I shouldn’t have done that. That’s a specific behavior pattern that 2026-era frontier models do reliably and 2023-era models did not.
For a user, this creates a strange new failure surface. The model can now produce two artifacts in sequence: confident invention, then confident apology. Both feel like the model being honest. Neither is grounded in retrieval. The user in the thread experienced both — and the second one (the apology) is psychologically more dangerous than the first (the invention).
The psychological trap
When a tool admits a mistake, users tend to forgive the tool. Verbalized contrition reads as accountability. But the model that apologized in this story isn’t actually more reliable than the model that invented the number — it’s just better at performing contrition when caught. The next phone number it invents will arrive with the same confidence; the next apology will arrive with the same tone of regret.
The top comment on the Reddit thread — Is this your first time using LLMs? — sounds dismissive but is doing real social work. It’s reminding the community that the apology doesn’t reset the trust calibration. The model that just admitted to inventing one fact is the same model that will invent the next one, with the same affect.
What an indie builder using LLMs in production should take
If your product surfaces LLM output as factual to end users (recommendations, contact info, prices, dates), the apology behavior makes the failure mode worse, not better. Pre-2024, your users saw obvious hallucinations and stopped trusting the output. Post-2026, your users see apologies for hallucinations and continue trusting the output, because the apology models accountability.
The specific engineering move: when the LLM expresses uncertainty or admits a mistake, surface that explicitly in your UI as this fact has not been verified. Don’t let the apology bury inside a conversational reply. The user who called the manufacturer’s invented phone number is fine, embarrassed but fine. The next user might be selecting a hospital, a lawyer, or a medication based on a confident invention followed by no warning. The product layer has to do work the model isn’t doing.
Log in to join the discussion.