What is after-call work (ACW)?
After-call work (ACW) is the time an agent spends finishing a contact after the customer has gone: writing the disposition note, updating the ticket, sending a follow-up email, filing a refund request, or logging the call outcome in a CRM. Most contact centers place the agent in a dedicated wrap-up state for the duration.
Wrap-up is paid, occupied time that carries no live conversation, which is why it sits inside the handle-time calculation in most staffing models. A common target is 30 to 60 seconds per call, though regulated lines like insurance and healthcare routinely run several minutes.
How after-call work is calculated
Average after-call work is one division: total wrap-up seconds divided by the number of contacts handled in the same period. An agent who takes 52 calls in a shift and spends 41 minutes in wrap-up has logged 2,460 seconds, which divided by 52 calls gives 47 seconds of ACW per call.
The number reaches the report through four layers. The telephony platform in a call center marks the agent unavailable the moment the caller disconnects and opens a wrap-up timer. The agent desktop captures the work itself: notes, disposition codes, ticket edits, follow-up tasks. Classification happens by hand or through auto-tagging, and the field the agent picks decides what the analytics layer can later group by. Reporting then folds the wrap-up seconds into average handling time, so ACW is both a standalone metric and a component of the headline one.
Remove wrap-up seconds and handling time falls by the same amount, which is why wrap-up is usually the first place a capacity plan looks.
What counts as after-call work and what does not
The boundary matters because everything on the wrong side of it distorts both the wrap-up average and the staffing forecast built on top of it.
Notes and disposition coding: Writing the account note and selecting the reason code that classifies the contact for reporting, usually the largest single chunk of the interval.
System updates: Editing the ticket, correcting an address, updating a subscription state, or reconciling what was agreed on the call with what the CRM holds.
Follow-up actions: Filing a refund, escalating to a specialist queue, scheduling a callback, or triggering the confirmation email the customer was promised.
Immediate internal handoffs: A short message to a supervisor or a specialist raised while the details are still fresh, capped on most floors at a minute.
Excluded time: Breaks, coaching sessions, training, idle time between contacts, and offline ticket work batched for later all belong to separate agent states.
After-call work vs average handling time vs talk time vs hold time
Handle-time metrics overlap by design, and operators regularly quote one when they mean another. Average handling time measures the whole contact from answer to release of the agent, wrap-up included. Talk time measures only the live conversation between agent and customer. Hold time measures the periods inside that conversation when the customer waits in silence. After-call work measures what the agent does once the line is already dead, which makes it the only component of handle time the customer never experiences directly.
What it counts | What it misses | Typical benchmark | |
|---|---|---|---|
After-call work | Post-contact notes, updates, follow-ups | Work deferred to a later batch | 30 to 60 seconds per call |
Average handling time | Talk, hold, and wrap-up combined | Queue wait before the answer | Varies widely by contact type |
Talk time | Live conversation only | Silent and post-call effort | No standalone cross-industry target |
Hold time | Customer silence mid-conversation | Wrap-up and offline work | Kept as low as routing allows |
If you are forecasting staffing, handling time is the number you need. If you are hunting for recoverable minutes inside that forecast, ACW is where the savings hide, because it is the one component you can automate without shortening the conversation.
Why after-call work matters for customer experience
Every second an agent spends in wrap-up is a second that agent is unavailable to the queue. On a busy afternoon that surfaces as longer waits and a rising call abandon rate, a customer experience failure caused entirely by work the customer never saw.
The second failure mode runs the other way. When wrap-up is squeezed hard, notes get thin, dispositions get miscoded, and the next agent to touch the account starts cold, so the customer explains the problem twice.
The tradeoff is direct: every second removed from wrap-up either comes out of duplicated effort, which is free, or out of the record itself, which is borrowed against the next contact. Teams that watch only the queue-side cost tend to meet the record-side cost a quarter later, in repeat contacts.
How is after-call work measured?
After-call work is read straight from the telephony platform's state log. The wrap-up timer opens when the caller disconnects and closes when the agent returns to an available state, so the figure is a byproduct of routing that nobody types in by hand. Averages get reported per agent, per queue, and per contact reason, and the contact-reason cut is the one that shows where wrap-up is structural.
Converting seconds into money is what makes the metric argue for itself. The U.S. Bureau of Labor Statistics puts median pay for customer service representatives at USD 20.59 an hour (USD 42,830 a year, 2024 data), so wrap-up running 15 to 45 seconds across a 60-call day costs roughly USD 5 to USD 15 of paid time per agent, or USD 500 to USD 1,500 daily across a 100-seat floor.
The state log has one blind spot: work an agent defers to the end of the shift gets recorded under a different state, so a falling wrap-up average sometimes signals a growing offline backlog.
How AI agents change after-call work
The mechanism is straightforward. A model reads the transcript while the conversation is still running, produces a structured account of the issue, the actions taken, and the promised next step, then writes it into the ticket with disposition fields pre-filled. Conversation summarization can turn a two-minute writing task into a short read-and-confirm.
Two consequences follow. Wrap-up becomes a verification step, which changes what supervisors coach for, since the skill on display is judgement about a draft. The second consequence is structural: when a voice agent handles the contact end to end, it emits its own summary, tags, and CRM update at the moment the call closes, so the wrap-up interval for that contact disappears. Teams running post-call summaries from live assist usually see the average move before any individual agent notices working differently.
How to reduce after-call work
Reducing wrap-up starts with removing work, since a target on its own just relocates the work somewhere unmeasured. Four levers do most of it. Automate the summary and the disposition so the agent confirms a draft. Shrink the disposition taxonomy, because a forty-value dropdown costs real seconds on every call. Push follow-up actions such as refund submissions and callback scheduling into workflows triggered by the disposition code. Then fix the desktop, since much of what gets logged as wrap-up is an agent copying values between systems that do not talk. The ways AI support agents cut response time apply directly here.
Governance sets the outer boundary. Transcripts fed to a summarization model carry account data and sometimes health data, so a HIPAA business associate agreement is table stakes on clinical lines, and GDPR retention limits decide how long a raw transcript may sit beside the summary it produced. The constraint teams underestimate is CRM write latency: an agent waiting seven seconds for a ticket to save is accruing wrap-up that no drafting model can remove.
After-call work and downstream support metrics
Wrap-up sits upstream of the numbers operators actually report to the business. Average resolution time counts the whole life of an issue from creation to closure, and wrap-up feeds it twice: once as the seconds themselves, and again through the quality of the notes that decide whether the next agent closes the case or reopens it. Contact rate works in the other direction, because thin post-call records produce repeat contacts, which raise the share of customers needing help at all and push more calls into the queue that wrap-up was already delaying.
What does after-call work mean in plain terms?
ACW stands for after-call work, and most floors simply call it wrap-up time. Think of it as the paperwork a paramedic finishes once the ambulance doors close: the patient has gone, the job continues, and the next crew depends on what got written down.
Take it away entirely and the effect is immediate. The refund the agent promised never gets filed, the account note stays blank, and when the customer calls back on Thursday the second agent has nothing to read, so the whole conversation happens again from the beginning.
The tradeoff is that this work is genuinely valuable and genuinely unproductive at the same time. Every minute of it is paid time in which no customer is being helped, which is why the goal is to make wrap-up shorter and never to make it optional.
Common after-call work mistakes
Four patterns account for most of the damage.
Setting a target without removing the work is the first. Agents hit the number by deferring notes to the end of the shift, where the time is recorded under another state, so the average improves while an unwritten backlog grows behind it.
Measuring wrap-up per agent and stopping there is the second. Coaching an individual makes sense when the variance is behavioural; when most of the wrap-up on a queue traces to one slow system or one badly designed form, the coaching conversation is aimed at the wrong person.
Trusting an unreviewed automated summary is the third. A generated note that is confidently wrong enters the customer record and gets read as fact by every agent after it, which does more harm than an empty field.
Optimizing wrap-up in isolation is the fourth. Cutting seconds while repeat contacts climb moves cost from a line you watch onto a line you ignore, and the total goes up.
What is a good after-call work time?
After-call work targets commonly land between 30 and 60 seconds per contact for straightforward retail or subscription support. Regulated and complex lines, insurance claims and clinical intake among them, routinely run several minutes because the documentation itself is the deliverable. The useful comparison is against your own contact reasons, since a blended average hides the reasons that dominate the total.
What is the difference between after-call work and hold time?
After-call work happens once the customer has disconnected and the agent is finishing notes, ticket updates, and follow-ups. Hold time happens during the live call, while the customer waits in silence and the agent checks something. Both count inside average handling time, and only hold time is experienced by the caller.
After-call work vs wrap-up time: are they the same thing?
After-call work and wrap-up time refer to the same interval and get used interchangeably on most contact center floors. Telephony platforms usually label the agent state wrap-up or ACW, while reporting tools tend to print after-call work. Some teams reserve wrap-up for the system state and after-call work for the tasks performed inside it.
Does after-call work count toward agent occupancy?
After-call work counts as occupied time in standard occupancy calculations, because the agent stays unavailable for a new contact throughout it. That makes wrap-up a strange lever: cutting it lowers handling time and cost per contact, while occupancy also falls, since the same agent now spends more of the hour waiting between calls.
How does AI reduce after-call work?
AI reduces after-call work by generating the summary, the disposition tags, and the ticket update from the transcript while the call is still in progress, leaving the agent a short review. Autonomous voice agents go further and file their own records the moment the contact ends, removing the wrap-up interval for those contacts entirely.
What does ACW stand for in a call center?
ACW stands for after-call work, the paid interval an agent spends completing post-contact tasks before returning to an available state. The full form appears in workforce management reports, telephony state logs, and quality scorecards. Related shorthand includes AHT for average handling time, which contains ACW as one of its three components.