Heroic KB turns WordPress into a searchable knowledge base for customer self-service. Instead of answering the same support questions repeatedly, a well-organised knowledge base lets customers find answers independently at any hour. Heroic KB handles the structure (categories, articles, table of contents), the discovery (instant AJAX search as you type), and the analytics (which articles are helpful and which need improvement). It integrates with support plugins including Fluent Support so agents can link relevant KB articles while responding to tickets.
The Business Case for a Knowledge Base
The ROI of a knowledge base is straightforward: every support ticket that a customer answers themselves from the KB is a ticket your team does not handle. If your support team spends 30 minutes per ticket and your KB deflects 20 tickets per week, that is 10 hours of support time recovered weekly. The initial investment in writing KB articles pays back quickly, and unlike support agents, articles are available 24/7 without overtime.
Heroic KB data shows which articles are searched for but not found (gaps in your knowledge base) and which articles receive low helpfulness ratings (articles that exist but do not answer the question adequately). This data makes the knowledge base improvable over time rather than a static document dump.
Step 1: Create Article Categories
Go to Heroic KB -> Categories -> Add New. Structure your categories to reflect how customers think about their problems, not how your product is organised internally. A support team thinks in terms of “product areas”; customers think in terms of “what am I trying to do.” Categories like “Getting Started”, “Billing and Payments”, “Troubleshooting”, and “Integrations” match customer mental models better than “Backend Configuration”, “Payment Module”, “Error Handling”.
Limit to 5-8 top-level categories. A knowledge base with 20 categories is harder to navigate than one with 6 well-chosen categories. Subcategories can provide additional structure within each main category.
Need help setting this up? Describe your project and get a free estimate.
Step 2: Write Your First Articles
Go to Heroic KB -> Articles -> Add New. Articles use the WordPress block editor. Start with the 10 most common support questions your team receives – these are guaranteed to deflect real tickets from day one. For each article:
- Title: use the exact question customers ask (“How do I reset my password?”, not “Password Reset Process”)
- Content: answer the specific question with numbered steps where relevant, screenshots for visual clarity
- Related articles: link to 2-3 articles that customers asking this question might also need
- Category: assign to the relevant category so it appears in the right section
Step 3: Configure Instant Search
Heroic KB’s instant search shows results as visitors type, without submitting a search form. Go to Heroic KB -> Settings -> Search. Configure: minimum characters before results appear (2-3 is standard), number of results to show in the instant dropdown, and whether to search in article titles only or titles and content. Title-only search is faster and usually sufficient; content search catches articles where the question is in the body but not the title.
Step 4: Analytics and Content Improvement
Go to Heroic KB -> Analytics. Three data points drive knowledge base improvement. Search terms with no results show what customers are searching for but cannot find – these become your next articles to write. Low helpfulness vote articles (visitors voting the article unhelpful) need revision. High search volume but low article view rate indicates the article title does not match what customers search for – rename it to match the actual search query.
Integration With Support Ticketing
Heroic KB integrates with several help desk plugins. When an agent is responding to a ticket, they can search the knowledge base and insert a link to the relevant article in their response. This dual-use pattern – self-service for customers who find the KB themselves, agent-assisted for customers who contact support directly – maximises the value of every article written.