After-Call Work: How to Measure and Reduce It
What after-call work is, how to measure it fairly, why it grows, and practical ways to shorten wrap-up without losing the notes that matter.
When a call ends, the work does not. The agent has to record what happened, update the customer's record, send a message or create a task. This is after-call work, often called ACW or wrap-up, and in many teams it takes as long as a quarter of the whole interaction or more. It is also the part customers never see, which makes it easy to ignore.

This guide explains how to define and measure ACW, why it grows, and how to cut it responsibly. It is closely connected to Reducing Average Handle Time Without Hurting Quality and to what AI Call Summaries can take over.
What counts as after-call work
Handle time is usually described as talk time plus hold time plus after-call work. ACW starts when the caller disconnects and ends when the agent becomes available for the next call. Typical tasks include:
- Writing a short note or choosing an outcome for the call.
- Updating contact details or the status of a case.
- Creating a follow-up task, callback or appointment.
- Sending a confirmation email or message.
- Handing the case to another team with the right context.
Some systems give a fixed wrap-up window, after which the agent is offered the next call automatically. Others let the agent stay in a wrap-up state until they are ready. Both are legitimate; what matters is that the time is recorded and that agents do not feel pushed to skip useful notes.
Measuring ACW fairly
The simplest measure is the average ACW per call. It becomes useful once you split it.
| Split by | What it shows |
|---|---|
| Call type | Quote requests, complaints and simple questions need different amounts of admin. Compare like with like. |
| Agent | A wide gap between agents on the same call type suggests different habits, not different speed. |
| Time of day | Wrap-up often shrinks in peak hours as agents rush. Check whether quality drops. |
| Outcome | Calls that create a task or a handover take longer than those that close. |
Look at the distribution as well as the average. A handful of very long wrap-ups can come from system problems, interruptions or an agent taking a break in wrap-up status. Review them separately before deciding anything about the whole team.
Why after-call work grows
When ACW keeps rising, there is usually a reason in the process rather than in the people.
Typical causes
- Too many fieldsEvery extra required field adds seconds, and most were added for reasons nobody remembers.
- Free-text notes with no purposeAgents write long notes because nobody told them what the notes are for.
- Several systemsThe agent copies the same details into the phone system, the CRM and a spreadsheet.
- Unclear outcomesA long list of outcome codes means thinking time on every call.
- Missing templatesCommon follow-up messages are typed from scratch.
- InterruptionsThe next call, chat or message arrives mid-wrap-up.
A hypothetical example shows how the numbers help. A five-person support team notices that wrap-up after billing calls is much longer than after opening-hours questions. Shadowing shows that billing agents retype the invoice number into three places and write a paragraph nobody reads. The team keeps one field for the invoice number, replaces the paragraph with a three-line template, and moves the confirmation email to a canned message. Wrap-up on that call type drops, and the weekly note review shows the records are still usable.
Notice what the team did not do: it did not announce a target and wait. It looked at the work, removed steps, and then measured.
Ways to reduce it
Start by looking at what is actually done in wrap-up and asking who reads it. Anything that nobody uses is a candidate for removal.
A simple wrap-up review
- List the tasksShadow two or three agents for a morning and write down every step after the call.
- Ask who uses each oneFollow each note or field to the person or report that depends on it.
- Remove or mergeDelete unused fields, merge duplicate systems or make fields optional.
- Add shortcutsCreate note templates, canned messages and a short outcome list.
- Re-measureCheck ACW and the quality of notes for a few weeks before changing anything else.
Some changes are quick wins:
- Shorter outcome lists. Six clear outcomes beat twenty-five fine ones.
- Note templates for the most common call types, with prompts such as what was asked, what was agreed and what happens next.
- Standard follow-up messages that the agent only has to tweak.
- Pre-filled records from the caller's history so agents confirm instead of retype.
- Automatic summaries drafted from the call, edited by the agent instead of written from scratch.
Keeping quality while cutting time
A shorter wrap-up is only an improvement if the next person can still use the record. Check that by sampling. Pick ten recent notes, imagine you are a colleague taking over the case, and see whether you can tell what happened and what is next. If you cannot, the notes are too short, not just brief.
Balanced and unbalanced wrap-up
| Rushed | Balanced | |
|---|---|---|
| Notes | "Called, issue fixed" | One or two lines naming the issue, the fix and the next step |
| Follow-up | Forgotten or promised vaguely | Created as a task with an owner and a date |
| Outcome code | The first option, to move on | Chosen from a short list that matches reality |
| Agent state | Pressure to be ready for the next call | A short, protected window with room for exceptions |
Pair ACW with quality checks from QA Sampling so a falling time is matched by stable notes. A drop in ACW with a rise in repeat contacts is a warning; see Repeat Call Rate.
One more habit helps: protect the end of the day. Agents who finish their last call close to shutdown often leave notes half done. Give a short window at the end of each shift to complete records, so tomorrow's team does not inherit unexplained cases.
After-call work in Call
In Call's dialler, a call that ends shows an After-call work panel with a countdown when a wrap-up time is set in Preferences. The agent chooses an outcome (Interested, Callback, Sale, Not interested, Voicemail or Wrong number), sets a callback time if needed, types notes or inserts one of their own note templates, and presses Log outcome. Calls handled by an AI agent record their own result, so the form is for calls you placed or answered.
In the call history, a finished call has a summary and transcript, and the Write it up section can draft a note, a follow-up email or a suggested outcome that the agent copies and edits. Using a drafted note as a starting point is a quick way to shorten typing while keeping the agent in control of what is recorded. For the broader picture, see Call Summaries in Call.
Frequently asked questions
Is after-call work part of handle time?
Yes. Average handle time is generally talk time plus hold time plus after-call work. Measuring ACW separately shows which part of handle time to attack first.
Should we set a fixed wrap-up time?
A short fixed window can help the flow, but allow agents to extend it when a call needs real follow-up. Rigid limits tend to push agents to skip useful notes.
How do summaries help?
A drafted summary gives the agent something to review instead of a blank box. They still need to check it is correct and add anything the draft missed.
What if agents stay in wrap-up to avoid calls?
Look at the distribution and the reasons before assuming. Long wrap-ups can come from complex work, system trouble or fatigue, and a conversation with the agent is usually more useful than a rule.
Which notes are worth writing?
Those that someone will read: the next agent, a manager reviewing a complaint, or a report. If nobody uses a note, consider dropping it.
How often should I review the wrap-up process?
A light review every quarter is enough for most teams, or sooner after adding a new system, product or call type.