What is after-call work (ACW)?

After-call work (ACW), also called wrap-up time or post-call processing, is the time an agent spends on administrative tasks immediately after a customer interaction ends and before they're available for the next one. It covers logging what happened, updating records, and any follow-up the conversation requires.

ACW is unglamorous, which is probably why it gets less attention than talk time or hold time. But it's the component of average handle time that's most within an agent's control and most sensitive to how well their tools work. A well-designed workspace can cut it in half. A bad one can make it longer than the call itself.

This page covers what counts as ACW, how to calculate it, why the published industry benchmarks don't agree with each other, how it fits into AHT, and what shortens it.

ACW in one sentence

ACW is the paperwork after the conversation, measured in the time it takes an agent to finish it.

What counts as after-call work

Most contact center platforms put an agent into an "after-call" or "wrap-up" status automatically when a call ends, and keep them there until they manually mark themselves available again. What happens during that status typically includes:

Disposition coding. Tagging the contact with a reason code so it can be reported on later.

Notes. A summary of what the customer needed and what was done about it, left for the next person who touches the account.

Record updates. Anything that changed (an address, a refund, an order status) gets written back to the system of record.

Follow-up scheduling. Callbacks, escalations, or a task for another team.

Compliance documentation. In regulated industries, this can be the largest share of ACW: verifying a disclosure was read or a consent was captured.

How to calculate after-call work

Average ACW = total time spent in after-call status ÷ total calls handled

A worked example. Across a shift, an agent spends 45 minutes total in after-call status over 90 calls handled.

Average ACW = 45 minutes ÷ 90 calls = 30 seconds per call

That's a per-agent or per-team average, the same way AHT is. It hides the spread between a quick disposition code and a long compliance write-up, which matters more for ACW than it does for talk time, because the tasks inside ACW vary so much by contact type.

Why the published benchmarks don't agree with each other

Search for an ACW benchmark and the numbers you'll find span two orders of magnitude with no explanation for the gap. Some vendor blogs cite 30–90 seconds as a healthy range. Others cite 20–40 minutes, which would mean an agent spends more time writing up a call than having it, for nearly every contact type that exists. Neither figure comes with a named study, a sample size, or a methodology attached, which is the same problem this site has flagged with other unsourced "industry average" claims.

The honest answer is that there isn't a credible, independently verified ACW benchmark the way there is for average speed of answer. ACW depends too much on what a disposition requires. A returns-only line and a benefits-eligibility line aren't comparable, and no single cross-industry number can capture both.

What's more useful than an external number is your own trend, segmented by contact reason. If ACW for the same disposition code is climbing month over month with no change in policy or complexity, that's the signal worth acting on, regardless of what any benchmark says is "normal."

ACW and average handle time

ACW is one of three components of average handle time (AHT):

AHT = talk time + hold time + after-call work

Because it's additive, every second trimmed from ACW is a second trimmed from AHT directly, with none of the tradeoffs that come from rushing the conversation itself. That's what makes it the component worth the most attention. Cutting talk time risks cutting corners with the customer. Cutting ACW is almost entirely about tooling and process.

Why after-call work matters

It's a proxy for how well the tools fit the job. Long ACW is rarely a discipline problem. It's usually a sign that the agent is re-entering information the system already had, switching between screens to find it, or writing free-text notes because there's no faster way to capture the outcome.

It determines real agent capacity. An agent isn't available for the next contact until ACW ends. A team that shaves 30 seconds off average ACW across a few hundred daily contacts recovers meaningful capacity without hiring.

It's where the record of the interaction gets created. Rushed ACW produces bad notes, and bad notes are what the next agent (or the same customer on their next contact) pays for.

Where ACW gets gamed

Because ACW is measured and talk time is watched even more closely, it's a status some agents learn to sit in a little longer than the task requires. It's a quiet way to control pace without it showing up as idle time. Making the underlying task fast enough removes the incentive to stretch it. Review ACW next to occupancy and queue conditions, since a standalone ACW number invites exactly this kind of gaming.

How to reduce after-call work

Pull up the record automatically. If the agent's screen already shows the customer's history and the relevant order or account, they're not searching for context while the clock runs.

Replace free text with structured capture. A disposition picklist and a couple of templated fields are faster and more consistent than an open note box, and they produce cleaner data for reporting.

Let the record update itself where it can. A refund processed or an address changed during the call shouldn't need to be typed again afterward if the system that made the change can log it directly.

Use AI-generated call summaries as a draft the agent reviews and corrects. That's faster than writing from scratch, as long as a person is still checking it. An unreviewed AI summary that's wrong is worse than no summary at all.

After-call work when AI handles the conversation

When a contact is fully resolved by automation with no agent involved, there's no ACW to measure for that contact. The system already has a structured record of what happened, because it generated the conversation. ACW as a metric only applies to the contacts a person still touches, which means as automation takes on more of the simple, well-defined work, the contacts left in the ACW average skew toward the more complex ones that were escalated to begin with.

That's worth watching for the same reason average handle time is worth watching in an automation rollout: a rising average ACW isn't necessarily a regression. It can just mean the mix of what's left for agents has gotten harder, because the easy contacts stopped needing an agent at all.