"Always write high-quality content" is useless advice — what does that even mean when the reader is an AI agent? | Community
Skip to main content
Submitted

"Always write high-quality content" is useless advice — what does that even mean when the reader is an AI agent?

Related products:Knowledge & Help CenterFin & AI
  • Jul 27, 2026 1:42 PM UTC
  • 2 replies
  • 55 views

Conor
Super User ✨
Forum|alt.badge.img+6

New Support Stack episode with ​@Dawn, AI Knowledge Manager at Fin. She's turned that vague instruction into a concrete 14-factor checklist you can run against any help article — the things that break AI retrieval and human comprehension at the same time (ambiguous references, missing alt text, steps buried in prose, headings that don't match how customers actually ask). Then she runs the whole check live as a single Operator prompt: what passes, what fails, and exactly what to rewrite.

Watch Dawn’s second episode on Support Stack here!

2 replies

  • New Participant
  • Oct 9, 2026 4:25 PM UTC

"Most transfers arrive within minutes" is true, but the agent will repeat it to someone whose transfer is stuck in pending. I ran a test on a demo transfer company, and the agent told a customer with a pending transfer it was "on its way" 3 times out of 3.

Usually, the fix is just putting the condition in the same sentence, like "once it shows Completed, it usually arrives within minutes." Also worth checking whether two articles describe the same policy differently, since the agent will quote whichever one it pulls.

@Dawn curious if one of the 14 already covers this?


Dawn
Employee
Forum|alt.badge.img
  • Employee
  • Oct 12, 2026 1:09 PM UTC

👋  Great test, thanks for running it! To your question: partly. Self-contained sections (#3) catches it if the condition sits in a different sentence from the claim. Limitations and workarounds (#11) catches it if the pending case isn’t documented at all. But none of the 14 says outright “keep the condition in the same sentence,” and it probably should.

Your fix is the right first step. I’d also give the pending case its own FAQ, something like “Why is my transfer still pending?” State exactly when to worry (“If your transfer has been pending for more than X hours”) and what to do next (contact support, check a status page, whatever the real process is). That way your AI Agent has a direct answer for the stuck customer, not just a hedged version of the happy-path answer.

Also, on conflicting articles we have functionality built in to catch this in the knowledge base →   Fin Al Agent > Analyze > Recommendations   :)