After-Call Work (ACW)

What is After-Call Work (ACW)?

After-Call Work (ACW) is the time an agent spends on tasks related to a call immediately after it ends, before they’re available to take the next one, such as updating a CRM record, writing call notes, or triggering a follow-up action. It’s also known as post-call processing or wrap-up, and it’s tracked as its own distinct metric because it directly affects how many calls an agent can realistically handle in a shift. A support agent who finishes a call but still needs two minutes to update the ticket and log a disposition code is, for those two minutes, unavailable for the next customer even though the conversation itself has ended.

How ACW fits into Average Handle Time

ACW is one of the three components of Average Handle Time (AHT), alongside talk time and hold time: AHT = (Talk Time + Hold Time + Wrap-up Time) ÷ Number of Calls Handled. Because AHT is such a closely watched staffing metric, a rise in ACW shows up immediately as a rise in AHT, even if talk time itself hasn’t changed. This is why workforce planners rarely look at ACW in isolation; it’s usually reviewed alongside talk time to understand which part of the call is actually driving a change in overall handle time.

What typically falls under ACW

• Updating customer records with details or outcomes from the call just completed.
• Writing call disposition notes summarizing what happened and what, if anything, needs follow-up.
• Triggering next steps, such as creating a support ticket or scheduling a callback.
• Completing compliance documentation required for certain regulated interactions.

Why ACW is worth measuring on its own

A contact center focused purely on talk time can miss where its actual capacity is being lost. Two agents can have identical talk times but very different total capacity if one spends 90 seconds on ACW per call and the other spends 30, that 60-second gap, multiplied across dozens of calls a day, adds up to a meaningfully different number of calls each agent can actually handle. Over a full shift and a full team, that gap can be the difference between hitting a service level target and missing it, even though nothing about the actual conversations changed.

Reducing ACW without cutting corners

The goal isn’t simply pressuring agents to rush through post-call tasks, which tends to produce sloppy notes and downstream problems. More sustainable approaches include CTI integrations that auto-populate CRM fields from call data, structured disposition codes that are faster to select than free-text notes, and AI-assisted call summarization that drafts notes for the agent to review rather than write from scratch. Standardizing on a short, well-maintained set of wrap-up codes also helps: a list that’s too long slows agents down during selection, while one that’s too short pushes more detail into manual notes. Some contact centers also allow a short, capped amount of ACW time to complete automatically after a call, so an agent isn’t marked available before they’ve genuinely finished the wrap-up.

Benefits of managing ACW well

• More accurate capacity planning: workforce management forecasts that account for real ACW, not just talk time, staff more accurately.
• Higher agent throughput: reducing unnecessary ACW time directly increases how many calls an agent can handle per shift.
• Better documentation quality: tools that assist rather than rush ACW tend to produce more useful, complete records.

FAQs

What’s a reasonable amount of ACW time per call?
It varies by industry and call complexity, but many contact centers target somewhere between 30 seconds and two minutes, with more compliance-heavy or technical calls naturally running longer.

Is ACW the same thing as hold time?
No. Hold time happens during the call, while the customer is still connected; ACW happens after the call has ended and the customer has disconnected.

Can ACW be eliminated entirely?
Not realistically, since some post-call documentation is usually necessary for continuity and compliance. The realistic goal is minimizing unnecessary ACW rather than removing it altogether.