Metric guide

After call work (ACW) / wrap time

Q: What is ACW (After Call Work) in a contact centre?

After call work (ACW), also called wrap time or post-call work, is the time an agent spends on tasks related to a customer contact after the call has ended and before they become available for the next contact. ACW typically includes: updating CRM or case notes, scheduling callbacks or follow-up tasks, sending confirmation emails, processing orders or requests initiated during the call, and completing compliance or disclosure logs. ACW is a component of AHT: AHT = talk time + hold time + ACW.

Q: What is a good ACW target for a contact centre?

ACW benchmarks vary significantly by operation complexity. Simple transactional contacts (order queries, basic account updates): 30–60 seconds ACW. Moderate complexity (multi-step processes, case notes required): 60–120 seconds ACW. Complex contacts (regulated advice, insurance claims, complaint handling): 2–5 minutes ACW. ACW above 5 minutes for standard contact types typically signals a process or systems problem, not a behaviour problem — agents spending that long on wrap usually cannot find the right CRM field or are navigating multiple disconnected systems.

Q: How does ACW affect staffing levels?

ACW is a direct component of AHT (Average Handle Time = talk time + hold time + ACW). Because Erlang C uses AHT as its primary input alongside call volume, any reduction in ACW reduces the AHT input to Erlang C and therefore reduces the agent count required to achieve the same service level. Example: 100 calls/hour, AHT 6 minutes (5 min talk + 1 min ACW) → 20 agents. If ACW reduces to 30s (AHT 5.5 min) → 18–19 agents. A 30-second ACW reduction across a 100-agent operation can save 5–8 agents — worth £500k+ annually at typical cost rates.

Q: What is the difference between ACW and hold time?

Hold time occurs during a call when the customer is waiting while the agent performs a task (e.g., checking a system, speaking to a colleague). The customer is still on the line, the call has not ended, and the agent cannot take another call. ACW occurs after the call has ended — the customer has disconnected, the call is complete, but the agent is not yet available in the ACD queue because they are completing post-call tasks. Both contribute to AHT, but they are driven by different problems: hold time is typically reduced by improving system access speed or knowledge; ACW is typically reduced by improving CRM workflow or reducing the post-call task burden.

After call work is the time an agent spends on post-call tasks before they become available for the next contact. It is a direct component of AHT — and through AHT, a driver of your Erlang C agent count. Reducing ACW is one of the fastest levers on headcount without changing service level or volume.

ACW in the AHT formula

AHT components

Talk time

4:00

Agent speaking to customer

Hold time

0:45

Customer waiting, call active

ACW / wrap

1:15

Post-call tasks, call ended

Total AHT

6:00

4:00 + 0:45 + 1:15

ACW represents 20.8% of total AHT in this example. Reducing ACW from 1:15 to 0:45 — a 30-second improvement — reduces AHT from 6:00 to 5:30, an 8.3% improvement. At 100 calls/hour, this typically saves 1–2 agents. Use the AHT impact calculator to model your specific scenario.

What ACW typically includes

CRM and case notes

→Contact summary note
→Call outcome / resolution logged
→Next action or follow-up scheduled
→Account update (address, preference)

Process and fulfilment

→Order raised or updated
→Refund or credit processed
→Referral or escalation logged
→Callback scheduled in WFM system

Compliance

→Disclosure log completed
→Recording flagged for QA
→Vulnerable customer marker
→Complaint formally registered

Communication

→Confirmation email sent
→Internal handoff note
→Third-party notification (e.g. claims team)
→Letter or correspondence triggered

ACW benchmarks by contact type

ACW above 5 minutes for standard contacts typically signals a process or systems problem — agents cannot find the right CRM field or are navigating disconnected systems, not consciously extending wrap time.

Contact typeTypical ACWPrimary ACW driver

Simple transactional (order status, balance)30–60s

Single CRM field update; low process complexity

Account update (address, preferences)45–90s

Multiple field updates across systems if not integrated

General customer service (retail)60–90s

Case note + action; moderate complexity

Financial services (billing, basic advice)90–150s

Compliance log + disclosure record + CRM update

Insurance (renewal, mid-term adjustment)120–180s

Policy system update + document trigger + compliance

Insurance (FNOL / new claim)3–6 min

Complex intake form; mandatory data collection; multiple systems

