What is ACW (After Call Work) and how to reduce it without compromising customer service

The ACW (After Call Work), or post-call work, is one of those metrics that often go unnoticed… until they start affecting everything else.

When ACW spikes, agents have less availability, queues begin to suffer, productivity drops, and the operation becomes harder to scale. But here’s the key point: reducing it isn’t about putting more pressure on the team, it’s about removing friction.

Because yes, lowering ACW is entirely possible. And no, you don’t need to sacrifice service quality to achieve it. In fact, when a business has a solid call and contact centre software in place, it becomes much easier to reduce administrative time, gain better context, and wrap up each interaction more efficiently.

In this article, you’ll learn what ACW is, how it’s calculated, why it increases, and, most importantly, what you can do to reduce it without harming the customer experience.

1. WHAT IS ACW

After Call Work is the time between when a call ends and when the agent becomes available again to handle the next interaction.

Even though the customer has already hung up, the work doesn’t always end there. In many teams, this time is used to properly close the case and document what happened.

During this period, agents typically carry out tasks such as:

• Recording the reason for contact.
• Updating customer details.
• Adding notes from the conversation.
• Categorising the interaction.
• Sending a follow-up email.
• Scheduling a next action.
• Completing mandatory fields in the CRM or contact centre software.

In short, ACW measures all the administrative or wrap-up work that takes place after speaking with the customer.

2. WHAT ACW MEANS IN A CALL CENTRE

In a call centre, ACW is a key metric because it shows how much operational time is spent outside the actual conversation.

It’s important to make a clear distinction: speaking to the customer is not the same as properly closing a case. Both take time, but they don’t impact the operation in the same way.

In environments with multiple channels, agents and workflows, having a cloud omnichannel solution also helps reduce friction and keeps everything far more connected.

It shouldn’t be confused with other common metrics:

• AHT: measures the total average handling time of an interaction.
• Talk time: measures the actual time spent speaking.
• Hold time: measures time spent on hold.
• ACW: measures post-call work.

ACW is part of the overall handling time. That’s why, when it increases significantly, metrics like AHT tend to rise as well.

3. WHY MEASURING ACW MATTERS

Measuring ACW isn’t just about tracking time. Above all, it helps identify where efficiency is being lost.

When analysed properly, it reveals issues that often remain hidden in day-to-day operations: unnecessary steps, slow tools, duplicated records, or poorly designed processes.

Monitoring it helps to:

• Improve team productivity.
• Reduce unproductive time.
• Optimise workforce planning.
• Identify poorly designed processes.
• Spot friction in CRM systems, forms or tools.
• Maintain data quality without compromising service.

It also helps answer key business questions:

• Are agents spending too long documenting each call?
• Are there repetitive steps that could be automated?
• Does the software require too many clicks?
• Are post-call tasks properly designed?

4. HOW ACW IS CALCULATED

The most common formula is:

Average ACW = total post-call work time / total number of calls handled.

For example, if a team spends 1,800 minutes on post-call work and handles 600 calls:

1,800 / 600 = 3 minutes per call.

That said, looking only at the overall average isn’t always enough. To uncover real improvement opportunities, ACW should also be analysed by:

• Agent.
• Team.
• Campaign.
• Call type.
• Channel.
• Time slot.
• Reason for contact.

This is where meaningful optimisation opportunities tend to appear.

5. WHAT IS A GOOD ACW

This is one of the most common questions. The honest answer is: it depends.

There’s no universal ACW benchmark that fits every contact centre. A reasonable level in a simple service may be inefficient in a more automated one… or even too low in a complex operation.

Context matters. A lot.

Factors that influence ACW:

• Process complexity.
• Industry.
• Level of regulation.
• Number of systems involved.
• Need for follow-up actions.
• Customer type.
• Level of automation.

A complex technical support case is not the same as a simple customer query or a short commercial interaction.

That’s why the goal shouldn’t be to achieve the lowest possible ACW, but to maintain a level that is efficient, sustainable and aligned with high-quality service.

