Set the Tone: Your Docs, Your Voice
SupportPages now supports writing style guides: define your tone once and every AI-generated help article matches your company's voice.
There's a tell that gives away AI-generated documentation instantly: it all sounds the same. Polite, slightly formal, faintly American, allergic to contractions. Whatever your product's personality is, the default AI voice sands it off.
That's a real problem, because your help centre is one of the highest-traffic surfaces you own. People land there mid-task, often mildly annoyed. If your product is playful and your docs read like a tax form, the seams show.
So SupportPages now has writing style controls.
How it works
You describe how your company writes - once. Formal or conversational. Terse or thorough. British or American spelling. Whether you say "click" or "select", "users" or "customers", whether you're the kind of company that uses exclamation marks (no judgement).
From then on, every article SupportPages drafts follows that guide. New articles, updated articles, all of them. Change the style guide and future generations pick up the new voice.
It's the difference between hiring a technical writer and hiring a technical writer who's read your brand guidelines.
Why I built this now
Early feedback from design partners was consistent. The articles were accurate - they're generated from the code, so they'd better be - but a few teams said some version of the same thing: "It doesn't sound like us."
They were right, and it matters more than it seems. Documentation you didn't write should still feel like documentation you would have written. Otherwise, every article needs a manual editing pass to fix the voice, and we're back to docs being a chore - which is exactly the thing SupportPages exists to kill.
Accuracy comes from your codebase. Voice should come from you too.
The review step still matters
Style controls don't remove the human from the loop. Every article still lands in your inbox as a draft, and nothing publishes without your approval. The style guide just means that when a draft arrives, it reads like a colleague wrote it rather than a well-meaning stranger.
Less editing per article. Same control.
We're pre-launch and looking for more design partners - especially teams with a strong voice who'd enjoy stress-testing this. Take a look at supportpages.io and get in touch.
About the Author
Simon Moxon has been building SaaS companies since 2009. He's scaled teams to 20+ people, hit £2m ARR, and learned most of the lessons the hard way. Now he's building SupportPages.io - help docs that write themselves when you ship code. He writes about what's changed in SaaS and what hasn't.