After-Call Work

What counts as after-call work

Anything the agent must do for this contact after the customer leaves the line:

• Writing case notes or a call summary in the CRM.
• Selecting a disposition or reason code.
• Sending a confirmation email, text or form the customer was promised.
• Opening a ticket or referral for another team.
• Updating account details captured during the call.

What does not count: breaks, personal time, coaching or a long pause while the agent recovers from a hard call. Those belong in other aux codes. When they leak into ACW, the number stops telling you anything about the work, and your average handle time is inflated with time that is really shrinkage.

Typical ACW ranges

For simple customer service calls with a well-designed CRM, ACW of 15 to 45 seconds is common. Regulated or document-heavy work (insurance claims, healthcare prior authorizations, collections with mandatory notes) often runs 60 to 120 seconds. Technical support with ticket creation can run longer.

The more useful comparison is internal. If the top quartile of agents on a queue wraps in 30 seconds with good notes and the bottom quartile takes 90, the gap is usually training, typing speed or a confusing screen, and all three are fixable.

Why ACW matters for staffing

During wrap the agent is busy but not talking, so ACW is full workload in the staffing math. Thirty extra seconds of wrap on 10,000 calls a week is 83 hours of work, roughly two full-time agents before shrinkage.

ACW also feeds occupancy. Some centers set the ACD to give agents a fixed wrap timer, for example 20 seconds, then automatically make them available. That protects service level but forces agents to finish notes while the next caller is talking, which hurts note quality and the next customer's experience. A better approach is to let agents close wrap manually and coach outliers, while watching the distribution by agent.

How to reduce after-call work without losing quality

1. Do the work during the call. Train agents to type notes and fill fields while the customer is talking or on a brief hold. The best agents finish most wrap before saying goodbye.
2. Simplify disposition codes. A list of 60 reason codes slows everyone down and produces bad data. Ten to twenty well-defined codes is usually enough.
3. Use note templates. A structured note with three or four fields is faster to write and easier to read later than free text.
4. Automate the summary. Call summarization from speech analytics or agent assist tools can draft the note for the agent to check and save. Many centers see wrap drop by a third or more on simple calls.
5. Trigger follow-ups from the CRM. Confirmation emails and forms should go out with one click, not be typed.
6. Coach the outliers. Look at agents whose ACW is twice the queue median. Often they are writing essays, re-reading the whole account or using wrap as a break.

Common ACW mistakes

• Hiding wrap to make AHT look better. Some reports show talk time only. The work still happens and still needs staff.
• Hard caps without fixing the tools. If notes take 60 seconds to write and the cap is 20, agents will either skip notes or do them on the next call.
• Using ACW as a recovery state. A short pause after an abusive call is reasonable, but give it its own aux code so it can be measured and managed honestly.
• Ignoring new hires. Wrap is where tenure shows most. Expect it to be double the floor average in the first weeks and track the decline as part of speed to proficiency.