Knowledge management: the quiet lever on AHT, FCR and ramp
The system planners never look at, that moves their numbers
Workforce planners spend their days on volume, handle time, shrinkage and headcount. Almost none of them spend any time on the knowledge base — the search tool, the procedure articles, the decision trees an agent reaches for mid-contact to find the answer. That is a blind spot, because the quality and accessibility of that knowledge quietly drives three numbers the planner cares about a great deal: average handle time, first contact resolution, and how long a new starter takes to become productive. Fix the knowledge and all three move in your favour; leave it broken and you are forever staffing around the cost of agents who cannot quickly find what they need.
What good knowledge does to the planning numbers
Start with handle time. A large part of many contacts is not talking to the customer; it is the agent hunting — searching, reading, asking a colleague, checking they’ve got it right. When the answer is one clean search away, that hunt collapses and AHT falls; when the knowledge base is a sprawl of out-of-date, contradictory articles, the hunt expands and AHT climbs, contact after contact, all day. Because AHT feeds straight into the staffing requirement, a knowledge problem is a staffing problem wearing a disguise.
Then first contact resolution. An agent who can’t find the right answer either gives the wrong one or promises to call back — and both create a repeat contact. Good knowledge is one of the most direct routes to resolving more contacts the first time, which means less repeat volume to forecast and staff. And finally ramp: a new starter on a great knowledge base can handle far more, far sooner, because the system carries the knowledge they haven’t built yet. On a poor one, the only path to competence is months of slowly memorising what the tool should have told them — a longer, more expensive ramp curve, every cohort.
Why it decays, and who should care
Knowledge bases rot. Products change, policies update, processes get rerouted — and the article describing the old way sits there, authoritative-looking and wrong, until an agent follows it and creates a failure. Nobody owns the decay, because knowledge sits awkwardly between operations, training, product and IT, and so it quietly degrades while everyone assumes someone else is tending it. The symptom the planner sees is a slow, unexplained drift upward in AHT and downward in FCR that no amount of coaching or staffing fixes — because the cause isn’t the agents, it’s what they’re working from.
This is where the planner has a part to play that nobody expects of them. You are the function that can quantify the cost of bad knowledge — the AHT minutes lost, the repeat contacts generated, the extra ramp weeks per cohort — and turn an abstract “our knowledge base is a mess” into a business case with a number on it. Few things move an organisation to invest in something unglamorous like knowledge management faster than a planner showing, in agent-hours and pounds, what its neglect is costing.
The practical stance
You don’t have to own the knowledge base to use it as a planning lever. Watch AHT and FCR by contact type for the drift that signals knowledge decay. When a new process or product lands, treat the knowledge update as part of the change — an un-updated knowledge base is an AHT and FCR event you can forecast. And when you build the case for any AHT or FCR improvement, put knowledge on the list of causes, because it is frequently the cheapest fix available and the one nobody thought to cost. The planner who connects the knowledge system to the staffing maths is sizing a lever most operations leave completely untouched.
Pair this with forecasting AHT, first contact resolution, and the new-hire ramp curve.