After Conversation Work
After Conversation Work (ACW) is a configurable period of time given to service agents immediately after a customer interaction ends, during which the agent can complete wrap-up tasks without being assigned a new interaction.
Definition
After Conversation Work (ACW) is a configurable period of time given to service agents immediately after a customer interaction ends, during which the agent can complete wrap-up tasks without being assigned a new interaction. This time is used for writing notes, updating case fields, setting follow-up tasks, or dispositioning the conversation.
In plain English
“Here's a simple way to think about it: After Conversation Work is the breath between calls a service team needs. Configurable buffer where agents finish notes, dispositions, follow-ups before being routed new work - without rushing through wrap-up.”
Worked example
At QuickAssist Insurance, agents handle back-to-back chat sessions. The admin configures a 90-second After Conversation Work window so that after each chat ends, the agent has time to update the Case status, add internal notes about the resolution, and set a follow-up task if needed. During this window, Omni-Channel does not route new chats to the agent.
Why After Conversation Work is the breath between calls a service team needs to do good work
A service agent ending a conversation isn't done - they need to log notes, update case fields, set follow-ups, and decide on a disposition before they're ready for the next interaction. Without explicit time for this, agents either rush through wrap-up (and produce sloppy data) or stall the queue (and miss the next call). After Conversation Work (ACW) is the configurable buffer that separates the two: a defined number of seconds or minutes during which the agent isn't routed new work and can finish the loop on what just ended.
The reason calibration matters is that ACW is a productivity dial. Set it too short and reps cut corners on case data; set it too long and queue throughput drops. Watch the actual time agents need to wrap up real conversations (a stopwatch helps), set ACW close to that median, and revisit when the case mix changes meaningfully. The right number for tier-1 password resets is wildly different from the right number for tier-2 escalations.
How organizations use After Conversation Work
Tuned ACW from 30 to 90 seconds; case data quality improved with no measurable throughput hit.
Different ACW per case complexity; tier-3 escalations get longer wrap, tier-1 password resets get shorter.
Trust & references
Straight from the source - Salesforce's reference material on After Conversation Work.
- Configure After Conversation Work TimeSalesforce Help
- How After Conversation Work Affects Service Rep CapacitySalesforce Help
Test your knowledge
Q1. How does After Conversation Work help support agents be more productive?
Q2. What business function does After Conversation Work primarily support?
Q3. What customer experience metric would After Conversation Work help improve?
Discussion
Loading discussion…