Self-service: knowledge base & FAQ
The best ticket is the one that never exists
Most requests are repetitive: "how do I reset my password," "what are your delivery times," "how do I cancel." Answering them one by one is a time leak. Self-service lets the customer find the answer alone, 24/7, without contacting you. It's the support investment with the best return: written once, it deflects hundreds of questions.
FAQ, help center, knowledge base
Three levels, from simplest to most complete:
graph LR
A[FAQ on one page] --> B[Structured help center]
B --> C[Searchable knowledge base]
| Level | When | Effort |
|---|---|---|
| Single FAQ | < 15 recurring questions | one page, 1 hr |
| Help center | Product with several topics | categories + articles |
| Knowledge base | High volume, search | dedicated tool + engine |
Start with a FAQ. Only upgrade when it overflows.
The tools
| Tool | Strengths | Indicative price |
|---|---|---|
| Notion (public page) | Free, fast to set up | free |
| Crisp / Tidio Helpdesk | Built into chat, auto suggestions | included in plans |
| Help Scout Docs | Clean, searchable, support-integrated | included / ~$22 |
| Document360 / GitBook | Rich, versioned bases | from ~$20 → $50 |
| Tally / site page | Simple accordion FAQ | free |
For most entrepreneurs, a public Notion page or the Docs built into the helpdesk are plenty.
Writing an article that truly deflects
A good help article isn't a manual: it solves the problem from the customer's point of view. A few rules:
- Title = the customer's real question ("How do I cancel my subscription?"), not an internal term.
- Answer in the first line, details after.
- Numbered steps and screenshots for procedures.
- One article = one problem, short and precise.
- Updated whenever the product changes: a wrong article is worse than none.
Plugging self-service into support
Self-service doesn't replace the human, it precedes them. Show the knowledge base inside the chat widget: before writing, the customer sees suggested articles based on their question. Many leave with their answer. Those who write anyway have already searched — their case truly deserves a human. That's smart deflection: filter the simple, escalate the complex.
Measure what really helps
A knowledge base is steered. Watch which articles get the most views (your real friction points), which still generate tickets despite existing (badly written or hard to find), and which internal searches return no result (articles to create). Self-service is alive: it feeds on the real questions you receive every week.
Psychology: autonomy and fluency
Many customers prefer to find answers themselves rather than ask — out of autonomy, or to avoid "bothering" you. Self-service respects this need for control. And a clear, well-organized help center sends a signal of fluency and seriousness: a brand that anticipates questions seems competent and trustworthy, even before any human contact.
Key takeaways
Self-service is the best-ROI support: written once, it deflects the repetitive continuously. Start with a FAQ (Notion or integrated Docs), grow toward a help center with volume. Write from the customer's point of view, one problem per article, and plug suggestions into the chat to filter before the human. Steer with view counts and zero-result searches. Now let's see how AI extends this self-service by automating replies.