A customer knowledge base can live in three places: inside your WordPress site (Heroic KB), as part of a help desk platform (Help Scout Docs), or in a general-purpose tool (Notion). Each has genuine advantages and genuine limitations. The right choice depends on where your support workflow already lives and how tightly the KB needs to integrate with ticket handling.
Heroic KB: Self-Hosted, WordPress-Native
Heroic KB lives inside your WordPress installation. Articles use the WordPress block editor. The KB appears on your domain. Customer searches happen on your site. Analytics stay in your database. This self-hosted model has three practical advantages: no additional monthly SaaS fee, complete design control to match your brand, and direct integration with Fluent Support and other WordPress-based support tools.
Heroic KB Pro costs $149/year. The annual cost covers unlimited articles, unlimited users, and all features. For businesses already paying for WordPress hosting, adding a KB within the existing infrastructure costs significantly less than adding another SaaS subscription.
Help Scout Docs: Integrated With Support Inbox
Help Scout Docs is the knowledge base feature built into Help Scout’s help desk platform. Agents can insert KB article links while responding to tickets directly from the ticket interface. Help Scout’s Beacon widget shows relevant KB articles before the customer submits a ticket, reducing ticket volume by surfacing answers proactively. If you use Help Scout as your support platform, Docs is the natural KB solution because of how tightly it integrates with the ticket workflow.
Help Scout’s base plan ($50/month for a small team) includes Docs. There is no separate KB-only plan – you get Docs as part of Help Scout. For businesses already paying for Help Scout, using Docs costs nothing additional. For businesses evaluating both a help desk and a KB, the combined platform simplifies the stack.
Notion: Flexible but Not Purpose-Built
Notion can function as a knowledge base – it has good search, linking between pages, and a clean reading experience. Many teams use it for internal documentation that gets shared with customers via public page links. The limitation is that Notion is not purpose-built for customer knowledge bases: no ticket integration, no helpfulness voting, no search analytics showing what customers cannot find, and the Notion URL structure (notion.site/your-page-id) is less professional than yourdomain.com/help.
Notion works as a low-cost starter knowledge base and for internal team documentation. As the support function grows and you need deflection analytics, ticket integration, and branded customer experience, Notion’s limitations become constraining.
| Factor | Heroic KB | Help Scout Docs | Notion |
|---|---|---|---|
| Setup complexity | Low (WordPress) | Low (part of HS) | Very low |
| Ticket integration | Fluent Support, etc. | Help Scout native | No |
| Search analytics | Yes | Yes | No |
| Custom domain/brand | Yes (your domain) | Custom domain | notion.site only |
| Annual cost | $149 | Part of Help Scout plan | Free-$96/user |
Not sure which fits your workflow? Describe your needs and get a free recommendation.
Measuring Knowledge Base Effectiveness
A knowledge base that nobody finds is no better than not having one. Track three metrics from day one. First: organic search traffic to KB articles – if customers search Google for answers and find your articles, ticket volume should decrease. Second: direct KB usage rate – how many site visitors land on the KB compared to your contact or support pages. Third: ticket deflection rate – compare tickets per customer per month before and after KB launch.
Heroic KB’s analytics track helpfulness votes and failed searches (what customers searched for but did not find). Help Scout Docs tracks article views and the rate at which the Beacon widget shows articles before tickets are submitted. Notion has no analytics. For evidence-based KB management, either Heroic KB or Help Scout Docs provides the data to improve the knowledge base; Notion requires adding external analytics separately.
Content Strategy for a Customer Knowledge Base
A knowledge base fails when articles answer questions nobody is asking or when the answers are too generic to be useful. The starting point that consistently produces results: pull three months of support ticket data and identify the 20 questions that appear most frequently. Write one article per question. Each article title should match the exact phrasing customers use when they ask the question or search for it – not the internal jargon your team uses.
For format: procedural questions (how do I do X) get numbered steps with one step per action. Conceptual questions (what is X, why does Y happen) get short explanatory paragraphs. Error messages get an article per error code with the exact error message text in the title so customers who copy-paste the error into Google find your article. This format discipline makes articles scannable and findable.