When a call ends, the agent’s work often does not. They update the customer record, pick an outcome, fill in a form or schedule a callback. This is after call work (ACW), also called wrap up time. Done well, it keeps your records accurate. Left unmanaged, it quietly takes agents out of the queue while customers wait. This guide explains what after call work includes, how to measure it, and how to keep wrap time useful but short.
What is after call work?
After call work is everything an agent does after hanging up and before taking the next call. Typical tasks:
- Choosing a disposition, the outcome code for the call.
- Adding notes or a remark to the customer record.
- Filling in a lead form or ticket.
- Scheduling a callback or sending a follow-up message.
- Passing the case to another team.
During ACW the agent is logged in but not available for calls, so the system does not offer them the next caller.
How to measure ACW
Average ACW = total after call work time / number of calls handled
Example: an agent handles 50 calls in a shift and spends 100 minutes in wrap-up. Average ACW is 2 minutes per call.
ACW is one of the three parts of average handle time, along with talk time and hold time. It also affects occupancy: time in wrap-up counts as work, but the agent cannot take calls during it.
There is no universal right figure. A two-minute call that needs a detailed medical or loan record will need more wrap-up than a quick order status query. Measure your own baseline per queue, then look for agents and call types that sit well above it.
After call work in Voxdial Contact Center
Voxdial calls the wrap-up state Closure.
- Closure state: after each call the agent moves into closure to finish their notes, then sets themselves back to available from the agent console.
- Auto closure: set per agent. With auto closure on, the console ends wrap-up automatically after a configurable time (30 seconds by default) and puts the agent back in the queue, so nobody stays unavailable because they forgot to click.
- Agent performance report: shows each agent’s time in incoming calls, outgoing calls and closure, with the number of calls handled. Divide closure time by calls to get each agent’s average ACW.
- Detailed report: a timeline of each agent’s status through the day, so you can see long or frequent closure periods.
- Missed calls and closure: in Call Center Settings you choose what happens to an agent whose phone rang but who did not answer. Closure (the default) takes them out of the ringing rotation until they set themselves back, so the next caller goes to an agent who is ready.
- Dispositions and forms: administrators define dispositions with a short code, a display name and whether the call was connected, and can require a remark for chosen outcomes. Lead forms and custom fields capture details per campaign or queue.
Why ACW gets too long
- Too many fields: forms built for reporting rather than for the agent.
- Typing what the system already knows: caller number, name and account details re-entered by hand.
- Unclear outcome codes: a long list of similar dispositions that agents hesitate over.
- Switching between systems: notes in one tool, tickets in another, the phone in a third.
- Using wrap-up as a break: agents staying in closure to rest because breaks are hard to take.
How to reduce after call work
Show the CRM inside the agent console
When the customer’s record opens on its own as the call arrives, the agent can update it during the call instead of after. Voxdial opens your CRM inside the agent console with click to call and a screen pop on incoming calls. See click to call CRM integration.
Keep dispositions short and clear
Ten clear outcomes beat forty vague ones. Group them by result (resolved, call back, escalated, wrong number) and use a remark only where you truly need detail.
Trim the forms
For each lead form or ticket field, ask who uses it. Remove fields nobody reports on. Pre-fill what you can from the CRM.
Use auto closure where wrap-up is light
For high-volume queues with simple calls, auto closure keeps agents flowing back into the queue. For complex queues, leave it off and give agents the time they need, then watch the closure column in the agent performance report.
Separate breaks from wrap-up
Give agents proper break reasons, such as meal, meeting or training, so rest is recorded as a break and not hidden as wrap-up. This also makes your occupancy and ACW figures honest. See managing remote call centre agents for running breaks across teams.
Coach the outliers
Compare closure time per agent on the same queue. Sit with the slowest and the fastest agents: the slow one may need a shortcut, and the fast one may be skipping notes.
ACW and the wider picture
Short wrap-up is not the goal by itself. Good notes mean the next agent can solve the customer’s issue first time, which lifts first call resolution. Track ACW with AHT, FCR and service level on the wallboard, and read call centre KPIs and the wallboard.
Want to see closure, auto closure and agent reports on your own queues? Book a demo of Voxdial Contact Center or talk to BitVoice.
FAQs
What is after call work in a call centre?
It is the work an agent does after a call ends and before the next one, such as choosing an outcome code, adding notes, filling in a form or scheduling a callback.
How is after call work calculated?
Divide the total time agents spend in wrap-up by the number of calls handled. The result is the average after call work per call.
Is ACW part of average handle time?
Yes. Average handle time is talk time plus hold time plus after call work, divided by the number of calls.
What is auto closure in Voxdial?
It is an agent setting that ends the wrap-up state automatically after a configurable time (30 seconds by default) and returns the agent to the queue, so agents are not left unavailable after a call.
