Talk or chat time
Time spent actively communicating with the customer.
Enter conversation volume, average talk or chat time, hold time, wrap-up time, and estimated automation level. See the average time for one conversation, monthly workload, and conversations represented by the automation scenario.
The automation percentage estimates volume, not guaranteed time savings. Automated conversations may still require monitoring, escalation, or human follow-up.
Average handle time, or AHT, is the average handling time required to complete one customer interaction. Service teams use it to understand workload and identify where agents spend time.
Time spent actively communicating with the customer.
Time on hold while the agent researches or completes a task.
Immediate after-contact work such as notes, CRM updates, tags, or follow-up.
Teams can adapt this call-center metric to live chat and messaging, but should define it consistently within each channel. Read Zendesk’s AHT guidance.
Use completed conversations from a typical month; do not mix in abandoned or unanswered contacts.
For messaging, use active agent handling time—not elapsed time while waiting for the customer.
Include research or consultation time. Enter zero when it is irrelevant.
Include immediate notes, CRM updates, tagging, and follow-up tasks.
Estimate the share represented by automation. It does not promise the same percentage reduction in workload.
Average talk or chat time + Average hold time + Average wrap-up time
Monthly conversations × Average handle time ÷ 60
Monthly conversations × Automation level
(Total talk + Total hold + Total wrap-up) ÷ Handled conversations
Both AHT approaches agree when inputs use the same period and definitions.
Suppose a team handles 3,000 monthly conversations with six minutes of talk or chat, 1.5 minutes of hold, and two minutes of wrap-up work.
AHT: 6 + 1.5 + 2
Monthly workload: 3,000 × 9.5 ÷ 60
Conversations at 50% automation
The scenario does not guarantee 237.5 saved hours. Savings depend on resolution, escalation, monitoring, and remaining human work.
May reflect complex questions, repeated clarification, missing context, or a high-touch service model.
May point to slow information retrieval, fragmented systems, approvals, or poor routing.
May reveal repetitive notes, manual CRM updates, or duplicate data entry.
Teams with the same AHT may need different improvements. The component breakdown makes the total actionable.
Agent effort during and immediately after an interaction.
How long a customer waits for the first reply.
The wait before an agent starts handling the request.
Elapsed time until the issue is resolved, sometimes across multiple contacts.
Satisfaction customers report after the experience.
Queue time is normally excluded from AHT. Lower AHT does not guarantee faster responses or better resolution. Read TechTarget’s AHT definition.
No. AHT is a diagnostic metric, not a target to minimize at any cost. Pressure to end conversations quickly can create incomplete answers, weak documentation, or repeat contacts.
There is no universal good AHT. The right range depends on channel, intent, complexity, and service model. Review it with first-contact resolution, repeat contacts, escalations, and CSAT.
Use conversation volume and time data from the same reporting window.
Keep every time input in the same unit.
Calculate channels separately when workflows differ.
Separate simple and complex conversation types.
Use conversation volume when combining teams.
Review comparable periods before and after a change.
Recalculate after major changes to the product, team, or support process. Do not combine team-level AHT figures without weighting by conversation volume.
Once you know where time goes, improve knowledge access, streamline wrap-up work, or automate repetitive conversations.
Dealism automation can connect customer triggers, replies, and follow-up actions. An AI Customer Agent can understand intent, answer common questions, collect information, and pass relevant context to a person when judgment is needed.
Average handle time: the average handling time required for one customer interaction.
Phone-based AHT normally includes it. Messaging may define AHT differently, so use one consistent method.
Normally, no. Queue time occurs before active handling begins.
Yes. Immediate notes, CRM updates, tagging, and similar wrap-up tasks are included.
No. Staffing also requires working hours, occupancy, shrinkage, arrival patterns, and service-level targets.
No. It shows conversations represented by the percentage. Actual savings depend on resolution, escalation, and follow-up.
Yes. Define active handling, hold, and wrap-up consistently and exclude customer response delays.
Dealism replies the second they message, sounds completely human, and quietly closes deals in the background.
Start Now
