Average Handle Time (AHT): Full Form, Formula and Examples

Updated October 2026.

Picture a queue of customers and an agent who needs a few extra minutes to find one policy detail. Multiply that delay across a shift, and the whole queue slows down. Average handle time (AHT) is the metric that makes this visible. This guide therefore explains what it means, how to calculate it and how to bring it down responsibly.

Average handle time: the short answer

AHT stands for average handle time, also written average handling time. It is the average time an agent spends on one customer interaction, counting talk time, hold time and after-call work. The AHT formula is total handle time divided by the number of interactions handled. Teams report the result in minutes or seconds.

AHT full form and meaning

The AHT full form in a call center is average handle time. In BPO and contact center work, people say AHT, average handling time or handle time. They all mean the same thing. It measures how long one interaction occupies an agent. The clock runs from the moment the customer connects until the agent finishes the follow-up work, so a call that ends at minute five can still count as seven.

Handle time has three parts:

• Talk time. The time the agent speaks with the customer.
• Hold time. The time the customer waits while the agent looks for an answer or consults someone.
• After-call work (ACW). The notes, ticket updates and follow-up tasks the agent completes once the call ends. Our guide to after-call work covers how to shorten this part.

However, AHT only tells half the story. It helps you judge agent efficiency and plan staffing. Speed alone does not show whether the customer got a correct answer, a complete answer, or an answer they will not need to call back about. For that reason, read it beside the other call center metrics you track.

AHT vs related call center metrics

People often confuse AHT with the metrics that feed into it. The table below separates them, since each one answers a different question.

AHT formula

Use this formula to calculate average handle time:

AHT = (Total talk time + Total hold time + Total after-call work) / Number of interactions handled

Some teams also add transfer time or leave out idle time. Because of that, write down your definition and apply it the same way every period. Otherwise, trends mean nothing at all.

Steps to calculate AHT

1. Add up the total handle time. Sum talk time, hold time and after-call work for the period. Include every call, not a sample. Otherwise, the average is skewed by the calls someone chose to pull.
2. Count the interactions handled. Take the same period and the same queue.
3. Divide. Total handle time divided by interactions gives the average.

AHT formula in BPO: a worked example

The numbers below are illustrative, not a benchmark. For instance, say a BPO agent handles 120 calls in one shift with these totals:

The calculation is 720 minutes divided by 120 calls, which gives an AHT of 6 minutes, or 360 seconds, per call. Since most BPO dashboards report seconds, convert at the end by multiplying minutes by 60, and keep the same unit across every report so that two managers never compare 6 against 360 by mistake.

How to calculate AHT in Excel

To start, put talk time in column B and hold time in column C. Next, add after-call work in column D and the call count in column E, with one row per agent or per day. Next, enter =(B2+C2+D2)/E2 in column F and copy it down. For a team average, divide the sum of all handle time by the sum of all calls, for example =SUM(B2:D20)/SUM(E2:E20). Do not average the individual AHT values. An agent with 10 calls would then count as much as one with 200, which distorts the result in ways that are hard to spot in a summary table.

How to set a good average handle time target

There is no single good number, and anyone who quotes one without context is guessing. A password reset and a billing dispute take very different amounts of time. Likewise, a healthcare line differs from a retail line. A useful target therefore comes from your own history, split by call type. In addition, a drop in AHT only counts as progress if first call resolution and customer satisfaction hold steady.

That is why many teams track AHT next to first call resolution. Rushing a call can push AHT down while repeat calls push total workload up. For example, if an agent skips a verification step to save 30 seconds and the customer calls back, the issue now costs two calls instead of one.

How to read AHT by call type

A single team-wide number is a starting point, not an answer. Because call types differ so much, split the figure before you act on it. First, group calls by reason, such as billing, technical faults, order status and account changes. Afterward, calculate AHT for each group. In addition, use the same formula every time.

In practice, the split usually shows that a few call types account for most of the total handle time. For example, if billing calls average 9 minutes and order status calls average 3 minutes, a team-wide average of 5 minutes hides both facts. You can fix the long calls with better guidance. Leave the short ones alone. Compare each group with its own past results, not the team average. Therefore, targets stay fair, and agents who handle the hardest call types are not judged against agents who handle the easiest.

Why average handle time matters

AHT earns its place on the scorecard for five reasons:

