A help center that actually reduces support load, in five evenings

Every SaaS eventually gets a help center, and most of them are written in one heroic weekend, linked from the footer, and never touched again. Six months later the screenshots are wrong, the pricing article describes a plan that no longer exists, and support volume is exactly what it was.

The help centers that reduce load share a different origin story. They are built from the inbox, not from the product's feature list, and they are maintained in tiny increments. Here is a five-evening plan that gets you there, using Svellyo's knowledge base and help center, though most of it applies to any tool.

Evening 1: mine the inbox, do not brainstorm

Open your conversations from the last two months. For each one, write down the question in the visitor's words, one line each, in a text file. Do not clean them up. "how do i change my card", "does it work with webflow", "i got charged twice", "where is the api key".

You will end up with fifty to a hundred lines and a lot of duplicates. Group the duplicates. The groups, sorted by size, are your table of contents. The top ten groups usually account for more than half of all conversations. Those ten articles are the whole first release.

If you use Svellyo, the Analytics page has a "Top questions" section that does this clustering for you weekly. Use it as a cross-check, not a replacement for reading the actual messages, because the phrasing matters for the next step.

Evening 2: write the top ten, badly

Write the ten articles in one sitting. Each one has three parts: the question as the title, the answer in the first two sentences, and then whatever detail is needed. Use the visitor's words from Evening 1 in the title. "How do I change my card?" not "Updating payment methods".

Do not add screenshots yet. Do not polish. A correct, plain, two-paragraph answer published tonight beats a beautiful one published never. The editor accepts Markdown on paste, so if you write in a text editor, paste the whole thing in and the headings and code blocks carry over.

Set every article's visibility to Public + AI. From the moment you publish, the AI agent starts using them, which means you get the benefit before anyone has visited the help center at all.

Evening 3: collections, order, and the two hidden articles

Group the ten into three or four collections. "Getting started", "Billing", "Troubleshooting" cover most products. Give each collection a one-line description; it appears on the help center home and in search results.

Order the articles in each collection by how often the question comes up, not alphabetically. The article at the top of "Billing" should be the one you answered most.

Then write two articles that are AI only: one with your exact plan limits and prices as a flat list, and one with the policies you apply but do not advertise, like the refund window you actually honour or the trial extension you give when someone asks nicely. The agent will state these precisely when asked. Your public help center will not show them.

Evening 4: turn on the public site and put it where people look

Under Knowledge base, Help center, enable the site. It lives at help.svellyo.com/your-slug immediately; on Pro and Scale you can add your own domain with a CNAME. Upload a logo, pick your colour, add a footer link back to your site.

Then put the link in four places: your site footer, your app's help menu, the automatic reply email you send when someone writes in, and your widget. The widget already has a "Browse the help center" entry on its home screen once the site is enabled.

The help center includes the chat widget, so a visitor who cannot find an answer can start a conversation from the article they are reading. That conversation arrives in your inbox with the page URL attached, which tells you which article failed.

Evening 5: the weekly ten minutes

The help center is done. Now the part that makes it work.

Every Monday, open two things: the "Unanswered questions" list in Analytics, which shows what the AI could not answer well, and the article ratings, which show where readers clicked "no" on "was this helpful?". Each entry is a small task: write an article, split an article, or fix a sentence. Ten minutes covers it. Over a quarter, this is what moves AI resolution from half of conversations to three quarters.

Also every Monday, glance at any conversation that was handed off with the reason "low confidence". That is the agent telling you exactly which article it wishes it had.

Structuring for two readers

A help center now has two audiences: people scanning, and a retrieval system matching a question to a chunk of text. Happily, what works for one works for the other.

• Short articles with one topic each. A person finds the answer without scrolling; the retriever gets a clean chunk.
• The answer first, context after. A person stops reading when satisfied; the retriever weights the opening.
• Real vocabulary in titles. A person recognises their question; the retriever matches it.
• Headings that are questions or actions. "Why is my export empty?" over "Exports".
• Tables for anything with numbers. They keep their headers as real tables in the editor, which the AI reads correctly.

The thing that works for people and hurts retrieval is the long "complete guide" page that covers everything. Keep those for onboarding, and split the reference material out.

What to leave out

Do not document what nobody asks about. A help center is not a spec. If a feature has never generated a question, it does not need an article yet, and writing one adds noise for both readers.

Do not screenshot every step. Screenshots go stale fastest and add the least. Use them only where the UI is genuinely confusing, and crop tight.

Do not write a "contact us" article. The widget is on every page of the help center already.

Measuring whether it worked

Three numbers, all in Analytics.

Resolved by AI should climb as the knowledge base fills in. Half is typical at the start; three quarters is achievable for a product with clear documentation.

Conversations per week should flatten or fall relative to your traffic, because more people are finding answers before writing.

Top pages where chats start should shift away from your docs and towards pages where a human genuinely is needed, like billing or account settings.

If resolved-by-AI is not moving, the articles are not being retrieved: check the titles. If conversations are not falling, the help center is not being found: check the four links from Evening 4.

The short version

Build it from the inbox, ten articles first, answers in the first two sentences, real vocabulary, a couple of AI-only articles with exact numbers, then ten minutes every Monday driven by the unanswered questions list. Five evenings to start. The weekly ten minutes are the whole secret.