Service knowledge management system
- Articles the structure implies
- 72
- Hours to write them all once
- 108
- What writing them costs once
- $6,264
The one external figure on this site is a statute, quoted and linked: 44 U.S.C. 3507, the Paperwork Reduction Act, which caps an approved federal information collection at three years so that even a form has to come back and prove it is still needed. The National Archives records control schedules are cited beside it as the other place a review cadence is written down rather than assumed. Everything else on these pages is your own count of categories, articles and owners, with the arithmetic printed next to each figure it produces.
A service knowledge management system is the service desk's version of this idea, and it is a wider thing than a base of articles: it is meant to hold everything the people running a service need to know, including the parts that are not prose. Companies buy it expecting a better help center and find a data problem, because most of what it promises to hold already lives in other systems that were not built to be read.
Open the Knowledge base template Free to use. No account, no card, no sign-up.
Separate the article half from the data half
The prose, how to resolve this, what to tell the customer, what the escalation path is, behaves like any knowledge base and should be built like one. The inventory, what is running, what depends on what, who owns each service, is data with a different update mechanism and a different definition of correct.
Build the article half first
It pays back in weeks, it is written by the people who already answer the questions, and it does not depend on anybody else's system being accurate. Programs that start with the inventory spend a year modeling and never publish an answer, which is the standard failure of this category.
Derive the data half, never declare it
An inventory somebody maintains by hand is out of date within a quarter and everybody learns to distrust it. What survives is derived from something people already update for their own reasons: the deployment pipeline, the monitoring configuration, the on-call rota, the ticket the change went through.
Put the article in the agent's path
The reader here is nearly always somebody with a ticket open, and the base earns its price only if the right article is offered inside the ticket rather than in a second tab. That integration is worth more than any feature on the comparison grid, and it is the first thing to test.
Write down what happens after an incident
The one thing this system can do that a plain base cannot is tie an answer to the event that produced it. Make the review note from an incident an article with an owner rather than a document in a folder, and the next person who hits the same failure finds it by searching for the symptom.
A base the Service knowledge management system does not fit?
Two things the planner does not cover, and they are the two situations people write to us about. The first is a base that is really one enormous category: the arithmetic still runs, but the answer it gives is misleading, because the cost of a hundred articles in one undivided section is not the writing, it is that nobody can find anything and the review load lands on one person. The second is a company whose article owners are contractors rather than staff, where a six-month review cycle collides with contracts that end sooner than that and ownership has to transfer with the work. Tell us which you have and one person reads it: we answer by email, within a working day, and we do not call.
Knowledge bases: the questions that come up
Is this different from a knowledge base?
The article half is the same thing with a narrower reader. What the service framing adds is the inventory and the link between an answer and a service, and that addition is where the effort and the disappointment both live.
Do we need one, or just a base?
If the reader is nearly always an agent with a ticket open, the service desk's own module is usually the right home because the integration is free. If the base also has to serve customers and everybody else in the company, a base with a service desk integration will serve more people.
Where does the configuration inventory belong?
With whatever already knows the truth, and surfaced here by reference. Copying it in creates a second version that is wrong in a different way, and the second version is the one people read because it is the one with a search box.
What should never go in it?
Credentials, and anything whose retention is answered by a records schedule. The system can say where a credential lives and who grants access; holding the credential itself is how it turns up in a search result years after the person who pasted it left.
Kbasevo Pro
Keep the library, and know which articles have gone stale
The planner tells you what the base will cost. Pro is for the month after launch, when the writing is done and the only question left is which of these 72 pages nobody has looked at since.
- Download the plan as a file you can edit, circulate and keep.
- Your plan without our name on the footer of every page.
- Keep this plan, with its version number and the date it was made.
- Your company's name and logo on the plan instead of ours.
- Export every article and every review at once, for a handover or an audit.
- Send the review reminder to the article's owner when it comes due, from inside the workspace.
$29per month, whole team
Start Kbasevo Pro Free for 14 days. No card needed. PricingThe first 14 days are free and no card is asked for. Add a card during the trial and the first charge is on the day it ends; do not, and your workspace becomes read-only with nothing deleted. Kbasevo Pro is $29 a month. It renews on the same date each month at the same price until you cancel, and the price you sign up at is the price you keep for as long as the subscription runs.