The short answer
After-call work is the time an agent spends after hang-up on notes, dispositions, CRM fields and follow-ups. The biggest saving comes from not retyping what was already said: draft the summary and fields from the call itself and have the agent confirm them. Before that, trim disposition codes and required fields so there is less to fill in.
What counts as after-call work
After-call work (ACW), also called wrap-up, is everything an agent has to do after a call ends before taking the next one. It usually includes:
- Writing call notes or a summary
- Choosing a disposition or wrap-up code
- Filling in CRM or case fields, such as a promise-to-pay date or claim details
- Creating follow-up tasks, callbacks or tickets
- Sending a confirmation email or text
Average handle time (AHT) is talk time plus hold time plus after-call work. ACW is the part of handle time the customer never hears, and often the part agents like least. See the glossary for related terms.
Why it matters, including on FTE contracts
On contracts priced per minute or per call, shorter wrap-up is extra capacity: the same team takes more calls. On FTE contracts, where an outsourcer is paid per agent rather than per call, cutting handle time does not raise revenue by itself.
ACW is still worth fixing there. Notes written from memory are less accurate, which leads to repeat calls and disputes. Retyping after every call is among the most tedious parts of the job. And every minute not spent typing can go to the next customer, to coaching or to a breather after a hard call.
Measure it before you change it
Break ACW down by call type
An average hides most of the story. Split wrap-up time by programme and disposition: a payment call and a complaint call need very different notes.
Watch agents wrap up
Sit with a few agents for an hour. You will see which fields are retyped, which screens are slow, and where agents copy from one system into another.
Separate wrap-up from recovery
Some wrap-up time is an agent catching their breath after a difficult call. That is a scheduling and wellbeing question, not a form-design one. Don't solve it by tightening wrap-up limits.
Fixes, from simplest to most effective
| Fix | What it does | Watch out for |
|---|---|---|
| Trim disposition codes | Fewer, clearer codes are quicker to pick and more consistent to report on. | Clients may require specific codes. Map them rather than delete them. |
| Cut required fields | Remove fields nobody reads, and pre-fill what the system already knows. | Check with the client before removing anything they audit. |
| Note templates | A fixed structure such as reason, outcome and next step makes notes faster to write and read. | Templates still need typing. |
| Hotkeys and text snippets | Common phrases in one keystroke. | Snippets drift from what was actually said. |
| Drafted wrap-ups | The summary and fields are drafted from the call, and the agent reviews and confirms them. | Drafts must be checked, sensitive details masked, and you need to know where the transcript is processed. |
| CRM write-back | Confirmed fields go straight into the CRM or case system, with no copy and paste. | Needs a connector, or a reliable copy-out for systems without one. |
Making drafted wrap-ups work
- The agent stays in charge. The draft is a suggestion. The agent confirms or edits it, and only confirmed text reaches the client's systems.
- Draft the fields, not just the summary. A paragraph of summary still leaves the agent filling in the amount, date and disposition. Structured fields save most of the time.
- Mask before saving. Card numbers, bank details and ID numbers said on the call should never end up in notes. See keeping card data out of recordings and notes.
- Keep a fallback. If a draft is not ready or a connector is down, the agent must still be able to wrap up by hand.
- Measure note quality, not only time. Spot-check confirmed wrap-ups against the recording, especially in the first weeks.
Where Orian fits
How Orian handles wrap-up
- The call summary and CRM fields are drafted at hang-up for the agent to confirm with one key.
- Industry packs draft the fields each programme needs, such as promise amount and date in collections, or loss date, location and police report in insurance claims.
- Sensitive details are masked in the transcript before it is saved, so they stay out of notes.
- Connectors for Salesforce, HubSpot, Zendesk, ServiceNow and Microsoft Dynamics 365, with a copy-out mode for systems without one.
- If the network drops, wrap-ups sync when it is back.