Average Handle Time

Contact Center Field Guide · Foundation 04

Best for: Healthcare executives, contact-center leaders, workforce-management leaders, finance partners, and emerging leaders
Helps with: Workload planning, capacity scenarios, process diagnosis, technology investment, and responsible metric interpretation
Reading time: Approximately 12 minutes
Last reviewed: October 7, 2026

Executive summary

Average Handle Time, usually shortened to AHT, estimates how much employee handling effort the average completed interaction required.

For voice interactions, a common formula is:

AHT = (talk time + hold time + after-contact work) ÷ handled contacts

AHT matters because it converts contact volume into workload. When volume remains constant, an increase in handling time creates more work. A decrease creates potential capacity.

That mechanical relationship sometimes leads leaders to treat lower AHT as an operating objective by itself. This is dangerous. A shorter interaction can reflect a simpler need, better technology, clearer processes, or stronger employee proficiency. It can also reflect rushed conversations, premature transfers, incomplete documentation, or unresolved patient needs.

The right goal is not the lowest possible AHT. The goal is appropriate handling effort that produces accurate, complete, and sustainable resolution.

The concept in plain English

AHT measures time from the employee-work perspective.

For a voice interaction, it often includes:

• time speaking with the patient or customer;
• time placing the interaction on hold; and
• time completing after-contact documentation or work.

Some organizations also treat consultation, conference, or transfer time in particular ways. The local definition must be documented before leaders compare teams, periods, or organizations.

Industry sources describe AHT as both an efficiency measure and an important workload input.¹ That is accurate, but incomplete. AHT also reflects contact mix, process design, system performance, employee proficiency, authority, and organizational complexity.

It is a result produced by the operating system.

The basic calculation

Assume employees handled 1,000 voice contacts with:

• 5,000 minutes of talk time;
• 500 minutes of hold time; and
• 1,000 minutes of after-contact work.

The calculation is:

(5,000 + 500 + 1,000) ÷ 1,000 = 6.5 minutes

The reported AHT would be 6 minutes and 30 seconds, assuming those time components and handled-contact count match the organization's definition.

The calculation says nothing by itself about whether the interactions were resolved, accurate, appropriate, or satisfactory.

Why small changes create meaningful workload

AHT applies across every handled contact included in the calculation. A small per-contact change can therefore produce a large workload change at scale.

Incremental workload = contact volume × change in AHT

Illustrative sensitivity

Illustrative example: These assumptions demonstrate the calculation and are not industry benchmarks. Results estimate workload or potential capacity and may not equal staffing or financial impact.

Assume a contact center handles 100,000 voice interactions per month. Average handle time increases by 30 seconds.

100,000 × 30 seconds = 3,000,000 seconds

3,000,000 ÷ 3,600 = approximately 833 raw workload hours per month

If a fully loaded productive-hour assumption were $30, the workload would carry an illustrative capacity value of approximately $25,000 per month.

That does not mean the organization's monthly expense automatically increased by $25,000.

The operation might:

• absorb the work through existing capacity;
• experience longer waits;
• use overtime or outsourcing;
• defer other activities;
• hire additional staff;
• accept lower service performance; or
• offset the increase through another improvement.

Capacity requirements do not automatically translate into equivalent budget savings or expense. The realized financial effect depends on staffing thresholds, service objectives, overtime, outsourcing, attrition, hiring decisions, and the period evaluated.

What changes AHT

AHT is influenced by far more than employee speed.

Contact reason and complexity

A password reset and a complex billing inquiry should not require the same handling effort. A change in contact mix can raise the overall average even when each type of interaction becomes more efficient.

Patient circumstances

Language needs, accessibility requirements, emotional distress, incomplete information, or the need to coordinate with a caregiver can affect appropriate handling time.

Longer time in these situations may represent necessary service rather than inefficiency.

Process design

Multiple approvals, unclear rules, redundant verification, duplicate documentation, and fragmented ownership add handling effort.

Technology and system performance

Slow applications, several disconnected systems, missing integrations, and poor search can increase talk, hold, and after-contact work.

Knowledge and training

Employees work more efficiently when they can find accurate information and understand how to apply it. Incomplete training can increase holds, consultations, and repeat work.

Authority and routing

An employee may understand the request but lack authority to complete it. The interaction may then require a transfer, consultation, or callback.

Documentation requirements

Some work must be recorded accurately for operational, financial, privacy, or safety reasons. Reducing after-contact work without redesigning the documentation requirement can move the work elsewhere or reduce record quality.

Measurement rules

A platform or policy change can alter the reported metric without changing the patient experience. Examples include changes in wrap codes, conference treatment, abandoned-contact logic, digital concurrency, or when a work item is considered complete.

A healthcare example

Illustrative example: This scenario demonstrates metric interpretation and does not describe a specific organization.

A health system sees AHT increase in its billing queue.

One interpretation is that employees are taking too long.

A better diagnostic review considers several possibilities:

• a new statement format is generating more complex questions;
• patients are calling after failed digital-payment attempts;
• employees must use another system to research balances;
• a policy change requires additional explanation;
• new employees are handling a larger share of contacts;
• repeat callers have unresolved issues; or
• the queue now receives contacts previously handled elsewhere.

