ClickHelp.com

Quick test for your docs site: run curl on an article URL, or open it with JavaScript turned off. If the article text isn’t there, an AI tool fetching that page may not see it either. More checks like this on Nov 5: clickhelp.com/events/ai-read…

“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

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

Who Are You Actually Writing For? Explaining "what is a subnet" to a CCIE engineer loses them in one line. Skipping VPC basics loses a junior. This article covers how to profile readers you'll never meet. Read → tinyurl.com/mkrumkty #TechnicalWriting #TechComm #Documentation

Documentation generation with AI takes under a minute. Reads perfectly. Also wrong — because the ticket it drew from was outdated before the writer even opened it. Where should tech writers sit in the SDLC? 🧵👇 Read → tinyurl.com/39c2tf87 #TechnicalWriting #AIWriting #SDLC

Your changelog and your release notes should never read the same. One's for developers. One's for users. Most teams write both the same way — which is why nobody reads either. Read more → tinyurl.com/4y8mec2y #TechnicalWriting #ReleaseNotes #DevOps #TechComm #CICD

Two dictionaries picked "slop" as their 2025 word of the year. Documentation has its own version: a portal that doubled in size while support tickets stayed flat. Writing got cheap. Scoping went with it. Read → tinyurl.com/4zmhuf4x #TechnicalWriting #DocumentationStrategy #AI

Ask MT to translate the same term twice, and there's no guarantee it comes back the same way. That's how one feature name ends up with three names across your docs. We asked @alconost what actually fixes it. Read here→ tinyurl.com/yxamm92s #Localization #TechDocs #AI

Short answer: it's not a snapshot — every query hits your live published docs at the moment the reader asks. No caching, no re-indexing lag. Update your topic, republish, and the agent sees the new version on the very next question. Read-only, nothing unpublished.

Docs-as-code brings technical documentation into the same workflow as software development: Git, pull requests, versioning, CI, automated validation, and continuous publishing. In this article: popular docs-as-code tools → tinyurl.com/2uuzse7j #TechnicalWriting #DocsAsCode

Your docs can now plug straight into Claude, Cursor, ChatGPT, or Gemini. The Published Docs MCP Server connects readers' AI agents to your docs — current content only, no guessing. Plus: AI Overview, and other improvements Read → tinyurl.com/ynbbtk7r #clickhelp #update

Same warning copied into 40 topics. Product changes, and now you're hunting down 40 places to fix it. Snippets fix this: write the block once, insert it everywhere, update the source when things change. Read more → tinyurl.com/3ee2a2bj #TechWriting #DocumentationManagement