“We need AI in our docs” means three different things to three people in the room: autocomplete, a chatbot, or an agent that publishes on its own.
We mapped it into 5 levels of autonomy, from editor to autopilot. Almost no one is at L4 yet.
👉 tinyurl.com/54cf7ebu
#AIdocs
Choosing a help authoring tool? Watch ClickHelp live: import from Word, snippets, conditional content, publishing, AI.
30 min, Thu Oct 29, 17:00 CET / 12 PM EDT.
No account needed, ask anything in the chat.
Join: tinyurl.com/3f6c35xn
#TechnicalWriting #Documentation
Your docs chatbot gives wrong answers? A bigger model won’t fix it.
We tested 14 setups on 50 real support questions. Often the model never got the article with the answer, and no model can answer from an article it never saw.
What we found→ tinyurl.com/5yrvpp7j
#AIdocs
Your AI support bot has a 78% deflection rate. Great.
But how many problems did it actually solve?
A conversation ending ≠ a problem solved.
Here’s how to measure what really matters → tinyurl.com/5n6w8mjk
#TechnicalWriting #AI #TechComm #AIdocs #documentationsystem
Thanks to everyone who joined Single-Sourcing with AI! Best moment: we renamed the product once, and every topic using the variable updated.
Next: a 30-min ClickHelp live web, Wed Oct 21, 16:00 CEST / 10:00 AM EDT.
Register: tinyurl.com/2smvfzy6
🤖 Made with AI
A Standard-plan user asks your AI assistant about SSO. It answers from the Enterprise docs. The text matched, the plan didn’t.
Embeddings capture what the text means, not who it’s for.
Metadata fills that gap → tinyurl.com/5hdtxaed
#TechnicalWriting #RAG #TechComm #AIdocs
AI writes the same instruction a little differently every time. Snippets make sure it’s written once.
On Oct 15, we’ll use an AI assistant + MCP to turn repeated text in a ClickHelp project into reusable snippets.
18:00 CEST / 12:00 PM EDT
Register: tinyurl.com/3zzu5e8p
Your support address changes. It lives in 4 manuals and 2 languages. One copy gets missed, and a user calls the wrong number.
How to publish several manuals from one source→ tinyurl.com/drxsdjj2
#TechnicalWriting #SingleSourcing #TechComm #Documentation
Second product, same argument: one docs site or separate ones? Both setups fail the same way. The real question is what must stay separate for readers and what must stay shared for the team.
Read the article → tinyurl.com/4dp4ss36
#TechComm #Documentation
Your docs say "SSO configuration." Your reader types "can't log in with my work account."
Same problem, no shared keywords. AnswerGenius now searches by meaning, so it still finds the right topic.
More features in our September release → tinyurl.com/mtrkmnzt
#Techcomm #AI










