The Short Answer
A knowledge base isn't a content project; it's an operational process. The question determining its survival isn't how many articles were written at launch, but what triggers the creation of new articles and the review of old ones. Without these two mechanisms, any knowledge base degrades into a folder of files nobody ever opens.
The simple test for current status: How many Cases were closed this month with a linked article? Below 30% means the knowledge base isn't integrated into the workflow.
Article Lifecycle
| Stage | Responsible Party | Trigger |
|---|---|---|
| Creation | Agent who resolved the inquiry | Recurring Case without a linked article |
| Approval | Knowledge Editor or Subject Matter Expert | Approval queue with a time target |
| Publication | Editor | Visibility setting: internal or public |
| Review | Defined Owner | Review date or usage data |
| Retirement | Owner | Discontinued product or changed policy |
The stage often skipped is retirement. Old articles aren't harmful as a minority, but once they make up a quarter of the knowledge base, agents stop trusting search results – and that's the point of no return.
The Trigger for Sustainable Knowledge Base Growth
The effective approach isn't to pre-plan a list of topics, but to let service data dictate it. A simple automatic rule: a case type that has recurred more than five times in a quarter, and whose resolutions aren't linked to an article, gets added to a writing queue.
This ensures the knowledge base reflects actual occurrences, not what was estimated in a planning meeting. An important addition: the agent who wrote an article receives visible credit. Knowledge contributions that aren't recognized anywhere stop after a few weeks.
Article Structure that Supports Both Search and AI
An article written as a continuous document is hard to quickly scan during a call and difficult for a model to retrieve accurately. An effective structure includes: a title phrased as the customer's question, a short answer in the first paragraph, numbered action steps, separate conditions and exceptions, and tagging for product, version, and validity.
Separating exceptions into a distinct section is crucial: when integrated within the steps, both a stressed agent and a retrieval mechanism struggle to distinguish between the rule and its exception.
Visibility: Internal vs. Public
The same topic often requires two versions. The internal version includes known limitations, workarounds, and escalation guidelines; the public version only includes what the customer can perform. This separation is managed at the article level, not the knowledge base level, to prevent two diverging knowledge bases.
Before launching a Self-Service portal, ensure the public versions truly stand alone. A portal that directs to incomplete articles doesn't reduce inquiries; it merely shifts them to another channel, usually phone. The operational context is detailed in Service Cloud Implementation.
What Changes When an AI Agent Reads from the Knowledge Base
A knowledge base that agents manage with despite gaps isn't necessarily ready for an AI agent. An experienced agent knows to disregard an old article; a retrieval mechanism does not.
Three additional requirements: no two active articles provide conflicting answers to the same question; every article has a clear validity and source; and it is explicitly defined what can be presented to the customer. An agent quoting an internal article or combining two conflicting sources creates trust damage that is difficult to repair. In-depth coverage on the subject can be found in Grounding and RAG in Agentforce and Knowledge Readiness for Agentforce.
Measurement
| Metric | What it Reveals | Threshold for Review |
|---|---|---|
| Knowledge attach rate | Is the knowledge base part of the workflow? | Below 30% |
| Searches with no results | Real content gaps | Weekly list for writing queue |
| Articles unviewed in six months | Redundant content or not found in search | Over 25% of the knowledge base |
| Time from creation to publication | Is the approval queue a bottleneck? | Over two weeks |
| "Not helpful" rating | Specific content quality | Concentration on one topic |
The list of searches with no results is the cheapest and most accurate source for content planning, and it's almost always underutilized.
Summary
A successful knowledge base is built from the ground up – from real Cases – and maintained by only two mechanisms: a trigger for creation and a trigger for review. Everything else, including adaptation for use by AI agents, stems from the content being up-to-date and self-consistent.