Glossary · ACW

What is ACW?

ACW (After-Call Work) is the time a contact center agent spends on post-call administrative tasks after a customer interaction ends, writing notes, updating the CRM, setting follow-up tasks, finalizing dispositions, escalating issues. ACW is a component of Average Handle Time (AHT) and is one of the highest-leverage metrics for contact center productivity. AI-powered automation can reduce ACW by 40–60 percent by auto-generating call summaries, syncing to CRM, and drafting follow-ups.

ACW components

Typical ACW tasks:

Writing a call summary note
Updating the CRM contact or account record
Creating a ticket or case
Logging the call disposition (resolved, escalated, callback requested)
Sending a follow-up email or SMS
Processing any commitments made on the call
Updating personal task lists
Handing off to another team if escalated

In a traditional contact center, ACW runs 45 to 90 seconds per call on simple transactions, 3 to 5 minutes on complex ones.

Why ACW matters

ACW is the hidden cost of every customer call. It’s the time agents spend not talking to customers. In a contact center with 100 agents handling 500 calls each per day:

50,000 calls per day × 90 seconds ACW = 1,250 agent-hours of ACW per day
At $25/hour fully-loaded agent cost = $31,250 per day on ACW alone
$11.4M per year in just post-call administrative work

Even modest ACW reductions drive major savings.

How to calculate after-call work

ACW is measured per interaction and averaged across the period you are analyzing:

Average ACW = Total after-call work time / Number of calls handled

If 1,000 calls in a day generated 25,000 seconds of wrap-up time, average ACW is 25 seconds. Two related figures matter as much as the raw average:

ACW as a share of AHT — Average ACW / Average Handle Time. Healthy contact centers land at 15–25%. Above 30% points to a tooling or process problem, not lazy agents.
ACW distribution, not just the mean — a 25-second average can hide a cluster of agents at 70 seconds. Always look at the spread by agent and by call type before drawing conclusions.

Measure ACW as its own state in the agent software, separate from talk time and idle time, so the number is clean. If agents do wrap-up while marked “available,” ACW is undercounted and the next caller waits.

How AI reduces ACW

Modern AI-powered contact centers automate the bulk of ACW:

AI call summaries: generated the moment the call ends, with intent, outcome, action items
Auto-logged CRM activity: transcript, summary, and metadata post to the contact/account/ticket without manual entry
Auto-drafted follow-ups: SMS or email prepared with relevant context, agent reviews and sends
Auto-disposition: AI proposes disposition based on call content; agent confirms
Auto-created tickets: issues automatically escalated with full context
Smart wrap-up prompts: AI surfaces the right wrap-up fields based on the call topic

DialPhone’s AI Quality Management and AI Agent Assist together cut ACW by 50 percent on average.

Measuring ACW

Good contact center measurement includes:

Average ACW time per call
ACW as a percentage of AHT: typically 15–25% is healthy; over 30% signals process or tooling problems
ACW variance by agent: outliers often signal either training needs or workflow issues
ACW by call type: complex calls legitimately have higher ACW
ACW trends over time: catch regressions from process changes or tooling issues

Best supervisors review ACW monthly alongside Call Handle Time and First Call Resolution.

Reducing ACW: tactics beyond AI

Pre-fill what’s knowable: if a caller authenticates, pre-populate the record
Reduce disposition choices: 8 dispositions max, not 50
Embed ticketing inside the call flow: don’t make agents context-switch
Auto-end workflows on disposition: hitting “resolved” shouldn’t require navigating to 3 other tools
Templates for common follow-ups: pre-written SMS and emails for the 80% case
Integrated knowledge base: agents shouldn’t spend ACW looking up what they should have said
Remove ceremony: does the agent really need to update four fields? Or can three be inferred?

Process improvements alone can cut ACW by 20-30% before any AI tooling.

ACW and occupancy

Occupancy = (Call Time + ACW) / (Call Time + ACW + Available Time). High occupancy means agents are busy; low means they’re idle waiting.

Target occupancy is typically 85–90%. Above 90% agents burn out; below 80% is expensive idle time.

Reducing ACW raises effective capacity, the same agents can handle more calls, which either lowers headcount needs or improves service levels at the same headcount.

ACW and auxiliary codes

Many contact centers use “Aux codes” or “not-ready codes” for various non-call states:

ACW (after-call work)
Lunch
Break
Training
Coaching
Admin
Meeting

Tracking Aux code time by agent surfaces patterns, an agent with unusually high ACW is either struggling with the work or using ACW as a pseudo-break.

ACW by channel

ACW concepts extend beyond voice:

Voice: classic ACW (write notes, update CRM)
SMS: typically lower ACW; the message thread is the record
Email: variable, depending on how many follow-up actions
Chat: lower ACW; transcripts auto-save
Social: variable

Omnichannel platforms should measure and display ACW consistently across channels.

DialPhone ACW reduction features