1. Efficiency measurement. A high AHT can show that agents struggle with certain issues. So, coaching helps.
2. Resource allocation. Staffing models depend on it. If a team takes 1,200 calls a day at 6 minutes each, the workload is 7,200 minutes, or 120 hours, before planners add breaks, training and absence.
3. Cost management. Shorter calls free capacity. Aggressive targets, however, cause rushed calls and callbacks.
4. Customer satisfaction. Customers like quick answers. They also want thoroughness, and a rushed agent who misses the real problem creates a second call that costs more than the minute saved.
5. Performance benchmarking. It gives a consistent measure for comparing agents, queues and months against internal goals, provided the definition stays fixed and the comparison accounts for the mix of call types each agent or queue received during the period being reviewed.

How AHT is used in a BPO

In a BPO, handle time often sits inside the client contract. The client pays for agent time and wants to know how much of it each interaction consumes, how that figure moves from month to month, and whether any rise comes from harder calls or from slower handling. As a result, AHT shapes staffing, pricing and the daily targets that supervisors track. Although a tight target looks efficient, it can backfire when agents feel pressure to end calls early. Instead, agree on a range by call type. Review it whenever the product, the process or the tools change. Meanwhile, keep quality scores and first call resolution on the same dashboard. That way, a faster average never hides a worse customer outcome, a repeat contact, or a complaint that surfaces a week later through another channel.

Common mistakes when measuring AHT

Most AHT problems, though, come from how the number is used. The arithmetic is rarely the issue. Watch for these:

• Averaging across very different calls. A blended figure hides the fact that one call type may be far longer than the rest. Split AHT by reason for contact.
• Punishing agents for long calls. Complex calls are sometimes the right calls, so penalizing them only teaches agents to transfer or end calls early, which pushes the cost onto another queue and onto the customer.
• Ignoring after-call work. Wrap-up time is easy to overlook. Yet it can be a large part of the total.
• Changing the definition mid-year. If one report counts transfers and the next does not, the trend means nothing.
• Chasing AHT alone. Without a quality measure beside it, a lower number can hide worse service.

How to reduce average handle time

Lower AHT comes from removing delays inside a call. Telling agents to talk faster does not work. These changes usually matter most:

• Train on the real top call reasons. Product knowledge and troubleshooting practice help agents find solutions without switching between screens.
• Give agents one searchable knowledge base. When answers sit in one place, hold time and search time fall.
• Script the routine calls. Structured prompts keep conversations focused and cut back-and-forth.
• Teach root cause questions. Active listening and good questions get to the problem sooner.
• Automate the routine. Call routing, customer information pop-ups and AI tools handle simple requests and reduce lookup time.
• Watch the trend by call type. Over time, a rise in one queue shows where the bottleneck sits. It may be one agent, one process or one missing article.
• Ask customers. Feedback shows which parts of the call frustrate them.

The knowledge base point deserves extra attention, because findability is where most delay hides. In a Gartner self-service survey, 43% of failed self-service attempts happened because customers could not find relevant content. Agents hit the same wall when answers are scattered across tools, so every search adds hold time. Our guide on how to reduce AHT goes deeper on fixing it.

Technology points the same way. Similarly, Gartner research expects knowledge management systems, live chat and self-service portals to surpass phone and email as the most valuable customer service technologies by 2027. Teams that organize answers now will find AHT easier to control later.

Reduce AHT with Knowmax

Knowmax is an AI-powered knowledge management platform that sits beside your CRM or help desk, which means agents keep the tools they already know while gaining one place to find verified answers during a live call. Agents search one call center knowledge base, follow guided workflows for common queries and see AI suggestions during the call. As a result, search time and hold time fall.

Training is the other lever. For example, new agents who learn from the same guided content that experienced agents use ramp up faster. Meanwhile, customers can resolve simple questions through self-service, so fewer calls reach an agent at all. With every deflected call one less contact in the queue, the remaining calls are also more likely to be the complex ones that deserve more time. If you are comparing options, start with this overview of knowledge management software.

Coaching and content ownership

Finally, coaching matters. As Gartner found that 58% of service leaders aim to upskill agents into knowledge management specialists, agents who help maintain articles are also the ones who spot the gaps that lengthen calls. As a result, handle time falls where the content improves, and not just where the agent speeds up.

In short, treat AHT as a diagnostic, not a verdict. Fast is good. Right is better. So, measure both. The strongest contact centers measure both together, review the numbers by call type every month, and fix the knowledge, process or tool gap behind a long call before they ever coach the agent who happened to take it. It points to a problem. It never names the cause, and that takes a closer look at the calls behind the number. When it rises in one queue, look first at the knowledge, the process and the tools. Then look at the individual agent.

Frequently asked questions about average handle time