Average handle time (AHT) is one of the most closely watched metrics in any call center or contact center. It measures how long each customer interaction takes from start to finish — not just the conversation itself, but the full handling cost including hold time and the work agents do after the call ends. Understanding what AHT is, how to calculate it, and how to manage it without sacrificing quality is essential for any team responsible for contact center performance.

What Is Average Handle Time?

Average handle time is the average total time an agent spends on a single customer interaction. It is a composite metric made up of three distinct components:

• Talk time — the time the agent and customer are actively speaking.
• Hold time — the time the customer spends on hold during the call while the agent researches, escalates, or consults a colleague.
• After-call work (ACW) — the time the agent spends after the call ends completing tasks such as logging notes, updating records, sending follow-up emails, or closing tickets.

AHT is typically measured in minutes and seconds and reported as an average across all calls handled during a given period — a shift, a day, a week, or a month. It applies equally to inbound voice calls, outbound calls, and in some contact centers to digital channels such as chat where a comparable handle-time concept exists.

When people ask "what is AHT in a call center," they are asking about this composite measurement. The term is used interchangeably for both individual agents and entire teams or queues.

Why all three components matter

Talk time alone does not tell the full story. An agent who keeps calls brief but puts customers on hold frequently, or who spends ten minutes after each call updating records, may have a higher total cost per call than their talk-time figure suggests. Measuring only talk time creates incentives to shorten conversations at the expense of hold time or ACW. AHT captures the full picture.

How to Calculate AHT

The AHT formula is straightforward:

AHT = (Total Talk Time + Total Hold Time + Total After-Call Work Time) ÷ Total Number of Calls Handled

All time values must be in the same unit — typically seconds or minutes — before dividing. The result is the average time per call across the measurement period.

Worked example

Suppose an agent handles 40 calls in a shift. Their totals for the shift are:

• Total talk time: 6,000 seconds
• Total hold time: 1,200 seconds
• Total after-call work time: 2,400 seconds

Applying the formula:

• Total handle time = 6,000 + 1,200 + 2,400 = 9,600 seconds
• AHT = 9,600 ÷ 40 = 240 seconds (4 minutes)

To calculate AHT at a team or queue level, sum the talk time, hold time, and ACW across all agents for the period, then divide by the total call count for that group.

Calculating AHT per component

It is useful to track each component separately alongside overall AHT. If AHT rises, knowing which component drove the increase points you toward the right intervention. Rising hold time suggests agent knowledge gaps or slow system access. Rising ACW suggests manual process inefficiencies. Rising talk time may reflect more complex call types or changed routing.

For a broader view of how AHT fits alongside other measurements, see our guide to call center metrics.

AHT Benchmarks by Industry

AHT varies significantly by industry, call type, and the complexity of issues a team handles. The following ranges are general guidance based on commonly reported figures across the industry — they are not authoritative benchmarks, and the right target for any team depends on its specific call mix and customer expectations.

These ranges reflect the mix of call types within each sector. A financial services team handling only high-complexity fraud cases will sit toward the top of its range or above it. A general customer service team with a strong self-service layer that filters simple calls will sit toward the bottom. Use these figures as orientation rather than targets — your own historical trend is a more useful benchmark than any industry average.

Why AHT Matters

Average handle time is not just an operational statistic. It connects to workforce planning, cost, and customer experience in ways that make it one of the most consequential metrics a contact center tracks.

Workforce planning and staffing

AHT is an input to Erlang calculations used to determine how many agents are needed to meet a service level target at a given call volume. If AHT increases by 20%, the same call volume requires more agents to maintain the same answer speed. Accurate AHT forecasting is therefore essential for staffing decisions — both for scheduling individual shifts and for longer-term headcount planning.

When AHT is measured only at the team level, outliers can distort planning. Breaking AHT down by queue, agent, and call type produces more reliable inputs for workforce management.

Cost per call

AHT directly determines how many calls an agent can handle per hour. A lower AHT means more calls handled per agent hour, which reduces the cost per interaction when call volume is constant. For teams measured on cost efficiency, AHT is one of the levers that sits closest to daily operational decisions.

The relationship is not purely linear — a dramatic reduction in AHT achieved by rushing callers often increases repeat calls (callbacks on the same issue), which raises total volume and can increase total cost even as individual AHT falls.

Customer experience

Customers form impressions based on how their call is handled, not on how short it was. A call resolved correctly and efficiently in six minutes produces a better customer experience than a four-minute call that requires a callback. AHT that is managed only downward — without reference to first call resolution (FCR) or customer satisfaction (CSAT) — typically produces worse outcomes on both.