Reducing it should never compromise:

• Data quality.
• Process compliance.
• Traceability.
• Case resolution.
• Customer experience.

6. WHY ACW INCREASES

When ACW rises, the issue rarely lies with a single individual. More often, it’s a combination of operational friction, poorly optimised processes and technology that doesn’t quite support the workflow.

These are the most common causes.

POORLY INTEGRATED TOOLS

If agents have to jump between multiple platforms, manually copy information or duplicate records across systems, post-call time increases almost inevitably.

That’s why it’s crucial to have a connected environment where telephony, customer service and CRM work in sync. A solution such as contact centre integrations helps reduce duplicated tasks and speeds up case closure.

TOO MANY MANUAL TASKS

Entering notes, classifying calls, sending emails, creating tickets and updating the CRM manually may seem manageable in a single interaction. The problem arises when this is repeated hundreds or thousands of times a day.

What looks small individually becomes a major time drain operationally.

COMPLEX OR UNCLEAR PROCESSES

When it’s not clear what needs to be recorded, which fields are mandatory or how each case should be closed, every agent ends up handling it differently.

This not only increases ACW, but also creates inconsistencies and makes analysis more difficult.

INSUFFICIENT TRAINING

An agent who doesn’t fully understand the tools or the closing workflow will need more time to complete each task.

Often, the issue isn’t lack of effort, but lack of operational clarity.

QUALITY OF THE PREVIOUS CALL

The more complex, unclear or incomplete the interaction, the greater the post-call effort.

Multiple transfers, conflicting information or lack of context make closing the case slower and more cumbersome.

SLOW OR NON-INTUITIVE SYSTEMS

Sometimes the bottleneck isn’t the process, but the tool itself: slow screens, confusing navigation, too many clicks or overly complex forms.

In those cases, asking agents to work faster doesn’t solve the issue it only worsens the internal experience.

7. RISKS OF REDUCING ACW TOO AGGRESSIVELY

Reducing ACW is a good idea. Reducing it poorly is not.

When this metric becomes an isolated obsession, without operational context or quality considerations, it can produce the opposite of the intended effect.

INCOMPLETE RECORDS

If agents don’t have enough time to properly document the interaction, valuable information is lost.

And when context is missing, the customer usually pays the price on the next call.

LOWER OPERATIONAL QUALITY

Excessive pressure to close quickly can lead to errors, incorrect classifications or poorly executed follow-ups.

What you gain in seconds may be lost later through rework.

MORE REPEAT CONTACTS

When post-call work is incomplete, issues resurface — and so does the customer.

This increases workload and damages service perception.

WORSE AGENT EXPERIENCE

If ACW is used purely as a pressure tool, it creates stress, a sense of constant monitoring and reduced control over the work.

The result is rarely a better operation, more often, it leads to burnout.

8. HOW TO REDUCE ACW WITHOUT COMPROMISING SERVICE

This is the key point. The smartest way to reduce ACW isn’t to push agents to do more in less time, but to design an operation where closing a case requires less effort.

These are the levers that tend to have the greatest impact.

AUTOMATE INTERACTION LOGGING

The more tasks that are handled automatically once the call ends, the lower the administrative burden on the agent.

For example:

• Automatic call summaries.
• Automatic classification by reason for contact.
• Suggested field completion.
• Automatic ticket creation.
• Automated follow-up emails or tasks.

Automation and AI can make a significant difference here. If you want to reduce post-call time without losing context, a solution such as AI for contact centres can help summarise conversations, suggest classifications and speed up repetitive tasks.

INTEGRATE TELEPHONY, CRM AND CUSTOMER SERVICE TOOLS

When agents have all the information in a single interface, closing interactions becomes much smoother.

Good integration eliminates duplication, reduces errors and saves time on every interaction. In this context, having a call and contact centre software connected to the rest of your operational stack makes a clear difference.

REDUCE UNNECESSARY FIELDS AND STEPS

