An AI user manual generator for software and SaaS help centres
People open a help centre with a task in mind and a screen in front of them. If the article calls a button by a different name, or promises a feature their plan does not include, they give up and raise a ticket. INKFLOW drafts software user guides and help centre articles around the tasks your users actually try to do.
Name it a software user guide or help centre in your brief and the writer works from guidance for SaaS documentation. It asks for the product and version, your user roles, which features each tier includes, a permissions matrix, the top tasks from your support tickets, error messages word for word and your style guide.
Interface labels, limits and quotas come only from what you send; where a file size or retention period is missing, the article shows a marked placeholder. INKFLOW writes text and does not capture screenshots, so images are yours to add. Read every article against the live product before you publish it.
Product name, edition and current version, so each article records what it was written against and can be rechecked when the next release lands.
2
Rank the tasks
The jobs users most often need help with, taken from tickets or analytics. These become the how-to articles, in that order.
3
Send the screens as they are
Current screenshots or an exact list of labels and navigation paths, plus each error message verbatim with its real cause and fix.
4
Check and publish yourself
The order page quotes before you pay. Your product or support team then tests each article against the product and publishes it in your own help centre tool.
Help centre articles the user guide includes
Task articles
One goal per article, with prerequisites, numbered steps and the result the user should see, in one consistent template.
Tier and role gating up front
If a feature needs a certain tier or permission, the article says so in its opening lines, before anyone hunts for a button they cannot see.
Admin guides
Roles, permissions, integrations and settings for the people who set the product up, kept apart from end-user articles.
Troubleshooting from real errors
Each error message as it appears, what causes it and the fix, from the list you provide.
Warnings before irreversible actions
Deletion, export and recovery behaviour stated plainly wherever a user could lose data.
Reference and changelog
Supported browsers and platforms, limits, and a release history built from your release notes.
Where a software user guide still needs your team
INKFLOW does not record screens or publish to your help centre platform. It cannot tell when the interface has changed, so articles go stale unless someone owns them after each release.
Standards such as ISO/IEC/IEEE 26514 describe good practice for user documentation, and the draft follows the same task-first thinking without claiming conformity. For developer-facing reference material, the API documentation page is the better fit.
Questions
Can it write release notes as well?
It builds the changelog section from release notes you supply. Articles about a new release are drafted from what you say changed, not inferred.
Can it match our existing help centre style?
Send your style guide and terminology list. Product terms are used exactly as you define them, and the tone follows your brand voice.
Can it rewrite articles we already have?
Yes. Upload them to have them revised, and ask for a plain English version if your readers are not technical.
Can it write onboarding guides for new customers?
Yes, as a getting-started path made of task articles in the order a new account needs them. Tell the writer what a customer must set up before the product is useful, and which steps an admin rather than an end user completes.
Does it work for desktop and mobile apps, not only web?
Yes. List the supported platforms and app versions; where steps differ between them, give the difference and each is written separately.
Do prices include VAT?
Prices include any VAT; nothing is added at checkout.
We are an organisation. How can we pay?
Single orders are paid by card at checkout. For subscriptions and repeat orders, care homes, councils and businesses can ask about paying by Direct Debit or standing order at app.inkflowstudio.org/organisations.
Write help for the task, not for the feature list.
Tell us what it is for, and it is written to the standard. In the free sample, any figure that must come from your own material is left as a marked placeholder.