Help center

A help center is a public, searchable set of articles answering the questions you get asked repeatedly. It is the only part of your support operation that works while you are asleep, and it does three jobs at once: it deflects conversations, it makes your agents faster, and it is what your AI assistant learns from.

Why bother

Three returns, and they compound.

Deflection. A well-written article about your refund policy stops that conversation happening. Not for everyone — but for the substantial fraction of people who would rather find an answer than ask for one.

Speed. Your agents stop writing the same explanation from memory. They link to it, and the customer gets a better, more complete answer than anyone types at pace.

Search. Help center articles are indexed. "How do I cancel a your product subscription" is searched by people who are already your customers — and by people evaluating you, who read your documentation to judge whether the product is serious.

Portals, categories and articles

Portals can be hosted on your own domain, so the help center reads as part of your website rather than as something bolted on.

Multiple languages

A portal can carry the same articles in several languages, with one set as default. Visitors get the language that matches them, falling back to the default when a translation does not exist.

Translate the ten articles that get the most traffic rather than all of them. A partial help center in someone's own language is far more use than a complete one they cannot read, and the traffic distribution is always steeper than people expect.

Deciding what to write

Do not brainstorm this. The answer is in your inbox already.

1. Open reports and look at your most-used labels. Those are your topics.
2. Look at your most-used canned responses. Each one is an article you have already written, just in a worse format.
3. Ask your agents what they are tired of typing. They will tell you immediately and accurately.
4. If Tola AI is on, look at its FAQ suggestions — it identifies the same question being answered repeatedly, from real conversations.

Write the top ten. Publish them. Then write the next ten. A help center of twenty good articles beats one of two hundred where half are stale.

Writing an article people finish

The failure mode of help articles is that they are complete and unreadable.

• Title it as the question the customer would ask. "How do I change my billing address?" not "Billing address management". People search in questions.
• Answer in the first sentence. Then explain. Anyone who needed only the answer has left, satisfied.
• Number the steps. If there are steps, there is a numbered list. No exceptions.
• One article, one question. A page covering five related things ranks for none of them and answers none of them well.
• Show what they will see. A screenshot removes more confusion than a paragraph.
• Say what to do if it does not work. Every article should end with a way out — the next thing to try, or how to reach a human.
• Write in the words customers use, not your internal names for things. If your customers say "account", do not title the article "tenant".

Using it inside conversations

Agents can search the help center from the conversation and drop a link into their reply. This is worth building as a habit: answer the question directly, then link the article for the full version.

That combination is better than either alone. The customer gets their answer immediately, and they learn the help center exists — so next time they may not need to ask.

Feeding your AI assistant

Everything you publish becomes knowledge Tola AI can answer from. Point an assistant at your help center and it will use the articles, keeping itself in sync as you edit them.

This changes the economics of writing articles considerably. Each one now answers customers who search, customers who ask an agent, and customers who ask the assistant — from a single piece of work.

It also raises the stakes on accuracy. A wrong article was previously read by a few people; now it is the basis of an answer given to everyone who asks. Fix errors quickly.

Keeping it alive

Help centers rot, and a stale help center is worse than none because customers act on it.

Review quarterly. Anything describing a screen that has changed is actively harmful.

Watch what gets no traffic. An article nobody reads is either answering a question nobody has, or unfindable. Both are worth fixing or deleting.

Watch what gets traffic and still generates conversations. That article is not answering the question it appears to answer — the most valuable signal the help center produces.

Assign ownership. Give someone the knowledge base permission and make it part of their job. See agents, teams and roles. A help center nobody owns is one that was written once.