Average Handle Time (AHT) — what it is and how to reduce it
AHT is the most powerful lever in contact centre workforce planning. A 10% reduction in handle time is operationally equivalent to adding 10% more agents, except it reduces cost rather than increasing it. But driven the wrong way, AHT reduction destroys quality. Here's how to do it right.
What is AHT?
Average Handle Time is the mean time an agent spends on a single contact from first answer to completion of all post-contact work. It is the product of three components:
AHT as a staffing multiplier
AHT is one of two inputs to Erlang C (the other is volume). Traffic intensity, the core Erlang C input, is calculated as:
Because AHT appears in the numerator, it has an approximately 1:1 relationship with staffing requirement at constant volume:
−10% AHT
~−10% agents needed
+10% AHT
~+10% agents needed
+20% AHT
+20–25% agents (non-linear at high occupancy)
The relationship is not perfectly linear: at high occupancy, AHT increases have a larger-than-proportional impact on service level. Use the AHT impact calculator to model the exact effect for your operation.
AHT benchmarks by contact type
The AHT benchmark trap
Comparing your AHT against an industry benchmark without controlling for contact complexity is misleading. A centre handling billing disputes will always have higher AHT than one handling delivery status queries. Compare against your own operation's baseline and trend, not a generic number.
8 ways to reduce AHT without hurting quality
The core rule: AHT reduction is safe when FCR holds or improves. If repeat contact rate rises as AHT falls, you have pushed too hard. Monitor FCR alongside AHT in every reduction programme.
Knowledge base access during contacts
Agents who can find accurate answers in under 30 seconds don't put customers on hold for 90 seconds while they search. A well-structured, searchable KB directly attacks hold time. Monitor: hold time rate before and after KB rollout.
Screen population and CTI integration
Automatic screen pop, which displays the customer's account before the agent says 'hello', removes 30–90 seconds of 'may I have your account number' and data entry from every contact. Requires CRM/telephony integration.
After-call work (ACW) reduction
Standardised wrap codes (rather than free-text notes), auto-logging from CRM, and one-click case closure can cut ACW by 30–50%. ACW is often the largest quick win in AHT reduction programmes.
Call structure and navigation coaching
Training agents on efficient call structure (opening, discovery, resolution, close) without sounding scripted. Monitor whether coached agents produce the same FCR as uncoached agents at lower AHT.
Reduce unnecessary hold time
Warm transfer protocols (briefing the receiving team before transferring), colleague messaging instead of hold, and escalation decision trees all reduce average hold time without affecting resolution quality.
IVR / digital deflection for simple contacts
Moving balance enquiries, delivery status, and simple resets to self-service changes the mix of contacts that reach agents, raising average AHT on the remaining contacts while reducing total volume. Not a pure AHT win, but a significant cost reduction.
Reduce repeat contacts (improve FCR)
Each repeat contact is a full extra AHT. A 5% FCR improvement removes 5% of total volume, which reduces average AHT indirectly if repeat contacts are proportionally longer. More importantly, it reduces total staff cost.
Skill-based routing improvements
Routing contacts to the most relevant skill group reduces handle time for complex contacts and avoids AHT inflation from misrouted calls. Well-calibrated routing reduces transfers, escalations, and frustrated repeat contacts.
The AHT / quality tension
Cutting AHT through time pressure — monitoring agent-by-agent AHT and creating a culture where agents rush to close contacts — reliably damages quality. Agents skip verification, give incomplete answers, and fail to identify upsell or retention opportunities.
Safe AHT reduction
- • Process and tooling improvements (KB, screen pop, ACW)
- • Coaching on efficient call structure
- • Reducing unnecessary hold time
- • FCR holds or improves
Dangerous AHT reduction
- • Time pressure and agent-level AHT targets
- • Coaching agents to close contacts before resolution
- • FCR declining as AHT falls
- • CSAT declining as AHT falls
Frequently asked questions
What is Average Handle Time (AHT)?
Average Handle Time (AHT) is the mean time an agent spends on a single contact from the moment they answer it to the moment they finish all associated work. It includes talk time (or active handling time for non-voice channels), hold time, and after-call work (ACW). AHT is one of the two main inputs to Erlang C — the formula used to calculate contact centre staffing requirements.
What is a good AHT for a contact centre?
There is no single 'good' AHT — it depends entirely on the contact type and product complexity. Simple transactional calls (balance enquiries, address changes) average 2–4 minutes. General customer service averages 4–8 minutes. Technical support typically runs 8–15 minutes. Chat contacts average 8–14 minutes including response lag. AHT benchmarks are only meaningful within your own operation, compared to your own baseline. Comparing against other operations without controlling for contact complexity is misleading.
How does AHT affect staffing?
AHT is a direct multiplier on staffing requirement. Traffic intensity (Erlangs) = contact volume × AHT ÷ interval length. A 10% increase in AHT produces approximately a 10% increase in traffic intensity and, at typical occupancy, roughly a 10% increase in seated agents required. The relationship is not perfectly linear: at high occupancy, an AHT increase has a larger-than-proportional impact on service level and queue depth. The AHT impact calculator models this non-linearity.
How do you reduce AHT without hurting quality?
The most effective AHT reduction techniques that do not harm quality: (1) Knowledge base access during calls, so agents can find answers quickly without putting customers on hold. (2) Screen population automation, pre-filling customer data so agents spend less time searching. (3) ACW reduction through standardised wrap codes, auto-logging, and one-click case closure. (4) Call structure coaching that helps agents guide calls efficiently without sounding scripted. (5) Quality-calibrated monitoring that ensures reduced AHT does not come at the cost of repeat contacts. The test is always whether FCR holds as AHT falls.
See the staffing impact of your AHT change
Enter your current volume, AHT, and service level target. Compare before and after with exact agent counts and occupancy.
Open the AHT impact calculator →Related
AHT impact calculator
Model the staffing effect of AHT changes
Erlang C calculator
Full staffing from volume, AHT, and SL target
Erlang C explained
How AHT feeds the staffing formula
Contact centre metrics
AHT in the context of all 10 KPIs
Service level explained
The target AHT planning must hit
AHT in the glossary
Quick-reference definition