Average Handle Time (AHT) tells you the average handling time per contact. For a typical voice operation, the calculation combines talk time, hold time, and after-call work, then divides that total by the number of handled calls.
This guide walks through a complete example, explains the difference between decimal minutes and minutes-and-seconds, and shows why averaging individual AHT figures can produce the wrong team result. The figures are illustrative, not industry benchmarks.
The AHT formula
AHT = (total talk time + total hold time + total after-call work) ÷ total contacts handled
Talk time covers the conversation, hold time covers periods when the customer is placed on hold, and after-call work (ACW) covers tasks such as notes and disposition after the conversation. Check your reporting definitions: component names and treatment can vary between systems.
Use totals from the same period, queue, channel, and contact population. For example, a daily report should not combine today’s talk time with a weekly contact count. Keep all durations in one unit before adding them.
Worked example: 6 minutes 30 seconds
Imagine a team handled 100 calls during one reporting period. Its time totals are shown below.
| Component | Total duration | Total minutes |
|---|---|---|
| Talk time | 8 hr 20 min | 500 |
| Hold time | 50 min | 50 |
| After-call work | 1 hr 40 min | 100 |
| Total | 10 hr 50 min | 650 |
AHT = 650 minutes ÷ 100 calls = 6.5 minutes per call.
Convert the decimal part into seconds: 0.5 × 60 = 30 seconds. The result is therefore 6 minutes 30 seconds, or 390 seconds.
The same calculation in seconds is (30,000 + 3,000 + 6,000) ÷ 100 = 390. Converting the totals first gives the same answer and can make comparisons with a seconds-based report easier.
Decimal minutes are not minutes-and-seconds
A value of 6.5 minutes means 6 minutes 30 seconds. It does not mean 6 minutes 5 seconds or 6 minutes 50 seconds. The decimal represents a fraction of a minute, and each full minute contains 60 seconds.
Similarly, 6.30 decimal minutes equals 6 minutes 18 seconds: 0.30 × 60 = 18. If a report shows “6:30”, check that the format means minutes:seconds before converting or comparing it.
For spreadsheet exports, label the unit in the column heading—for example, “AHT (seconds)” or “AHT (decimal minutes)”. A clear unit prevents a correct value from being interpreted incorrectly.
Calculate team AHT from totals
A simple average of agent AHT values can be misleading when those agents handled different numbers of contacts. Consider two agents: Agent A handled 10 calls at an AHT of 300 seconds, while Agent B handled 90 calls at an AHT of 600 seconds.
Their handling totals are 10 × 300 = 3,000 seconds and 90 × 600 = 54,000 seconds. Together, they handled 100 calls in 57,000 seconds.
Team AHT = 57,000 ÷ 100 = 570 seconds, or 9 minutes 30 seconds.
Simply averaging 300 and 600 gives 450 seconds, which is incorrect for this team. That method gives the two agents equal influence despite their different call volumes. Use original time totals where possible; reconstructing totals from rounded AHT values can introduce small differences.
The same principle applies when combining days, shifts, or queues. Add compatible handling-time totals and contact counts before calculating the combined average.
Use the CX Metric Works AHT Calculator
Open the AHT Calculator and enter the totals for your reporting period. To reproduce the first example, enter:
Talk time: 8 hours, 20 minutes, 0 seconds.
Hold time: 0 hours, 50 minutes, 0 seconds.
After-call work: 1 hour, 40 minutes, 0 seconds.
Contacts handled: 100.
Calculate and check the result against 6 minutes 30 seconds. Enter total durations for the period, rather than the average talk, hold, or ACW duration per contact.
If you have an agreed target, add it for comparison. With an illustrative target of 6 minutes, the result is 30 seconds above target. That difference identifies a question to investigate; it does not identify its cause.
Check these common input problems
Zero handled contacts: AHT cannot be calculated because division by zero is undefined. Report the value as unavailable rather than interpreting it as zero seconds.
Missing time: A blank or missing reporting component is not evidence that no time was spent. Confirm whether a zero is a genuine measured value or a data-quality issue before using it.
Overlapping components: Check whether your source report already includes hold or wrap-up time in another total. Adding an included component again would count the same time twice.
Different contact definitions: Confirm whether the report counts unique customer interactions or agent-handled segments after transfers. Use the count that matches the handling-time totals.
Interpret the result alongside quality
AHT measures time, not whether the customer received a complete answer. Compare similar work and review quality, resolution, and repeat contacts before deciding that a lower number represents improvement.
For example, if a team’s AHT rises by 20 seconds, break the change into talk, hold, and ACW. If ACW alone rose by 20 seconds while the other components stayed flat, review documentation steps first. Treat this as a starting hypothesis and check interactions before drawing a conclusion.
For chat and asynchronous messaging, use your platform’s handling-time definition. Concurrent conversations and elapsed waiting periods need different treatment from a straightforward voice calculation.
Try the worked example
Use the free AHT Calculator to check your totals and compare the result with your target. To understand the quality side of performance, read our guide to weighted QA scores and critical errors.
Further reading: NiCE’s explanation of Average Handle Time covers the voice formula and channel-specific considerations. The worked calculations in this guide are original illustrative examples for CX Metric Works.