Build a help centre customers can search

The problem

Every business accumulates a small set of questions that account for most of its support volume. How do I change my booking, what is included, how long does delivery take, what happens if it does not fit. The answers are known, written well at least once, and buried in a sent folder.

Because they are not published anywhere findable, the customer’s only route to them is asking you. That is fine at ten customers and expensive at five hundred, and it is worse than expensive at odd hours, when the answer exists and nobody is there to send it.

The half-solution most businesses reach is an FAQ page written once, never updated, and structured around what the business thinks is confusing rather than what customers actually ask.

What AI can actually do here

Two useful things and one tempting mistake.

The first useful thing is retrieval: an AI agent or search that answers from your published articles rather than making something up. This works well when the article exists and fails visibly when it does not, which is the correct failure mode. It also handles the phrasing problem, where a customer asks about a refund and your article is titled Returns Policy.

The second is drafting. Turning a good email reply you already sent into a clean article takes minutes rather than being a writing project, which matters because the reason help centres do not exist is that nobody has time to write one.

The mistake is expecting the AI to substitute for the content. A support agent with nothing to retrieve from will either say it cannot help, which is the honest outcome, or produce something plausible, which is worse than silence. The work is writing the answers. The tool makes them findable.

The other real gain is knowing what is missing: the searches that return nothing tell you which article to write next, which is a better roadmap than guessing.

How the tools differ

Help Scout is built around a shared inbox with a self-service widget, AI drafts and summaries. There is a free plan, with paid from $25 per user per month billed annually. It suits businesses where support is conversational rather than ticket-driven.

Freshdesk is paid from EUR 17 per agent per month on Growth, billed annually, after a 14-day trial, with ticketing across email, chat and messaging plus Freddy AI agents and copilot. It is the middle option on both price and formality.

Zendesk starts from EUR 19 per agent per month on Support Team, with Suite plans from EUR 55 per agent per month billed annually. It is the most complete and the most structured, which is worth it when support is a department and heavy when it is one person.

Notion is the alternative worth naming honestly: if your help content is mostly internal or you have very few public articles, a shared workspace page is free for individuals and EUR 9.50 per seat on Plus, and it is where your other documentation probably already lives.

Zendesk vs Freshdesk compares the two ticketing options directly.

When you don't need a tool

If you get five support messages a week, publish a page on your existing website. A help centre platform for five questions is overhead.

If your questions are all different, a knowledge base will not deflect anything. Check your last fifty conversations: if there is no repetition, this is the wrong fix.

And if the volume is real but the channel is chat, start at answer repeat customer questions or run a support inbox without paying per agent.