Knowledge Base

Definition

A knowledge base (KB) is a structured, searchable repository of information — articles, guides, procedures, FAQs — that enables users (customers, employees, or both) to find answers without contacting a human. It is the primary vehicle for support ticket deflection and the foundational layer of any self-service strategy.

The term is often used interchangeably with help center (customer-facing) and internal wiki (employee-facing), though each has distinct structural requirements.

Types of knowledge bases

External help center: Publicly accessible, customer-facing, often SEO-optimised. Goal: reduce inbound support contacts by letting customers self-serve. Examples: Document360, Zendesk Guide, Help Scout Docs.

Internal wiki: Employee-facing, access-controlled, policy-and-process focused. Goal: reduce “Slack-as-KB” anti-patterns, enable compliance documentation, accelerate onboarding. Examples: Notion, Confluence, Slab, Guru.

Dual-purpose KB: Separate workspaces for internal and external content under one admin. Rare in the SMB space; Document360 Business ships this via multi-workspace.

What makes a knowledge base actually work

Most KBs fail not because of bad tooling, but because of bad content strategy. The three drivers of KB effectiveness:

1. Article coverage: Does the KB cover the 30 most common questions? In most B2B SaaS products, 30-50 well-written articles cover 60-70% of ticket volume. Starting with coverage is more important than perfect search.

2. Search quality: Can users find articles when they don’t know the exact title? Synonym matching, intent understanding, and contextual surfacing (in-product Beacon) all matter. Most free-tier KBs fail here.

3. Content freshness: Are articles kept current? Stale articles are worse than no articles — they undermine trust. Tools with verification workflows (Guru, Document360) outperform tools without (Notion, basic Confluence) on long-term quality maintenance.

The buyer’s question nobody asks

Most buyers evaluate KBs on feature checklists: “Does it have analytics? Does it support multilingual? Does it integrate with Zendesk?” Those are all valid questions. The question that almost nobody asks upfront is: “What deflection rate can I realistically expect in 6 months?”

The industry-honest answer: 15-30% for a B2B SaaS team with a dedicated content owner and serious article investment. Not 70%. Not 50%. 15-30% is the number that actually unlocks the ROI conversation.

Related terms

• Help center — the customer-facing form of a KB
• Internal wiki — the employee-facing form
• Ticket deflection — the primary ROI metric
• Knowledge management — the broader discipline; KB is one artefact within it
• Deflection rate — the % of contacts resolved by self-service