Over time, processes tend to accumulate layers: more fields, more validations, more categories and more “just in case” steps.

The result is predictable: longer closure times.

It’s worth reviewing:

• Which fields are truly mandatory.
• What information can be auto-filled.
• Which steps add no real value.

STANDARDISE CALL CLOSURE

When all agents follow a consistent approach to documenting and closing cases, the process becomes faster and more reliable.

You can support this with:

• Note templates.
• Clearly defined contact reasons.
• Closure workflows by case type.
• Short checklists for logging.

USE REAL-TIME AGENT ASSISTANCE

Agent assistance tools don’t just help during the call, they also reduce post-call work.

For example:

• Automatic suggestions.
• Quick access to history.
• Call reason detection.
• Post-call summaries.
• Automatic extraction of key data.

The less agents have to reconstruct afterwards, the lower the ACW.

IMPROVE CALL ROUTING

Part of high ACW originates before the call even ends. If the call reaches the wrong agent, lacks context or goes through multiple transfers, closing it becomes more complex.

Improving smart routing helps reduce post-call work by connecting customers with the right team sooner and reducing the need to rebuild information.

ANALYSE WHICH CALL TYPES DRIVE HIGHER ACW

Not all interactions require the same post-call effort.

It’s important to identify:

• Which contact reasons increase ACW.
• Which campaigns generate more admin work.
• Which teams or processes have more friction.
• Which agents need more support or training.

Often, significant improvements come from fixing a few specific cases.

IMPROVE OPERATIONAL TRAINING

Training agents isn’t just about product knowledge or customer service skills. It also means teaching them how to close each case efficiently and correctly.

For example:

• How to document interactions.
• What needs to be recorded.
• When to escalate.
• How to classify correctly.
• Which automations to use.

9. ACW AND OTHER CONTACT CENTRE METRICS

ACW shouldn’t be analysed in isolation. It is directly linked to other key performance indicators and therefore to overall operational efficiency.

ACW AND AHT

If ACW increases, AHT usually increases as well.

ACW AND PRODUCTIVITY

High ACW reduces the number of interactions an agent can handle during their shift.

ACW AND FCR

If post-call work is cut too aggressively and records are incomplete, first contact resolution may suffer.

ACW AND CUSTOMER SATISFACTION

Although customers don’t see ACW directly, they feel its impact through poor follow-ups, lack of context or having to repeat information.

10. BEST PRACTICES TO IMPROVE ACW

As a quick reference, these actions tend to deliver good results:

• Consolidate tools into a single interface.
• Automate repetitive tasks.
• Review processes regularly.
• Remove unnecessary fields.
• Use smart templates.
• Leverage AI for summaries and classification.
• Analyse ACW by contact reason.
• Train agents on operational closure.
• Avoid setting ACW targets without context.
• Balance efficiency and quality.

11. PRACTICAL EXAMPLE

Imagine a customer service team that spends an average of 2 minutes and 40 seconds on post-call work.

At first glance, it may not seem excessive. But when multiplied across hundreds of daily interactions, the operational impact is significant.

After reviewing the process, the team identifies that:

• Agents write notes manually.
• Cases are classified in two systems.
• Follow-up emails are sent manually.
• Time is spent searching for history in another tool.

After implementing:

• CRM integration.
• Closure templates.
• Automatic call summaries.
• AI-based classification suggestions.

ACW drops to 1 minute and 25 seconds.

The improvement doesn’t come from pushing agents to work faster, but from removing operational friction and simplifying post-call tasks.

12. CONCLUSION

ACW (After Call Work) is a key metric for understanding how much time is spent on post-call work. When managed well, it improves contact centre efficiency and agent availability. When mismanaged, it becomes a source of overload, errors and poor experience.

The key isn’t to cut it at any cost, but to simplify processes, integrate tools and automate repetitive tasks so agents spend less time on admin and more time delivering value to customers.

Ultimately, reducing ACW isn’t just about saving seconds. It’s about building a more agile, scalable and effective operation for both your team and your customers.