After-Call Work

In depth

After-call work (ACW), sometimes called wrap-up time, is the admin an agent completes straight after an interaction and before moving on to the next. As the formula shows, the metric is the total wrap-up time across a period divided by the number of interactions handled, giving an average per interaction. The name comes from voice support, but the same work exists on every channel, so the term covers the wrap-up after a chat or an email exchange just as much as after a call.

Typical after-call work includes writing up notes on what happened, tagging or categorising the ticket, updating the customer record, and sending or scheduling any follow-ups the conversation created. None of it is visible to the customer, which is exactly why it is worth measuring: it is real time that does not show up in the conversation itself.

Its most important relationship is with average handle time, of which after-call work is one of three components, alongside talk time and hold time. That connection cuts both ways. Trimming necessary-but-slow admin lowers handle time; letting wrap-up balloon inflates it. It should not be confused with average resolution time, which measures the whole span until a customer's issue is solved, not the housekeeping that follows a single interaction.

What counts as after-call work?

The category covers everything an agent does to close out an interaction properly:

• Notes and summaries. Recording what the customer needed and what was done.
• Tagging and disposition. Categorising the interaction so reporting and routing stay accurate.
• Record updates. Amending account details, order notes, or case status.
• Follow-ups. Sending a promised email, creating a task, or scheduling a callback.

Good after-call work is not waste. Clear notes make the next interaction faster and stop the customer from having to repeat themselves, and accurate tagging is what keeps your other metrics honest. The goal is to make wrap-up efficient, not to cut it out.

What's a good amount of after-call work?

There is no universal benchmark, because the right amount depends on how much each interaction genuinely needs to be documented. A regulated financial query may require detailed notes, while a simple order status update needs almost none. A blanket target risks pushing agents to skimp on documentation that matters.

The most useful approach is to track your own trend and look at what drives it. A steady rise often points to clunky tools or fragmented systems that make the admin slower than it should be, rather than to agents being careless. And the surest way to lower the total across the team is to reduce the number of interactions that reach agents in the first place: a question resolved by self-service carries no wrap-up at all.