AI Call Summary: post-call summary with intent, outcome, action items generated automatically
Auto CRM Logging: Salesforce, HubSpot, Zendesk records updated without manual effort
AI-Drafted SMS Follow-ups: templated drafts with context for common scenarios
Auto-Ticketing: escalations create tickets in the right system with full context
Integrated Knowledge Base: AI surfaces knowledge during the call, removing the search step
Unified Agent Desktop: one interface for all channels, no context-switching

Customers using DialPhone’s AI Contact Center report 50% ACW reduction at the tier with AI Agent Assist and AI Quality Management included (Professional plan and above).

Example

A 120-agent customer support operation averaged 90 seconds of ACW per call handling 500 calls per agent per day:

Before DialPhone: 90s × 500 × 120 = 1,500 agent-hours of ACW per day
After DialPhone Professional with AI Agent Assist + AI QM: ACW dropped to 42 seconds per call
New ACW: 42s × 500 × 120 = 700 agent-hours per day
Savings: 800 agent-hours per day × $25/hour fully loaded = $20,000 per day = $5.2M annualized

That ACW reduction alone justified the move to DialPhone Professional ($95/user × 120 users × 12 months = $136K annualized license cost).

After-call work in 2026: what AI changes

For most of the contact center’s history, ACW was simply accepted — every call cost a minute or two of paperwork, and the only lever was training agents to type faster. AI has changed the assumption itself: the target for ACW is now approaching zero.

Wrap-up happens during the call, not after. AI transcribes and structures the conversation in real time, so by the time the customer hangs up, the summary, disposition, and CRM fields are already drafted. The agent reviews and confirms in a few seconds instead of starting from a blank note.
The agent’s job shifts from writing to checking. ACW becomes a verification step. This is faster and also more accurate — AI-drafted summaries do not suffer the recall errors and shorthand that creep into notes written under time pressure.
Downstream data quality rises. Because the AI populates structured fields consistently, the CRM and analytics layer get cleaner data than manual wrap-up ever produced — which improves first-call-resolution tracking, root-cause analysis, and forecasting.
The metric to watch becomes accuracy, not just speed. When ACW is automated, the risk is agents rubber-stamping a wrong summary. The 2026 best practice is to spot-check AI wrap-up quality the same way you would coach call quality.

The strategic takeaway: in 2026, a contact center still running 60–90 second manual ACW is carrying a cost its AI-equipped competitors have largely eliminated. ACW reduction has moved from a nice-to-have efficiency project to a baseline expectation.

After-call work frequently asked questions

What does ACW stand for?

ACW stands for After-Call Work — the administrative tasks an agent completes immediately after a customer interaction ends and before taking the next one. It covers writing the call summary, updating the CRM, logging a disposition code, creating tickets, and sending follow-ups. ACW is sometimes called “wrap-up time” or “post-call processing.” It is a distinct, measurable agent state and one of the three components of Average Handle Time, alongside talk time and hold time.

What is a good after-call work time?

There is no single universal target because ACW depends on call complexity, but two rules of thumb apply. In absolute terms, simple transactional calls should wrap up in well under a minute; complex calls (claims, technical support) legitimately run several minutes.

The more useful benchmark is relative: ACW should be roughly 15–25% of total Average Handle Time. If wrap-up exceeds 30% of AHT, the problem is almost always tooling or process — too many disposition codes, disconnected systems, manual note-taking — not slow agents. With AI-automated wrap-up, well-run contact centers push ACW under 30 seconds.

How do you reduce after-call work?

The biggest single lever is AI automation: real-time transcription and AI-generated call summaries eliminate manual note-writing, and auto-logging posts the record to the CRM without data entry. Beyond AI, process changes help — cut the number of disposition codes, pre-fill known caller data, embed ticketing inside the call flow so agents do not context-switch, and template the common follow-up messages. Process improvements alone typically cut ACW 20–30%; adding AI wrap-up takes the reduction to 50% or more.

Is after-call work counted in average handle time?

Yes. Average Handle Time is calculated as (total talk time + total hold time + total after-call work) / number of calls. ACW is the third component. This is why reducing ACW directly lowers AHT and raises agent capacity without rushing customers on the actual conversation — it is the part of handle time you can shrink without hurting CSAT or call quality. That makes ACW one of the highest-leverage metrics a contact center can optimize.

Should agents go into ACW state or stay available?

Agents should be placed in a dedicated ACW (wrap-up) state while doing post-call work, not left marked “available.” Two reasons: first, accuracy — if wrap-up happens while available, the next call can interrupt it and the ACW time is never measured, so the metric is wrong. Second, customer experience — an agent still finishing paperwork should not be routed a new caller. The right setup is an explicit ACW state, ideally time-boxed, so supervisors can see real wrap-up time and coach the outliers.

AI contact center pricing 2026
Workforce management in the contact center
Average Handle Time (AHT) — the parent metric ACW feeds into
First Call Resolution (FCR) — the quality metric that prevents ACW rework
CCaaS — the platform where AI-driven ACW reduction is delivered
AI Contact Center pricing
AI Agent & Supervisor Assist