If the organization applies pressure to end interactions faster, it may reduce the reported AHT while increasing transfers, repeat calls, complaints, or unresolved balances.

If it corrects the statement, integrates account information, improves knowledge, or routes contacts more accurately, it may reduce both handling time and patient effort.

The metric identifies where to investigate. It does not prescribe the solution.

Why “lower is better” fails

The lowest achievable AHT would result from ending every interaction immediately. That would obviously fail the service purpose.

The meaningful question is whether the time produced an appropriate outcome.

Lower AHT can be positive when it comes from:

• fewer system steps;
• better routing;
• clearer knowledge;
• reduced hold time;
• simpler authentication;
• less duplicate documentation;
• effective self-service before escalation; or
• greater employee proficiency.

Lower AHT can be harmful when it comes from:

• rushing the patient;
• skipping discovery;
• transferring work prematurely;
• incomplete documentation;
• discouraging complex contacts;
• ending the interaction before the patient understands; or
• failing to complete the underlying task.

Research on customer retrials is relevant here. Customers may initiate another contact when a prior interaction does not provide satisfactory resolution.² A shorter first interaction can therefore create additional future workload if it leaves the need open.

What AHT does not tell us

AHT does not establish:

• whether the patient's need was resolved;
• whether the information was accurate;
• whether the employee followed required processes;
• whether the patient understood the outcome;
• how much effort the patient experienced;
• whether another contact will occur;
• whether longer time was clinically, legally, or operationally appropriate;
• whether the employee had functional systems and accurate knowledge; or
• whether a workload change became a financial change.

An average also does not show the distribution. Two teams may report the same AHT while handling very different work. One may have tightly clustered interactions. Another may have many brief contacts and a smaller number of very long complex contacts.

Measures to consider alongside AHT

Resolution and repeat contact

Did the organization complete the underlying need, and did the patient need to return?

Transfers

Did the employee resolve the request or move the remaining work elsewhere?

Quality and accuracy

Did the interaction follow policy, document the work correctly, and provide accurate information?

Patient effort and experience

Did the patient understand what happened and what to do next? How many steps, channels, or explanations were required?

Employee experience

Does the handling-time expectation allow employees to complete complex work responsibly? Are systems and processes adding avoidable effort?

Contact mix

Did the proportion of simple and complex work change?

Talk, hold, and after-contact components

The total AHT can remain stable while one component worsens and another improves. Component analysis often points more directly to the cause.

Workload and interval demand

What capacity effect does the change create at the actual volume and timing of work?

Digital-channel complications

AHT definitions become more difficult outside voice.

An employee may manage several chat conversations concurrently. A messaging interaction may remain open for hours while containing only a few minutes of active employee work. An email may sit in a queue before an employee begins working it.

For digital channels, leaders should define:

• whether the measure uses elapsed time or active work time;
• how concurrency affects employee effort;
• when the interaction starts and ends;
• whether waiting for the customer counts;
• how transfers or escalations are treated; and
• which after-contact activities are included.

A vendor-neutral comparison requires documented definitions. A number called AHT may represent different operating realities across platforms.

Responsible improvement

The most sustainable way to improve AHT is to remove work that does not contribute to resolution.

Useful targets include:

• redundant verification;
• slow system navigation;
• duplicate data entry;
• unnecessary holds;
• unclear knowledge;
• avoidable transfers;
• incomplete upstream information;
• preventable repeat contacts; and
• documentation that can be simplified without compromising accuracy or control.

The improvement test should examine more than the time metric.

1. Did handling effort decrease?
2. Did resolution remain stable or improve?
3. Did repeat contact or transfer behavior worsen?
4. Did quality, accessibility, or patient effort change?
5. Did employees experience less friction or simply more pressure?
6. Did the organization realize capacity, financial value, or another operational benefit?

Questions leaders should ask

1. What exact time components and contacts are included in our AHT definition?
2. Has contact mix or complexity changed?
3. Which AHT component moved: talk, hold, or after-contact work?
4. What do distribution and percentile views show beyond the average?
5. How do AHT changes relate to resolution, repeats, transfers, quality, and patient effort?
6. Are employees compensating for process, knowledge, or technology failures?
7. Which longer interactions are appropriate and necessary?
8. Does the analysis describe raw workload, required capacity, expense, or realized savings?
9. What behavior might an AHT target unintentionally encourage?

Decisions this concept should inform

AHT should inform:

• workload forecasts;
• staffing and capacity scenarios;
• process and technology investments;
• routing and skill design;
• knowledge-management priorities;
• training and coaching;
• automation evaluation;
• financial sensitivity analysis; and
• investigation of changes in contact complexity.

It should not function as a standalone employee-performance target.

Illustrative-model policy: Calculations demonstrate operating relationships and are not industry benchmarks. Results estimate workload or potential capacity under stated assumptions and may not equal actual staffing or financial impact. Leaders should substitute local demand, handling, workforce, service, and cost assumptions before making decisions.

This entry addresses contact-center operations and does not provide clinical, legal, or regulatory advice.