What is a knowledge base?
A knowledge base is a searchable collection of articles, guides, and answers that explains how a product works, so users and support agents can find answers without asking someone. In SaaS it usually means a public help center plus an internal library that support agents and AI assistants draw on.
What a knowledge base contains
How-to articles walk through completing a task. Reference articles explain what a screen, field, or setting means. Troubleshooting articles cover what to do when something does not work. FAQ-style articles answer the short questions that come up repeatedly. A well-organized knowledge base groups these by product area and keeps the how-to articles close to the screens they describe.
Who reads it
Customers arrive from search or from a help link inside the product, usually with one specific question. Support agents use it to answer tickets consistently and to link customers to a fuller explanation. And AI assistants, whether a chatbot in the help center or an assistant inside the product, read it as a source. That last reader is new and changes what a knowledge base needs to be, because an assistant will repeat whatever the articles say, with full confidence, whether or not the article is still true.
Why knowledge bases go out of date
The product changes every week and the articles change when someone remembers to change them. The gap between the two shows up as screenshots of old interfaces, steps that reference renamed buttons, articles for features that were removed, and no article at all for features that shipped last month. Since no alert fires when an article goes wrong, the drift accumulates until a customer or an assistant surfaces it.
The cost is tickets that should have been deflected, customers who tried the article and got stuck, and assistants that give wrong answers. The economics of that are in the freshness tax, and the case for treating the help center as a transitional layer rather than a destination is in the help center was a stopgap.
What a good knowledge base looks like now
It is verified against the live product rather than against the previous version of the article, and reviewed per release rather than per quarter. It is written for two readers at once, a person skimming for one answer and an assistant that will extract the answer and present it in context, which favors short, task-scoped articles with current interface names. Long tutorials with embedded screenshots go stale fastest and are the hardest for an assistant to extract a clean answer from.
How Frigade fits
Frigade approaches the problem from two directions. The assistant learns the product by using it, so its answers do not depend on articles being current. And Frigade Knowledge audits an existing knowledge base against the live product, flags the articles that have drifted, and proposes rewrites the team can approve or auto-publish, so the help center stays accurate for the people and systems that still read it.
Common questions
- What is the difference between a knowledge base and a help center?
- A help center is the public, customer-facing part of a knowledge base. The knowledge base as a whole can also include internal articles for support agents, troubleshooting runbooks, and content that only an AI assistant reads. Many teams use the terms interchangeably.
- What is knowledge base software?
- Software for writing, organizing, and publishing the articles. Zendesk Guide, Intercom Articles, Help Scout Docs, Document360, GitBook, and Notion are common choices for SaaS companies. The software handles hosting, search, and permissions. Keeping the articles accurate as the product changes is a separate job that falls to the team.
- Ticket deflectionTicket deflection is when a customer resolves a question on their own, through self-service help or an automated assistant, instead of opening a support ticket. The deflection rate is the share of would-be tickets resolved this way, and it is the main number used to judge whether self-service is working.
- Contextual helpContextual help is assistance that changes based on where the user is and what they are doing in the product, so the answer matches the screen in front of them. It ranges from a tooltip on a single field to an assistant that knows the user's current page and answers accordingly.
- In-app guidanceIn-app guidance is help delivered inside the product interface, where the user is working, instead of in a separate help center, email, or support ticket. It includes tooltips, walkthroughs, checklists, contextual hints, and in-product assistants that answer questions and complete tasks.
- Customer onboardingCustomer onboarding is the process of taking a new customer from the point of purchase to the point where they are getting the value they bought the product for. In B2B SaaS it covers implementation, account setup, training, and the first weeks of use, and it is judged by time to value and by whether the account is still active at renewal.