What is Knowledge Base?

Converge Converge Team

A self-service library of information about products, services, and common issues

What is Knowledge Base?

A knowledge base is a structured collection of articles, guides, and tutorials that customers can browse to find answers without contacting your support team. Unlike a simple FAQ page, a knowledge base is organized into categories, includes a search function, and contains detailed articles with screenshots, videos, and step-by-step instructions.

Knowledge bases serve two audiences: customers looking for self-service answers, and support agents who need quick access to product information while handling conversations. The best knowledge bases are written in plain language, cover both common and edge-case scenarios, and are continuously updated based on actual support tickets.

Why Knowledge Base Matters

A well-maintained knowledge base can deflect 20-40% of incoming support tickets. Each self-service resolution costs roughly $0.10 compared to $6-12 for an agent-handled interaction. For a team receiving 100 tickets per day, deflecting even 25% saves your team 25 conversations daily and thousands of dollars monthly.

Knowledge bases also improve agent efficiency. Instead of typing detailed explanations from scratch, agents can link customers to relevant articles. This reduces handle time and ensures every customer gets accurate, consistent information regardless of which agent they speak with.

Knowledge Base in Practice

A B2B software company analyzed their top 20 support topics and found that 15 of them could be answered with documentation. They created detailed knowledge base articles for each topic, embedded them in their chat widget as suggested articles, and saw their monthly ticket volume drop from 1,200 to 740—a 38% reduction. The articles also improved onboarding, as new customers found setup guides without needing to contact support.

Related Terms

Related Reading

Frequently Asked Questions

Start with articles covering your 10-15 most common support questions. This alone can deflect 20-30% of tickets. Add articles based on recurring questions from your support queue. Quality matters more than quantity—10 thorough articles outperform 50 superficial ones.
Both, but in separate sections. Customer-facing articles should use simple language and step-by-step instructions. Internal articles for agents can include technical details, troubleshooting trees, and escalation criteria that customers don't need to see.
Review articles whenever your product changes (new features, UI updates, pricing changes). Also review your top 10 articles quarterly to ensure they're still accurate. Articles that generate follow-up support tickets are candidates for rewriting.