Want help applying this guide?Ask the DripTell team
A customer hangs up after an agent promises to correct a delivery address. The conversation is over, but the work is not. The outcome still needs to be recorded, the address change needs an owner, and the next person who opens the case must be able to understand what happened.
The right wrap up time is not a universal number. Give each queue enough protected time to complete its minimum reliable record. Then use real work to adjust the timer, extensions, and exceptions. If agents regularly become available before those essentials are complete, the timer is too short. If long research is being hidden inside wrap up, that work needs its own owner and due date.
Wrap up is part of the customer work
Wrap up, also called after call work, is the short period after a call or message ends when the agent finishes necessary administrative work. That might mean recording the outcome, correcting customer details, adding a useful note, or creating the promised follow up.
- Request and outcomeState what the customer needed and what actually happened.
- Decision evidenceKeep the reason behind any approval, refusal or change.
- Next actionWrite the concrete step that remains, if any.
- Owner and due pointName who is responsible and when the work returns.
- Complete or hand offClose the record or transfer an accepted linked task.
This is not spare time between customers. Microsoft includes active wrap up in conversation handle time and measures average wrap up from the start of that state until the representative closes the conversation. Its documentation also notes an important reporting limit: when several representatives handle one conversation, the conversation level measure counts only the last representative's wrap up. That is a reason to inspect transfers separately rather than treating one average as the whole story. Microsoft explains the calculation here.
Define done before choosing a timer
Start with the record, not the clock. For each queue, write down what must be true before the agent becomes available again. A simple customer service record normally needs the request, the outcome, any decision that was made, and the next action with a clear owner. If the issue is finished, the closure rule should say why. If it is resolved, the resolution code should describe the observable action, not merely repeat the request type.
Use different paths for different work
The timer should protect short, necessary completion work. It should not become a hiding place for every task that follows a conversation.
| Situation after the conversation | Best path | Evidence before the agent is ready | What to review |
|---|---|---|---|
| Routine issue is resolved | Standard wrap up | Outcome and concise note are saved | Missing notes and reopened cases |
| Conversation is transferred | Protected transfer wrap up | Receiving owner has the useful context | Transfer quality and repeated questions |
| A brief promised action remains | Standard wrap up or one controlled extension | Action, owner, and due point are recorded | Extensions by queue and outcome |
| Research or back office work will take longer | Separate owned task | Task is accepted and linked to the conversation | Overdue work and unclear ownership |
| Record is incomplete because a system failed | Visible exception path | Failure and temporary owner are recorded | Incident volume and recovered records |
Microsoft documents a specific example after a transfer: representatives may need protected time to finalize notes, and the workstream can keep their capacity blocked during that wrap up. Its transfer guidance also shows why closing the state matters because capacity is released when the session is closed.
The useful distinction is short completion versus ongoing work. If an agent needs to wait for a warehouse answer tomorrow, keeping them in wrap up today does not protect the customer. Create a linked task, assign it, set a due point, and let the agent return to the queue. That is easier to plan and harder to forget.
Set the first policy from real work
Review a representative sample from each queue and channel. Do not combine password resets, damaged orders, account investigations, and sales calls into one average. List the required post conversation actions and measure how long correctly completed examples take. Look at the distribution, not just the mean, because a few complex cases can pull the average upward.
Choose an initial base time that covers normal required work. Add a controlled extension for legitimate short exceptions. When a task cannot fit even with that extension, move it to the separate owned workflow. This keeps the rule understandable:
- Finish the minimum reliable record.
- Use a visible extension only when a short extra step is necessary.
- Create an owned follow up when the work is genuinely longer.
- Return to available only after the record or handoff is complete.
Watch where the missing time goes
A shorter timer can look efficient while making the rest of the operation worse. Pair wrap up time with evidence that shows whether the work stayed complete:
- note completion and quality;
- cases reopened because the outcome was unclear;
- repeated customer questions after a transfer;
- follow ups created late or without an owner;
- time spent in other unavailable states immediately after a conversation; and
- changes in meaningful support touches.
Also compare the policy with team workload and the assumptions in the staffing plan. Protected wrap up consumes real capacity. Hiding it does not create capacity. It only makes the forecast less honest.
Keep ownership visible in a shared inbox
In a shared inbox, the conversation record and the follow up should remain connected. DripTell can support that operating model through shared history, assignment, internal context, and visible ownership in the team inbox. The policy still matters. A tool can show who owns the work, but the team must decide what qualifies as complete and when a longer task leaves wrap up.
Frequently Asked Questions
What is wrap up time in customer support
It is protected time after a customer conversation ends for necessary work such as recording the outcome, updating details, and creating the next owned action.
Is shorter wrap up time always better
No. It is better only when required records remain complete and downstream errors do not rise. A shorter timer that creates missing notes or late follow ups moves work rather than removing it.
Should every queue use the same wrap up time
Usually not. Channels, case types, compliance steps, and tools create different completion work. Use one clear method across the team, but set and review the policy by comparable queue and outcome.
What should happen when work cannot fit inside wrap up
Create a separate linked task with an owner and due point. Do not keep the agent unavailable indefinitely, and do not release them until the minimum conversation record explains the handoff.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy