Knowledge Base Article Generator
Turn a question and a list of facts into a help article with an intro, steps and notes, for customers or your internal team. A model drafts it in your tone; you check the facts.
The help center has an article for every question that was common two years ago and none for the three that fill the queue today. Agents know the answer; it is in a macro, a Slack thread, and the head of one person who wrote the feature. Getting it into an article means someone writing prose on a Friday afternoon, so the queue keeps answering it one ticket at a time.
This tool drafts the article from the facts. Give it the title or the question, then the steps, limits and policies the article should contain — the click path, who can do it, what expires — and pick the audience and tone. A model turns the notes into a short article with an intro, numbered steps and the caveats, using only what you gave it. It is a draft: check each fact against the product before publishing. The model reads your notes once; nothing is stored beyond a short cache of the result.
This ran once, on one input. The product runs on your whole site, every conversation.
Write the article, then let an agent answer from it — start freeExample: help article on adding a teammate
How do I add a teammate to my workspace? Workspace admins can invite as many teammates as they need. Seats are free, so adding someone doesn't change your bill. Before you start You need the Admin role. If you don't see Team under Settings, ask an existing admin to invite the person or to make you an admin. Steps 1. Open Settings from the menu in the top right. 2. Choose Team. 3. Select Invite and enter the teammate's work email address. 4. Pick a role: Admin or Member. Members can do everything except manage billing and the team. 5. Select Send invite. What happens next Your teammate gets an email with a link to join. The link is valid for 7 days; after that, you can resend it from the Team page. Once they've joined, they appear in the Team list and you can change their role at any time. Good to know Invites are tied to the email address, so if the teammate signs up with a different one they won't be added to your workspace.
What each input means
- 01
Article title or question
The question in the customer's words — "How do I add a teammate?" — which becomes the title, or the title itself. One question per article. If the answer differs by plan or role, say which in the notes, or write two articles.
- 02
The facts, steps and policies it should contain
Everything the article must say, in any order, as notes: the click path with the menu names exactly as they appear, who has permission, limits, costs, what expires. The model writes from these and nothing else, so if a step is missing here it is missing in the article.
- 03
Audience
Customers gets an article for the help center: no jargon, no internal system names, a friendly intro. Internal support team gets one for your own wiki: terse, includes the edge cases and the escalation path, assumes the reader knows the product.
- 04
Tone
Warm, Professional or Brief. Professional is the usual choice for a help center; it reads as documentation. Brief produces steps with almost no prose, which suits internal articles and anything an agent will paste into a reply.
Questions about this tool
As long as the task and no longer. A how-to is usually 150 to 300 words: one sentence on what it does and who can do it, numbered steps with one action each, and a note on what to expect after. Articles over 600 words are usually two articles. If the steps run past eight, split the task.