WFM guideFCR & AHT

Contact centre knowledge management

Q: How does a knowledge base reduce contact centre AHT?

A knowledge base reduces contact centre AHT primarily by reducing the time agents spend searching for information during a contact (hold time / dead air) and by reducing after-call work (ACW). When agents can find the correct answer within 10–20 seconds using an effective knowledge base, hold time drops from a typical 45–90 seconds per contact (poor knowledge access) to 10–20 seconds (effective knowledge base). For an operation with average 8-minute AHT, hold time accounts for 30–60 seconds (6–12% of AHT). Eliminating most of that hold time through better knowledge access reduces AHT by 5–8%, which at 100 agents translates to approximately 2–4 fewer agents required at the same service level.

Q: What is a knowledge management governance model for a contact centre?

Knowledge management governance defines who owns content, who reviews it, and how frequently. The most effective model for a contact centre of 50–500 agents is: (1) a designated Knowledge Manager or Knowledge Champion role (part-time or full-time depending on size) responsible for the knowledge base as a system; (2) subject matter experts (SMEs) per product or process area who own and maintain specific content sections; (3) a formal review cadence (typically quarterly for evergreen content, triggered reviews for regulatory or product changes); and (4) a feedback loop from agents — rated articles, flagged errors, and gaps surfaced from quality monitoring. Without a governance model, the knowledge base grows stale within 6–12 months and becomes a source of incorrect information rather than a solution.

A knowledge base is not a reference library — it is a live operational tool that directly determines how long contacts take and how often they are resolved first time. Poor knowledge access drives hold time, incorrect information, callbacks, and early-tenure attrition. Good knowledge access reduces AHT by 5–10% and raises FCR by 5–15 percentage points.

Impact on AHT and FCR

Worked example: 100-agent operation, 8-minute AHT, 75% FCR

Poor knowledge access

Avg hold time per contact75 sec

Knowledge search time (ACW)40 sec

Incorrect info rate8%

Repeat-contact rate (FCR failure)25%

Blended AHT8.0 min

FCR75%

Effective knowledge base

Avg hold time per contact18 sec

Knowledge search time (ACW)10 sec

Incorrect info rate2%

Repeat-contact rate (FCR failure)15%

Blended AHT7.2 min

FCR85%

AHT reduction of 0.8 min (10%) at 100 agents → Erlang C requirement drops by approximately 8 agents at the same service level target. FCR improvement of 10pp → repeat contact volume falls by 10%, reducing total volume and further reducing staffing requirement. Combined WFM impact of a well-maintained knowledge base at 100 agents: approximately 10–15 FTE reduction or equivalent capacity reallocation.

Identifying knowledge gaps

Knowledge gaps show up in operational data before agents raise them explicitly. Four data sources identify gaps faster than agent surveys:

AHT variance by agent cohort

Experienced agents (12+ months tenure) have internalised the knowledge base. New agents (0–6 months) rely entirely on it. If new-agent AHT is more than 20% above experienced-agent AHT and the gap is not narrowing, the knowledge base is failing new starters.

Action

Extract the top 20 contact types by volume and measure AHT for new vs. experienced agents on each. Contact types with the largest AHT gap are the knowledge gap priority list.

Hold time analysis by contact type

High hold time on a specific contact type indicates agents cannot find the answer quickly. Hold time above 60 seconds on a contact type is a flag for a knowledge gap or a knowledge base findability problem.

Action

Pull hold time by contact type / wrap code from the ACD. Sort by average hold time descending. The top 10 by hold time are the knowledge base rebuild priority list.

Repeat-contact / recall analysis

A contact that repeats within 7 days on the same issue indicates FCR failure. A significant proportion of FCR failures are caused by the agent providing incorrect or incomplete information — which traces back to knowledge quality.

Action

Run a repeat-contact report filtered to contacts that repeated within 7 days on the same contact reason. Sample the recordings from the initial contact: was the agent using the knowledge base? Was the information there? Was it correct?