Complaint (formal registration)3–8 min

Complaint form, regulatory categorisation, next-action scheduling

Technical support (Tier 1)90–180s

Ticket creation, fault logging, escalation note

ACW reduction techniques — ranked by impact

CRM screen-pop with pre-populated fields

Very high impact

If the CRM automatically populates contact summary fields from call metadata (queue, duration, IVR path, account number verified), agents spend zero time entering data they didn't gather — they only confirm and add unique information. Screen-pop that pre-fills the contact type, product touched, and a suggested outcome field can reduce ACW by 40–60% for straightforward contacts.

Post-call guided workflows

High impact

A post-call screen that presents only the fields relevant to this contact type (driven by IVR path or call classification) prevents agents from navigating a full CRM to find the right section. Sequential guided workflows reduce cognitive load and navigate ACW steps faster. Completion rates are also higher — agents are less likely to skip fields when guided linearly.

Single-system integration

High impact

ACW time often doubles when agents must update more than one system (CRM + order management system + billing system). Integrating updates through a single interface — or using a desktop layer that pushes updates to multiple back-end systems simultaneously — removes system switching time. Even a 30-second system switch per update compounds across hundreds of agents.

Templated note structures

Medium impact

Contact note templates for common contact types (complaint, refund, address change) allow agents to select a template and fill in only the unique information rather than writing free-text notes from scratch. Template discipline also improves note quality and consistency for downstream teams.

Speech-to-text note transcription

Medium impact

Tools that transcribe call audio to auto-generate a contact summary draft reduce free-text typing time. Agent reviews and corrects rather than writes from scratch. Accuracy varies by product and accent — review the error rate before rolling out to assess whether correction time exceeds typing time.

ACW cap (maximum wrap time) in ACD

Low–Medium (risk) impact

Setting a maximum ACW time in the ACD (e.g. 120 seconds, after which the agent is automatically returned to available) creates urgency — but also creates a perverse incentive to rush notes and skip compliance steps. ACW caps are controversial and typically harm FCR when agents defer follow-up tasks. Use only with close monitoring; never cap compliance-mandatory ACW.

ACW and schedule adherence

Extended ACW is one of the most common causes of below-target schedule adherence — agents in wrap are not available in the ACD queue and do not count as adherent to their scheduled availability.

Legitimate ACW

Agents completing genuine post-call tasks — CRM update, compliance log, fulfilment action — are in legitimate ACW. This time is correctly captured in AHT and does not represent an adherence problem. It is a process efficiency opportunity, not a behaviour problem.

ACW as recovery time

In high-occupancy operations (>88%), agents occasionally extend ACW deliberately to recover between calls. This is a sign that occupancy is too high — the agent has no other recovery mechanism. The fix is to lower occupancy, not to discipline the behaviour. Disciplining recovery-ACW in a high-occupancy operation accelerates burnout.

ACW questions

What is ACW (After Call Work) in a contact centre?

ACW is the time an agent spends on post-call tasks (CRM updates, case notes, fulfilment actions, compliance logs) after the call has ended and before they become available for the next contact. AHT = talk time + hold time + ACW. ACW is a direct component of AHT and therefore of agent headcount via Erlang C.

What is a good ACW target for a contact centre?

Simple transactional contacts: 30–60 seconds. Moderate complexity: 60–120 seconds. Complex regulated contacts (insurance claims, formal complaints): 2–8 minutes. ACW above 5 minutes for standard contacts usually signals a process or systems problem — agents navigating fragmented CRM screens rather than taking excessive time deliberately.

How does ACW affect staffing levels?

ACW is a component of AHT which is the primary input to Erlang C alongside call volume. Reducing ACW reduces AHT which reduces agent requirements at the same service level. Example: 100 calls/hour, AHT reduces from 6:00 to 5:30 (30s ACW reduction) — typically saves 1–2 agents. Across a 100-agent operation, a 30-second ACW reduction can save 5–8 agents (~£500k/year).

What is the difference between ACW and hold time?

Hold time: customer is waiting on an active call while the agent performs a task. ACW: the call has ended, the customer has disconnected, but the agent is completing post-call tasks. Both contribute to AHT. Hold time is reduced by improving system access speed and knowledge; ACW is reduced by improving CRM workflow and reducing post-call task burden.