Every question your support team answers twice is a help article that does not exist yet. Writing documentation is slow, though, and it usually loses to the next urgent ticket. The Article Generator - Documentation tool writes a detailed first draft from a topic and a set of instructions.
You enter the topic, such as how to export invoices, and the instructions, such as the audience, the steps in your product, the format and anything to avoid. The tool writes a documentation article following those instructions. Your team then checks every step against the real product and publishes it in your help center.
It is part of the Customer service family. Turn recurring ticket replies into articles, and use the FAQ Generator for short question-and-answer pages.
What you get
- A detailed documentation article on the topic you give
- Structure and format that follow your instructions, such as numbered steps or sections
- Plain language suited to the audience you describe
- The article in the language you choose, so one set of instructions can serve several help centers
What you fill in
- Topic required
-
What the article explains, e.g. How to export invoices to CSV.
- Instructions required
-
Audience, the real steps or facts, format, length and what to avoid.
How to use it, step by step
-
Name the topic as a task
Help articles work best as one task, such as how to reset a password, rather than a broad subject.
-
Write the real steps in the instructions
Menu names, buttons and settings exactly as they appear in your product. The tool cannot see your interface.
-
Set audience and format
Say who reads it and how it should look, for example numbered steps and a troubleshooting section.
-
Generate and test the steps
Follow the article in the product and fix anything that does not match before publishing.
Example, input and output
Input
- Topic
- How to export invoices to CSV
- Instructions
- For non-technical users. Steps: Invoices menu, filter by date, Export, choose CSV. Numbered steps, short troubleshooting section.
Output
You can download your invoices as a CSV file to open them in a spreadsheet.
1. Open the **Invoices** menu.
2. Use the date filter to choose the period you need.
3. Click **Export**.
4. Select **CSV** and confirm.
## Troubleshooting
**The file is empty.** Check that the date filter includes at least one invoice.
Illustrative example written by the editorial team to show the expected format.
Tips for better results
- Paste the exact labels of buttons and menus. Readers follow documentation literally.
- Include the questions customers actually ask in tickets, in their own words, so the article answers them.
- Ask for a short troubleshooting section at the end. It often prevents the next ticket.
Who uses it, and for what
SaaS team building a help center
Draft the first set of how-to articles from the most common tickets.
Support lead reducing repeat questions
Turn a frequent ticket answer into a public article agents can link.
Product manager at release time
Write a draft article for a new feature from the release notes.
Internal operations
Document an internal procedure, such as onboarding a new client, for the team wiki.
Limits and good practice
- The tool cannot see your product. Steps it was not given may be generic or wrong, so test every article.
- It does not publish to your help center or update articles when the product changes.
- Give complete steps the first time, since each rerun is a new generation that uses credits from your plan. See pricing.
Frequently asked questions
What makes a good help center article?
One task per article, a title that matches what users search for, a short intro, numbered steps with the exact labels from the product and a troubleshooting section for common problems. Screenshots help too. The tool drafts the text, and your team adds images and tests the steps.
What should I write in the instructions field?
The audience, the real steps or facts, the format and any rules, for example avoid technical terms or keep it under 400 words. The more precise the instructions, the less editing the draft needs, because the tool follows them closely.
Can it write API or developer documentation?
It can draft explanatory articles for developers if you give it the endpoints, parameters and examples in the instructions. It cannot read your code or API, so every request and response must come from you and be tested. For code itself, see the Developer tools.
How is this different from a blog article?
A documentation article helps someone complete a task in your product, so it is precise, literal and focused on steps. A blog article informs or persuades a wider audience. For blog content, use the SEO Article tool, and keep this tool for help and knowledge base pages.
Can I write internal documentation with it?
Yes. Procedures, onboarding guides and checklists for your team work well, as long as the instructions contain the real steps. Remove confidential data you do not want in the workspace and store the final version wherever your team keeps internal documentation.
Try it in your workspace
Start free, no credit card needed. When you need more, one suite grows with you, from Lite to Agency.
Sign in or create a free account, the tool opens in your workspace.