After-call work: the invisible queue
The call ends, the customer leaves happy, and the agent is still working — tagging, typing, updating. After-call work is a full component of handle time and the largest pool of support capacity nobody puts on a budget. How much it eats, and how to measure it before you squeeze it.
The call ends. The customer hangs up happy. And the agent is still working — typing a summary, tagging the ticket, updating three fields in the CRM, setting a follow-up reminder. For the next thirty, sixty, ninety seconds, sometimes several minutes, that agent is unavailable to the queue and invisible to every real-time board a supervisor is watching. Do that after every call, across every agent, all day, and you have the largest pool of support capacity that never appears on a budget: after-call work.
The work that hides after the customer leaves
After-call work — wrap-up, ACW, disposition, whatever your platform calls it — is everything an agent does to close out a contact once the conversation is over. It is not a footnote to the call. It is a full component of average handle time, sitting right alongside talk time and hold time in the formula.
Ninety seconds sounds trivial until you notice how much of the job it quietly claims. Reps do not spend their day talking to customers as much as anyone imagines:
The rest is administration — and wrap-up is one of the biggest recurring pieces of it. It hides so well because it behaves differently from the rest of the call: talk and hold light up the live queue board, but wrap-up happens after the customer is gone, in a state most tools log as "handling" and few reports ever break out on its own.
After-call work is the only part of the job that happens after the customer is gone — which is exactly why no dashboard watches it, and exactly why it grows.