How to build a help center that actually deflects tickets

A help center is supposed to answer questions before they become conversations. Many never do, because they are written from the product's point of view (a tour of every settings screen) rather than the customer's (I'm trying to do this, and it isn't working). The fix is not more articles. It is the right articles, written the way customers search, placed where customers already ask.

What deflection really means

"Deflection" sounds like keeping customers away. It should mean the opposite: the customer gets a complete answer immediately, at any hour, without waiting for a reply, and your team gains time for the conversations that need a person. If an article leaves people more confused, it has not deflected anything. It has delayed a conversation and made it harder.

So the goal is not fewer chats at any cost. It is fewer repeat questions, and better conversations about everything else.

Choose your first 20 articles from real conversations

Do not start from a blank outline. Start from what people already ask.

1. Tag a few weeks of conversations by topic. Keep tags broad, such as billing, setup, shipping and account access, so the counts mean something. If you already tag, start from the tags report.
2. Look at your saved replies. Every saved reply is an answer you have written more than once. Most of them should become articles.
3. Search the inbox for phrases like "how do I", "where is" and "can I" to find questions that slipped past your tags.
4. Rank by frequency and effort. A question that comes up daily and takes five minutes to answer is worth more than a rare one.
5. Write the top 20. In most businesses a fairly small set of questions makes up much of the chat volume, so twenty well-chosen articles go a long way.

Structure collections around tasks

Collections are the top-level groups in your help center. Organise them by what customers are trying to do, not by how your product's menus are laid out. Four to eight collections is plenty to start with, for example:

• Getting started
• Account and billing
• Orders, shipping and returns (or "Using the product" for software)
• Integrations
• Troubleshooting

Put each article in the collection a customer would check first, and link related articles to each other so a reader who lands in the wrong place can still find the right one.

Write for search

Most help-center readers arrive from a search box, either yours or a search engine's. Write for that.

• Use the customer's words in the title. If customers say "cancel my subscription", do not call the article "Managing your plan lifecycle". Task titles ("How to cancel your subscription") and question titles ("Why was I charged twice?") both work.
• Answer in the first two sentences. Put the short answer first and the detail after it. Many readers stop as soon as they have what they need.
• One task per article. Long articles covering five tasks are hard to find and hard to keep current.
• Number the steps and name buttons and menus exactly as they appear on screen.
• Use the different words people use for the same thing. If some customers say "invoice" and others say "receipt", mention both.
• End with a next step: a related article, or a way to contact you if the article did not solve the problem.

Put articles where people ask

A help center only deflects questions if people find it. The best place to surface it is the chat window, at the moment someone is about to ask.

• Search in the messenger. TalkingDot's messenger home screen includes help search, so visitors can look for an answer before starting a conversation.
• The answer bot. When a visitor asks a question, TalkingDot's answer bot suggests relevant articles. If one solves it, nobody needed to step in; if not, your team picks up the conversation as usual.
• Saved replies that link to articles. When a teammate answers a common question, including the article link shows the customer where to look next time.
• Links from your site and product. Put a link to the relevant article next to the pages and settings where people get stuck.

Use votes and view counts

TalkingDot records view counts and "Was this helpful?" votes for every article. Read them together:

Also watch your conversation tags after publishing. If a topic's share of conversations drops after you publish or rewrite its article, that is your best evidence the article is working.

Keep articles fresh

An out-of-date article is worse than none, because it gives a confident wrong answer. A few habits keep a help center accurate:

• Give every collection an owner who reviews it on a regular schedule; quarterly suits most teams.
• Add "update the help center" to your release checklist, so product changes and article changes ship together.
• Treat corrections as bugs. If a teammate has to correct an article in chat, fix the article the same day.
• Retire articles about features that no longer exist, rather than leaving them to confuse search.

The SEO benefit of a public help site

Every TalkingDot workspace gets a public, search-engine-friendly help site. That matters beyond support. People search for things like "how to connect X to Y" or "why does Z happen" long before they contact you, and a clear article can be the first time they meet your business. Help articles answer the specific, long-tail questions that marketing pages never cover.

To get the most from it, keep titles in plain customer language, link to the help center from your site's navigation and footer, and link related articles to each other. Keep anything private, such as internal procedures or customer details, out of public articles.

The help center guide shows how to set up collections and publish your first article in TalkingDot. If you do not have a workspace yet, create one free and start with the five questions you answered most often this week.