The healthiest teams treat AHT as a diagnostic rather than a target. When AHT rises unexpectedly, they investigate why. When it falls, they verify that quality indicators have held.

How to Reduce Average Handle Time

Reducing AHT effectively means identifying which component — talk time, hold time, or ACW — is driving the figure, and then applying the right intervention. The following tactics address the most common root causes.

1. Skills-based routing

When calls reach agents who are not equipped to handle them, hold time and talk time both increase as agents search for information, transfer calls, or attempt to resolve issues outside their expertise. Skills-based routing matches each call to the agent most qualified to resolve it. First-contact resolution improves, unnecessary transfers drop, and both hold time and talk time decrease.

2. Agent training and knowledge refreshes

Agents who know systems, processes, and common call types handle calls faster and with fewer holds. Regular training — focused on the specific call types showing the highest AHT — reduces the time agents spend searching or escalating. Pairing new agents with higher-AHT call queues before they are fully trained is a common source of elevated team-level AHT.

3. Knowledge base access during calls

Hold time frequently occurs because agents need information they cannot recall or find quickly. A well-structured internal knowledge base — accessible from within the agent desktop with minimal clicks — reduces hold time materially. The key is keeping it current: outdated articles cause agents to doubt the content and either hold to verify or seek another source.

4. AI call summaries to reduce ACW

After-call work is often dominated by note-taking and logging. AI call summaries that automatically generate a structured record of the call — topic, outcome, next steps — can remove a significant portion of ACW without any reduction in call quality. Where agents previously spent two to four minutes logging after each call, AI summaries can compress this to under a minute, with agents reviewing and confirming rather than composing from scratch.

5. Improved IVR to reduce misrouted calls

An IVR that routes calls incorrectly means agents receive calls outside their queue's scope. The agent either handles a call inefficiently or transfers it, adding hold time and sometimes requiring the customer to re-explain their issue. Reviewing IVR routing logic against actual call outcomes identifies where misrouting is adding AHT systematically. See our guide to IVR configuration for more on building routing that reduces transfers.

6. Real-time agent prompts

Real-time guidance tools can surface relevant information to agents during a call — compliance disclosures, product details, troubleshooting steps — based on what is being discussed. This reduces the need for holds and prevents agents from delivering incorrect information that prolongs the call. Real-time prompts are particularly effective for newer agents and for call types with high regulatory or procedural complexity.

7. Streamline wrap-up workflows

ACW is sometimes elevated not because logging is slow but because the post-call workflow requires agents to complete multiple system updates in sequence. Consolidating these into a single interface — or automating the parts that do not require judgment — reduces ACW directly. Audit the steps agents actually take after a call ends before assuming training is the lever.

8. Monitor AHT by call type, not only in aggregate

Team-level AHT masks variation. An overall AHT of six minutes may be driven by a small proportion of complex call types that average fifteen minutes, while straightforward calls average three. Segmenting AHT by call type, queue, and agent allows targeted intervention rather than applying pressure across the board where most agents are already performing well.

AHT vs Other Call Center Metrics

AHT is most useful when read alongside complementary metrics. In isolation it can mislead; in context it becomes a reliable operational signal.

AHT and First Call Resolution (FCR)

First call resolution measures whether the customer's issue was resolved in a single contact without a callback. AHT and FCR have an inverse relationship that must be managed carefully. Reducing AHT by shortening calls without fully resolving issues lowers FCR, increases repeat contact volume, and ultimately increases total handle time across the customer journey. A team with a low AHT but a low FCR rate is not efficient — it is deferring work.

The healthiest signal is both metrics improving together: AHT falling because processes are faster and agents better equipped, while FCR holds or improves because issues are still being resolved on first contact.

AHT and Customer Satisfaction (CSAT)

CSAT measures how satisfied the customer was with the interaction. It is possible — and common — for AHT and CSAT to move in opposite directions when AHT is managed as a target rather than a diagnostic. Agents under AHT pressure may rush callers, skip empathy steps, or close calls before the customer is fully satisfied. Tracking CSAT alongside AHT provides the check: if AHT falls while CSAT holds or improves, the reduction is genuine. If CSAT deteriorates as AHT falls, the reduction is at the customer's expense.

AHT and Occupancy Rate

Occupancy rate measures the proportion of time agents spend in active work (on calls or in ACW) versus available and waiting. High AHT inflates occupancy because each call consumes more agent time, reducing the available time before the next call. When AHT falls, occupancy either falls (agents have more idle time) or call volume absorbs the capacity gain. Workforce managers use AHT and occupancy together to determine whether capacity is in balance with demand.

Frequently Asked Questions