.png)
Last updated: August 14, 2026
Every support conversation has a shadow. The call ends, the customer hangs up satisfied, and then the agent spends another minute — sometimes four — typing a summary, picking a disposition code, updating the CRM, and firing off a follow-up email. That shadow is after-call work, and in most contact centers nobody owns it.
It is an odd blind spot, because after-call work is one of the few support costs you can shrink without touching quality. Cutting talk time usually means rushing customers. Cutting wrap-up time means removing typing. Those are very different trade-offs, and the second one is almost always the better deal.
On this page
- What after-call work actually includes
- Why ACW is the most expensive metric nobody manages
- Five ways to cut ACW without losing case data
- What to measure once you automate
- A realistic 30-day rollout
- Frequently asked questions
What after-call work actually includes
After-call work (ACW), also called wrap-up time, is everything an agent does to close out an interaction once the customer is gone. Verint defines it as the administrative tasks that follow a contact and that keep the agent unavailable for the next one — which is the part that matters operationally. An agent in wrap-up is occupied but not serving anyone.
The label hides a lot of different work. It helps to separate it into four buckets, because each one responds to a different fix.
The four buckets of wrap-up
- Narrative. Writing the free-text summary of what the customer wanted and what was done. Slow, inconsistent, and the bucket most often skipped when queues get long.
- Classification. Choosing disposition codes, reason categories, product tags, sentiment flags. Fast per field, but centers routinely stack eight or ten of them.
- Systems of record. Updating the CRM, the order system, the billing platform, the warranty log. This is where swivel-chair work lives.
- Follow-through. Sending the confirmation email, opening the internal task, scheduling the callback, notifying the account owner.
Most ACW reduction programs attack the narrative bucket and stop there. The systems-of-record bucket is usually the bigger prize, because it scales with how fragmented your tooling is rather than with how chatty the agent is.
Why ACW is the most expensive metric nobody manages
Start with the size of it. Commonly cited industry benchmarks put average ACW in the range of 30 to 90 seconds per contact, with e-commerce at the low end and complex, document-heavy sectors well above it. Aggregated across a shift, ACW can absorb up to 12% of agent time — and unlike talk time, none of it is spent with a customer.
Zoom out further and the picture gets worse. Salesforce research covering thousands of service professionals found that agents spend only 39% of their time actually servicing customers, with internal meetings, admin, and manual case logging eating the rest. Wrap-up is not an edge case in that number. It is a headline contributor.
The financial translation is simple, and it is worth doing on your own volumes rather than trusting a vendor slide:
| Input | Example figure | Why it matters |
|---|---|---|
| Contacts per month | 40,000 | Every second of ACW is multiplied by this number |
| Average ACW | 75 seconds | Measure it separately from talk time or it disappears |
| Monthly wrap-up hours | ~833 hours | Roughly five full-time agents doing paperwork |
| Target ACW | 30 seconds | Frees ~500 hours a month for live contacts |
Those recovered hours are the reason ACW belongs in your support capacity planning model. Wrap-up reduction is effectively free headcount, and it lands without a hiring cycle.
There is a second, quieter cost. When ACW is squeezed by pressure rather than by design — a spike hits, supervisors push occupancy, agents shorten their notes — you do not lose minutes, you lose data. Thin case notes degrade routing, break your knowledge base, and make root-cause analysis guesswork. That is why the goal is never simply lower ACW. It is lower ACW with equal or better case data.
Five ways to cut ACW without losing case data
1. Generate the summary from the conversation, not from memory
An agent writing a summary is transcribing something that already exists. The transcript, the chat log, or the email thread is a complete record; the summary is a compression of it. Compression is exactly what language models are good at, and it is the single highest-leverage swap available: the agent moves from author to editor. Reviewing and correcting a draft summary takes a fraction of the time of writing one, and the output is more consistent across a team of fifty than any style guide will ever make it.
The design detail that decides whether this works is the review step. Auto-summaries that post without a glance drift from reality; auto-summaries the agent must confirm stay accurate. Keep the human in the loop, but give them one click instead of one paragraph.
2. Replace free-text fields with structured, pre-filled ones
Audit your disposition form and ask a blunt question about every field: when was the last time anyone queried it? Most centers accumulate tags nobody has reported on in two years. Delete those. For the fields that survive, pre-fill them from the conversation — intent, product, sentiment, resolution type are all inferable — and let the agent correct rather than choose.
Tracking cost per resolution alongside this cleanup keeps you honest. If you remove fields and cost per resolution drops while quality scores hold, the fields were overhead.
3. Kill the swivel-chair with real integrations
Copy-pasting an order number from the helpdesk into the ERP is not knowledge work; it is data transport. Every one of those hops is 10 to 20 seconds and a chance to fumble a digit. Write-back integrations between your support platform and your systems of record remove the whole bucket rather than speeding it up, which is why they tend to deliver the largest single reduction in wrap-up time.
This is also the bucket where AI agents earn their keep in practice. Tools such as Darwin AI's customer experience worker Eva handle the conversation, the classification, and the CRM and order-system updates in one pass, so routine contacts close with no wrap-up at all and human agents inherit only the cases that genuinely need judgment.
4. Move wrap-up into the interaction, not after it
Wrap-up performed while the customer is still on the line costs nothing extra in agent time and often improves accuracy, because details are fresh and the customer can confirm them. Coach agents to summarize aloud — "so I've credited the shipping charge and reissued the order, you'll see an email in a few minutes" — while the notes are being written or reviewed. It doubles as a resolution confirmation, which is one of the cheapest ways to nudge first contact resolution upward.
5. Watch ACW and AHT together, never alone
A wrap-up target set in isolation is an invitation to hide time elsewhere. Agents under ACW pressure extend talk time, use more holds, or defer notes to a later batch that never happens. Report ACW as a component of average handle time and review the two side by side, so a drop in one that is offset by a rise in the other is visible immediately.
Key takeaway: ACW reduction fails when it is framed as a speed target and succeeds when it is framed as a removal target. Do not ask agents to type faster. Remove the typing — through generated summaries, pre-filled fields, and write-back integrations — and hold case-note quality as a hard constraint.
What to measure once you automate
Automating wrap-up creates a new risk: notes that are fast, uniform, and quietly wrong. Pair every efficiency metric with a quality metric and review them in the same meeting.
| Efficiency signal | Paired quality signal |
|---|---|
| Average ACW per channel | Summary accuracy on a sampled audit |
| ACW as a share of AHT | Repeat-contact rate within 7 days |
| Percentage of contacts closed with zero manual wrap-up | Disposition-code agreement between agent and reviewer |
| Agent hours returned to live queues | CSAT and escalation rate, held flat or better |
Summary accuracy is the one most teams skip, and it is the one that protects everything downstream. If you already run automated contact center quality assurance, extend the same scoring to the case note itself rather than only the conversation. A note that omits the resolution is a defect, however quickly it was produced.
A realistic 30-day rollout
You do not need a platform migration to start. A month is enough to prove the case on one queue.
- Days 1–5. Instrument ACW separately by channel and queue. If your reporting only exposes AHT, fix that first — you cannot manage a number you cannot see.
- Days 6–10. Audit the disposition form. Cut every field with no consumer. Baseline note quality on 50 sampled contacts so you have a before picture.
- Days 11–20. Turn on generated summaries and pre-filled classification for a single high-volume, low-complexity queue. Keep agent confirmation mandatory.
- Days 21–30. Add write-back to whichever system of record agents touch most. Compare ACW, repeat contacts, and note quality against the baseline, then decide what to expand.
Expect the gains to be uneven. Simple, high-volume queues collapse to near-zero wrap-up; complex B2B cases with genuine investigative notes will improve modestly and should. Salesforce found that service teams using AI spend around 20% less time on routine cases, freeing roughly four hours a week — a useful reference point for the routine end of your mix, and a reminder that the savings concentrate where the work is repetitive.
Close routine conversations with zero wrap-up — summaries written, fields filled, and systems updated before the agent would have started typing.
See how Eva handles wrap-upFrequently asked questions
What is a good after-call work time?
It depends heavily on channel and case complexity, but published benchmarks generally place average ACW between 30 and 90 seconds. Rather than chasing an external number, set your target relative to your own baseline and require note quality to hold as ACW falls.
Is after-call work included in average handle time?
Yes. AHT is normally calculated as talk or handle time plus hold time plus after-call work, which is precisely why ACW hides so easily — it is folded into a bigger number. Report it as its own line item.
How much agent time does after-call work consume?
Estimates vary by center, but ACW can take up to 12% of agent time. The broader admin burden is larger still: Salesforce found agents spend only 39% of their time servicing customers.
Can AI write case notes without a human reviewing them?
Technically yes, and for very simple, templated interactions it is reasonable. For anything involving a commitment, a credit, or a compliance-relevant statement, keep a confirmation step. The review is fast and it is what keeps your case history trustworthy.
Will cutting ACW hurt CSAT?
Not if you cut it by removing work rather than rushing it. Problems appear when agents are pressured to shorten notes while doing the same tasks manually; then repeat contacts rise because the next agent inherits an incomplete record. Track repeat-contact rate alongside ACW to catch that early.
