After-Call Work

Why It Matters

ACW is a necessary operational step that ensures institutional knowledge is captured after each interaction. Without proper ACW, ticket data is incomplete, historical context is lost, and pattern analysis is impossible because agents skip documentation under time pressure. However, excessive ACW time is an efficiency drain — an agent spending 5 minutes on ACW after every 8-minute call is consuming 38% of their work time on documentation rather than serving customers. Optimizing ACW through better templates, automation, and AI-assisted note generation reduces documentation burden while maintaining quality.

How It Works

ACW is managed through the agent's support platform, which provides the tools needed for post-interaction documentation. Ticketing systems provide structured fields, dropdown menus, and note sections to capture relevant information. AI-assisted documentation tools (auto-summarization from call transcripts or chat logs) are increasingly used to reduce ACW time by generating draft notes that agents review and approve rather than typing from scratch. Best practices include: having the relevant ticket open during the call, using keyboard shortcuts and macros, and standardizing documentation templates to reduce cognitive load.

Real-World Example

Common Mistakes

• ✕Eliminating ACW time goals entirely in pursuit of efficiency — some ACW time is essential for quality documentation; the goal is appropriate ACW, not zero ACW
• ✕Using ACW time as a coaching tool without understanding its purpose — variations in ACW time may reflect documentation thoroughness, not laziness
• ✕Not providing good documentation tools — agents who must navigate clunky systems to complete ACW will rush through it, creating poor data quality

Related Terms