QA monitoring flags

Skilled quality assessors will flag contacts where the agent gave incorrect information or took excessive hold time. A pattern of flags on the same topic identifies a systematic knowledge gap rather than individual agent error.

Action

Tag QA findings by root cause: agent error (knowledge existed but not used) vs. knowledge gap (knowledge did not exist or was wrong). Track knowledge gap findings by contact topic. These feed directly into the knowledge update queue.

Knowledge base design principles

Principle	What it means	Common failure
Findable in under 10 seconds	An agent under the stress of a live call should be able to locate the correct article in under 10 seconds. This means effective search (keyword-indexed, not just title search) and a shallow hierarchy (max 3 clicks to any article).	Deep folder hierarchies and poor search mean agents give up and either hold the customer or guess. This is the most common reason knowledge bases fail in practice.
Layered content (TL;DR first)	Every article should open with a 1–2 sentence answer to the most common question. Full detail follows. Agents in a hurry should not have to read the full article to find the quick answer.	Articles written by subject matter experts are typically comprehensive but agent-hostile — the quick answer is buried in paragraph 4.
Plain language (not internal jargon)	Articles should use the same language the agent uses on the call — and the same language the customer uses to describe their issue. Technical product names, internal system names, and policy codes should be secondary, with the plain-language term primary.	New agents cannot map customer language to internal jargon. They search using the customer's words and find nothing — then give up on the knowledge base entirely.
Decision trees for complex processes	Multi-step processes with conditional logic (e.g., eligibility checks, complaint triage, FCA suitability assessments) should be structured as decision trees, not prose. The agent clicks through the tree on the call.	Process articles written as prose paragraphs require the agent to hold the customer while they read and parse the decision logic. Decision trees reduce processing time by 30–50% for complex contacts.
Maintained, not just published	A knowledge base without governance becomes misinformation within 6–12 months. Every article needs an owner, a review date, and a last-verified date visible to the agent.	The most dangerous contact centre failure mode is agents confidently using a knowledge base article that is 18 months out of date. FCR falls, complaints rise, and the root cause is not visible in AHT data alone.

Governance model

Knowledge Manager

50+ agents

The knowledge base as a system. Search relevance, article quality standards, governance cadence, gap analysis. Not responsible for writing all content — responsible for ensuring content is written, reviewed, and maintained.

Full-time at 200+ agents. Part-time (0.5 FTE) at 50–200 agents.

Subject Matter Expert (SME)

Per product/process area

Content accuracy for their domain. Writes first drafts of new articles for their area. Reviews articles on the quarterly governance cycle. Flags triggered updates when products or regulations change.

Typically 2–4 hours/week per SME. SME role is secondary to their primary operational or product role.

Agent feedback loop

All agents

Surfacing gaps and errors. Every article should have a 'Was this helpful?' rating and a feedback field. Agents who find a wrong or missing article should have a 1-click route to flag it. The Knowledge Manager triages flags within 48 hours.

30–60 seconds per flag submission. Aggregate feedback review: weekly for the Knowledge Manager.

Knowledge management questions

How does a knowledge base reduce contact centre AHT?

Primarily by reducing hold time (agents searching for information during a call) and ACW (post-call documentation uncertainty). Poor knowledge access: 75-second hold time. Effective knowledge base: 18-second hold time. At 8-minute average AHT, this represents a 10% AHT reduction — approximately 8 fewer agents required for 100-seat operation at the same service level.

What is a knowledge management governance model for a contact centre?

A Knowledge Manager (full-time at 200+ agents, part-time below), SMEs per product/process area who own and review their content sections on a quarterly cadence, and an agent feedback loop (rate articles, flag errors). Without governance, a knowledge base becomes misinformation within 6–12 months. Stale knowledge is the most dangerous failure mode: agents confidently deliver incorrect information because they trust the knowledge base.