After Call Work - ACW: Definition, Examples and How to Reduce It
After call work (ACW) — also known as wrap time or wrap-up time — is the time an agent spends completing tasks directly related to a customer interaction after the call has ended and the customer has disconnected. It is the period between ending one call and being available to take the next.
ACW is a critical component of Average Handling Time (AHT) and has a direct impact on contact centre efficiency, staffing requirements, and agent occupancy. High ACW means agents spend more time on post-call tasks and less time available for customers — which either drives up costs or drives up queue times, or both.
This guide covers what after call work is, how it affects AHT and workforce planning, how long ACW should be, and 10 practical tips for reducing it in your contact centre.
What after call work is
Any task completed by an agent after a customer call ends — notes, data entry, CRM updates, follow-up actions — before they become available for the next call.
Why it matters
ACW directly drives AHT, staffing requirements, and occupancy. Reducing ACW is one of the most cost-effective improvements a contact centre manager can make.
What this guide covers
The definition, real-world examples, how ACW relates to AHT, how long it should be, who is responsible for it, and 10 practical tips to reduce it.
What is After Call Work?
After call work (ACW) is the time an agent spends on tasks directly related to a customer interaction after the call has ended. During ACW, the agent is not available to receive the next call — they are completing the administrative, documentation, or follow-up work generated by the interaction they just had.
ACW is sometimes called wrap time, wrap-up time, or post-call work. In some contact centre platforms it is captured as a separate status or aux code. However it is labelled, it represents the same thing: the gap between the customer hanging up and the agent being ready for the next interaction.
In plain English
ACW is everything the agent does for the customer after the customer has gone. Notes, data entry, CRM updates, follow-up tasks, case creation — all of it. Until that work is done, the agent cannot take the next call.
Common ACW tasks
- Entering notes and call summary into the CRM
- Updating customer records or account details
- Creating or updating service tickets or cases
- Sending follow-up emails or confirmations
- Notifying other departments of required actions
- Completing compliance or quality documentation
- Scheduling callbacks or follow-up appointments
What is NOT ACW
- Work done while the customer is still on the line
- Breaks, training, or team meetings
- Idle/available time between calls
- Aux code time unrelated to a specific call
- Admin tasks not connected to a specific interaction
A Real-World After Call Work Example
Here is a concrete example to illustrate what ACW looks like in practice — and why it matters.
The call
A customer rings a contact centre to place an order for a product. During the 3-minute call, the agent takes the customer's details, confirms the order in the ordering system, gives the customer an order reference number, and ends the call.
The ACW
After hanging up, the agent must: notify the warehouse team via a separate system, enter the customer's personal details and purchase history into the CRM for future marketing use, and create a follow-up task for next-day dispatch confirmation. This takes 90 seconds.
The result
The total AHT for this interaction is 3 minutes (talk time) + 90 seconds (ACW) = 4.5 minutes. The agent is only available for the next call after that 90 seconds of post-call work is complete.
The key insight from this example
The 90 seconds of ACW was entirely driven by the fact that the contact centre uses multiple disconnected systems — the ordering system, the warehouse system, and the CRM are all separate. If these were integrated, much of this work could either be done during the call or automated entirely. ACW is often a symptom of poor systems integration more than agent behaviour.
ACW and Average Handling Time
After call work is one of the three components of Average Handling Time — the most commonly used operational metric in contact centres. Understanding how they relate is essential for workforce planning.
ACW is the component of AHT that agents and managers have the most direct ability to influence through process and system improvements. Talk time is largely driven by the nature of customer enquiries — you cannot dramatically reduce a complex call. Hold time can be improved through better knowledge access. But ACW can often be reduced significantly through better systems integration, clearer expectations, and smarter tooling.
Example 1 — All on-call
Agent spends 200 seconds talking to a customer, entering all information during the call. The customer disconnects and the agent is immediately available.
Talk time: 200s + ACW: 0s = AHT: 200s
Example 2 — Post-call wrap
Agent spends 100 seconds on the call, then 100 seconds post-call entering notes. Same AHT — but the customer had a shorter call and the agent was unavailable for 100 extra seconds.
Talk time: 100s + ACW: 100s = AHT: 200s
💡 ACW's impact on workforce planning
Because ACW is part of AHT, it feeds directly into Erlang C workforce planning calculations. A 30-second reduction in average ACW across a team can meaningfully reduce the number of agents required to hit your service level target — or allow the same headcount to handle more calls. It is one of the highest-leverage improvements available to a contact centre manager.
How Long Should After Call Work Be?
There is no single correct ACW time — it varies significantly by industry, contact type, and the systems and processes your contact centre uses. A complex financial services call with regulatory documentation requirements will have much higher ACW than a simple order status enquiry. What matters is that your ACW is as low as it can be while still allowing agents to complete the required tasks accurately.
Simple transactional contacts
For straightforward interactions — order status, account enquiries, basic information requests — ACW should typically be under 30 seconds. If it is higher, there is likely a systems or process issue worth investigating.
Standard service contacts
For typical customer service contacts — complaints, account changes, troubleshooting — ACW of 45–90 seconds is common. The target should be defined based on what needs to be documented, not left open-ended.
Complex or regulated contacts
Financial services, healthcare, and insurance contacts often involve compliance documentation, case creation, and multi-system updates. ACW of 2–4 minutes may be appropriate — but should still be systematically reviewed for reduction opportunities.
AI-assisted contacts
AI call summarisation tools are now capable of generating a draft call summary for the agent to review, edit, and save — reducing ACW to as little as 10–20 seconds for many contact types. This is one of the fastest-growing ACW reduction levers available.
Who is Responsible for After Call Work?
A common misconception is that high ACW is primarily an agent behaviour problem. In reality, the contact centre manager typically has far more influence over ACW than the agent does. The systems, processes, and expectations the organisation puts in place are the primary drivers of ACW — agents work within the constraints they are given.
Manager's responsibility
- Defining what documentation is actually required after each call type
- Providing integrated systems that reduce manual data entry
- Setting clear, consistent expectations for what "good" ACW looks like
- Investing in tools that automate repetitive post-call tasks
- Removing unnecessary or redundant documentation requirements
- Creating feedback channels for agents to flag process inefficiencies
Agent's responsibility
- Completing required documentation accurately and promptly
- Not extending ACW unnecessarily (e.g. personal tasks during wrap time)
- Using available systems and tools efficiently
- Flagging system or process barriers that inflate ACW
- Following established documentation standards consistently
The manager's biggest lever: clarity
One of the most impactful things a manager can do is be explicit about what is and is not required in post-call documentation. Without clear standards, some agents will write extensive notes for every call while others will leave minimal records — both creating different problems. Clear documentation standards, regularly reinforced through coaching, create consistency and make ACW measurable and manageable.
10 Tips to Reduce After Call Work in Your Contact Centre
Reducing ACW is one of the highest-return improvements available to contact centre managers. These 10 strategies address both the system and process drivers of ACW — and the agent behaviour side.
Provide comprehensive agent training
Agents who are confident in navigating systems, accessing information quickly, and resolving common issues efficiently will complete their ACW faster and more accurately. Comprehensive onboarding and ongoing refresher training — particularly on system navigation and documentation standards — directly reduces ACW. Team leaders who provide regular side-by-side coaching can identify specific bottlenecks for individual agents in real time.
Be explicit about documentation requirements
Define precisely what agents should document for each call type — not just "add notes." Should they record customer sentiment? The exact resolution provided? Follow-up actions? Verbatim customer statements? Without clarity, agents default to either too much or too little. Documented standards, reinforced through coaching, create consistent ACW across the team and make it easier to identify outliers.
Integrate your systems
Much of the highest-impact ACW comes from agents having to enter the same information into multiple disconnected systems after a call. CRM integration with your contact centre platform, automated data syncing between systems, and single-pane-of-glass interfaces for agents all reduce the manual effort required post-call. This is a technology investment with one of the most direct and measurable returns in contact centre operations.
Use screen pops and pre-populated fields
When a call arrives, screen pops that automatically display the customer's record, recent history, and relevant context give agents a head start — reducing both talk time and ACW. Pre-populating fields where data is already known (customer name, account number, previous contact reason) means agents are updating rather than creating from scratch, which is significantly faster.
Leverage AI call summarisation
AI tools that automatically generate a draft call summary from the conversation transcript are one of the fastest-growing ACW reduction technologies available. The agent reviews, edits if needed, and saves — reducing documentation time from several minutes to as little as 15–30 seconds for many call types. This is no longer a future capability; it is available from most major contact centre platform vendors today.
Optimise call scripts and workflows
Clear call scripts and guided workflows help agents capture required information during the call in a structured way, reducing the need for retrospective note-taking after it. If agents need to ask the same set of questions and record the same fields for a given call type, building that structure into the call flow rather than leaving it to post-call memory will reduce both errors and ACW.
Automate routine post-call tasks
Automated call dispositioning, automated follow-up email triggers, and workflow automation for common case types can eliminate significant volumes of manual ACW. If an agent handles 50 calls per day and each call requires sending the same type of confirmation email, automating that task saves 50 individual manual actions — and reduces the chance of errors or omissions.
Maintain a strong knowledge base
An up-to-date knowledge management system that agents can search quickly during and after a call reduces the time spent looking for information post-call. If agents know they can find the right resolution steps, escalation paths, and compliance requirements in seconds, they spend less time searching and less time writing incorrect notes they later have to correct.
Create an agent feedback loop
Frontline agents are the first to know when a system is slow, a process is redundant, or a documentation requirement is unclear. Building a structured way for agents to flag ACW-causing issues — and demonstrating that those issues are acted on — surfaces improvement opportunities that management cannot always see. Agents who feel heard about operational problems are also more engaged and more likely to follow standards consistently.
Monitor, coach, and provide regular feedback
Regular monitoring of agent ACW at the individual level — combined with targeted coaching sessions — identifies both outliers and systemic issues. An agent with consistently high ACW may be using a workaround for a broken process, compensating for a knowledge gap, or simply unclear on expectations. Side-by-side coaching allows team leaders to observe exactly where the time is being spent and provide real-time support. ACW data without follow-through coaching is just a number — the coaching is where the improvement actually happens.
Frequently Asked Questions About After Call Work
What does ACW stand for in a call centre?
ACW stands for After Call Work. It refers to the time an agent spends on tasks related to a customer interaction after the call has ended and the customer has disconnected. It is also sometimes called wrap time, wrap-up time, or post-call work. During ACW, the agent is not available to receive the next call.
What is included in after call work?
After call work typically includes: entering notes and call summaries into the CRM, updating customer account records, creating or updating service tickets, sending follow-up emails or confirmations, notifying other teams of required actions, and completing any compliance or quality documentation. The specific tasks depend on the contact centre's processes and the nature of the call.
How is after call work different from Average Handling Time?
ACW is a component of AHT, not the same thing. Average Handling Time = Talk Time + Hold Time + After Call Work. AHT measures the total duration of an interaction from the agent's perspective. ACW is specifically the post-call portion — the time after the customer has disconnected. You can have two calls with identical AHT where one has no ACW (all work done on-call) and another has significant ACW (post-call documentation).
What is a good after call work time?
There is no universal benchmark — it depends entirely on the nature of your contacts, your systems, and what documentation is required. For simple transactional calls, under 30 seconds is achievable with good systems. For standard customer service contacts, 45–90 seconds is common. For complex regulated interactions, 2–4 minutes may be appropriate. The right target for your centre is the minimum time required to accurately complete all necessary post-call tasks.
Who is responsible for reducing after call work?
Primarily the contact centre manager — not the agent. The systems, processes, documentation requirements, and tooling that drive ACW are all management decisions. Agents work within the constraints they are given. While agents have a responsibility to use their time efficiently and follow standards, the biggest ACW reduction opportunities — systems integration, automation, clear documentation standards, AI summarisation — are all within management's control.
Should I aim for zero after call work?
Not necessarily. Instructing agents to complete all work while the customer is on the line will technically eliminate ACW — but it is not always the best approach. Agents may seem distracted or rushed, and customers may feel they are holding the agent up. For most contact types, some post-call work is appropriate. The goal is to make ACW as short and structured as possible, not to eliminate it at the expense of call quality.
How does AI reduce after call work?
AI call summarisation tools transcribe the conversation in real time and generate a draft summary of the key points, actions, and outcomes. The agent reviews and edits the summary (if needed) and saves it — reducing documentation time from several minutes to as little as 15–30 seconds. This is now available from most major contact centre platform vendors and is one of the most impactful ACW reduction technologies currently available.
How does ACW affect staffing and occupancy?
ACW is part of AHT, which is a direct input to Erlang C workforce planning calculations. Higher ACW means higher AHT, which means more staff required to handle the same call volume at the same service level. Reducing ACW — even by 20–30 seconds — can allow you to handle more calls with the same headcount, or achieve the same volume with fewer agents. It also affects occupancy: higher ACW means agents spend more time between calls on post-call tasks, reducing their availability for the next contact.
Where to Next
Summary: After Call Work
After call work is the time between a customer disconnecting and an agent being available for the next call. It is a direct component of Average Handling Time and has a measurable impact on staffing requirements, agent occupancy, and service levels. Getting it right matters both commercially and operationally.
The most important insight for contact centre managers: high ACW is usually a systems and process problem, not an agent behaviour problem. Disconnected systems, unclear documentation standards, and lack of automation are the primary culprits — and they are all within management's control to address. Agents who are given integrated tools, clear expectations, and AI-assisted documentation will consistently deliver lower ACW than those who are not.
Use the 10 tips in this guide as a starting framework. Prioritise systems integration and AI summarisation for the fastest wins, invest in coaching and feedback loops for sustained improvement, and model the workforce planning impact of any ACW reduction using the Erlang C Calculator to build the business case.
