What actually happens during wrap-up
Wrap-up covers the administrative and follow-through work a completed interaction generates: selecting a disposition code that categorizes the outcome, writing or reviewing call notes, updating a customer or case record, triggering a follow-up task or callback, and in some workflows, completing a brief compliance or quality checklist. None of this is customer-facing time, but all of it is necessary for the interaction to be properly closed out and for the next agent (or the same agent, next time) to have accurate context.
Why wrap-up time matters for staffing
Workforce planning models the total time an agent is occupied per interaction, not just the customer-facing talk time. If wrap-up time is underestimated or ignored in a staffing model, the model will understate how many agents are actually needed to handle a given volume of contacts, since each agent is unavailable for a new interaction during their wrap-up period even though the call itself has ended.
Wrap-up time and Average Handle Time (AHT)
Average Handle Time is typically calculated as talk time plus hold time plus wrap-up time, averaged across interactions. Because wrap-up time is a direct additive component of AHT, a change in wrap-up time — whether from a process change, a new disposition-code taxonomy, or new tooling — changes AHT and therefore changes staffing and scheduling calculations downstream, even if talk time itself hasn’t changed at all.
The tension: minimizing wrap-up time vs. data quality
There is a genuine operational tension in how wrap-up time is managed. Pushing agents to minimize wrap-up time reduces occupied time per interaction and can improve throughput, but rushed wrap-up tends to produce lower-quality disposition data, incomplete notes, and missed follow-up tasks — all of which create downstream cost elsewhere (a customer calling back because a follow-up was never scheduled, a report that misclassifies outcomes because dispositions were chosen carelessly). Some operations set a wrap-up time target or cap; whether that’s the right tradeoff depends on how much the organization depends on accurate post-call data versus raw contact throughput.
A general operational concept, not a Voz360-specific metric
Wrap-up time and its relationship to AHT and staffing are standard contact-center operations concepts that apply across any platform or vendor. This page describes the general concept for education; it does not state a specific Voz360-measured wrap-up-time benchmark or claim a particular reduction, since no such measured statistic is being asserted here.
Can the vendor tell you — in one sentence — which of their AI capabilities are rule-based, which are generative, and which are still roadmap?