After Call Work (ACW): Formula, Benchmark Ranges, 7-Day Check
After call work (ACW) is the time an agent spends on notes, updates and follow-ups after a call ends and before the next call starts. Measure it per call, not by guesswork.
By Tej Pandya, Founder · Updated 14 Oct 2026
Key takeaways
- After call work (ACW) is the time an agent spends on notes, record updates and follow-ups after a call ends. Average ACW is total ACW divided by calls handled, and it must be read next to the share of calls that have a saved note.
- Benchmark ranges depend on the kind of contact, from under 30 seconds to 4 minutes (ACXPA), so time your own team over seven days instead of copying one. The call-history gap between calls is a proxy for ACW, and a five-call stopwatch check shows how much of that gap is real ACW.
- In our worked model (10 callers, 40 calls a day each), cutting ACW from 3 minutes to 1 minute recovers about 347 hours a month, worth about ₹33,000 of paid time.
- Fix the process before adding a timer: fixed outcome codes, notes typed during the call, one place to write, then automated summaries.
In this article
- 1What is after call work (ACW) and how does it differ from wrap time and ACD time?
- 2How do you calculate average ACW and its share of the shift?
- 3Is there an industry standard for after call work time?
- 4How can you measure your own ACW in seven days?
- 5What does slow ACW cost a telecalling team in rupees?
- 6How do you cut ACW without making notes worse?
- 7Frequently asked questions
A telecaller who ends a call and then spends longer typing the outcome than they spent talking has lost part of the day to something many call-history reports on basic phone systems do not show. After call work is that gap.
The Australian Contact Centre Professionals Association (ACXPA) gives 45 to 90 seconds as common for standard service contacts in its contact-centre glossary (the page carries no date; we read it in October 2026). That range is Australian guidance set for one kind of contact. It is a poor target to copy for a team in Indore or Pune; your own baseline is the better target.
This page is for owners and team leads who run telecallers or support staff. By the end you can time your own team's ACW in one week, put a rupee value on it, and cut it without making the notes worse. It also settles the terms that get mixed up with it, such as wrap time and handling time.
What is after call work (ACW) and how does it differ from wrap time and ACD time?
After call work is the time an agent spends on notes, record updates and follow-up tasks once a call has ended. Wrap time, wrap-up time and after contact work are the same thing: Amazon Connect's metric definitions list "Call Wrap Up time" as another name for it.
Three neighbouring terms cause most of the confusion:
- Average handling time (AHT): the full time a call takes the agent. It is talk time plus hold time plus ACW (ACXPA).
- ACD time: ACD stands for automatic call distributor, the system that routes each incoming call to a free agent. In Avaya's reporting, ACD time is talk time on ACD calls, while ACW time is a separate item. A high ACD time says nothing about wrap-up.
- Break or not-ready time: time away from calls that is not work on a particular call. It stays out of ACW.
If your team has no ACD system and dials from an app, ACW still exists. In call history it shows up as the gap between one call's end and the next call's start. That gap also holds lookups and idle time, so treat it as a proxy for ACW. The seven-day check below tests how much of it is real ACW.
Is there an industry standard for after call work time?
No single after call work industry standard fits every team: ACXPA's own bands run from under 30 seconds to 4 minutes depending on the contact. Use ranges as a rough guide and replace them with your own baseline.
ACXPA gives these bands in its contact-centre glossary. They are Australian guidance, not Indian data:
- Under 30 seconds for simple transactional contacts.
- 45 to 90 seconds for standard service contacts.
- 2 to 4 minutes for complex or regulated contacts.
- 10 to 20 seconds for many contact types when an AI tool drafts the summary (ACXPA).
ACXPA's conclusion is the more useful one: high ACW is usually a systems and process problem rather than an agent behaviour problem.
Our recommendation for an outbound telecalling team with a fixed list of outcomes is to aim for 30 to 60 seconds and treat a stable average above two minutes as a process fault. These are our targets, not a measured standard.
How can you measure your own ACW in seven days?
Sample 20 connected calls per caller across five working days, work out the gap between each call's end and the next call's start, and check how many of those calls have a saved note. Seven days gives you two days to fix the data and read the result.
- SampleTake 4 connected calls per caller per day for 5 days, spread across morning and evening.
- Find the gapFrom your call history, call end = start time + duration. Gap = next call's start − this call's end. Drop any gap over 10 minutes, since that is a break or a meeting, and count how many you dropped. Pass: 2 or fewer of the 20 dropped. Fail: more than 2, so check whether callers are logging breaks properly.
- Check the note rateOpen the saved outcome and note for each of the 20 calls. Pass: 18 or more have an outcome and a next step. Fail: fewer than 18, so fix completeness before reading the average.
- CalculateAverage ACW = total of the kept gaps ÷ the number of kept gaps. Then work out the share of the shift.
- Test the proxyOn 5 of the calls, time the note itself with a stopwatch, from the call's end to the note being saved. Pass: on at least 4 of the 5 calls, writing the note took over half of the gap. Fail: otherwise, which means most of the gap is lookups or finding the next lead, so fix that before reading the gap as ACW.
| Result | What it means | What to do |
|---|---|---|
| Under 60 seconds, note rate 90% or more | Healthy | Leave it; re-check monthly |
| 60 to 120 seconds | Mostly typing free text | Add fixed outcome codes and a note template |
| Over 120 seconds | Process fault | Find the cause: switching between tools, long free text, lookups |
| Note rate under 90% | The average means nothing | Fix completeness, then re-run the sample |
The thresholds in this table are our recommendation.
A note template that fits in 30 to 45 seconds has four fields:
- Outcome: one code from your list.
- Next step: a date and time.
- Objection: two or three words.
- Context: one line.
Example: "Outcome: Call back. Next step: Thursday, 4 pm. Objection: price. Context: needs a demo for 6 users." Test it: a colleague should be able to act on the note without hearing the call. Pass or fail on that alone.
What does slow ACW cost a telecalling team in rupees?
In our model, cutting ACW from 3 minutes to 1 minute for 10 callers recovers about 347 hours of paid time a month, worth about ₹33,000. This is a model with assumed inputs, not an official figure, so replace the inputs with your own.
| Input or step | Value |
|---|---|
| Callers | 10 |
| Calls per caller per day | 40 |
| Working days a month | 26 |
| Shift | 8 hours (480 minutes), so 208 hours a month |
| Monthly pay per caller (illustrative) | ₹20,000 |
| ACW before and after | 3 minutes and 1 minute |
| ACW share of shift, before | 40 × 3 = 120 minutes, 25% |
| ACW share of shift, after | 40 × 1 = 40 minutes, 8.3% |
| Minutes saved per caller per day | 40 × 2 = 80 |
| Minutes saved per month | 80 × 10 × 26 = 20,800 (346.7 hours) |
| Pay per hour | ₹20,000 ÷ 208 = ₹96.15 |
| Paid time recovered | 346.7 × ₹96.15 = ₹33,333 |
That is paid time freed, not cash saved. It becomes money when the 80 minutes a day, roughly a sixth of a shift per caller, goes into more calls and follow-ups.
How do you cut ACW without making notes worse?
Cut ACW in this order: fixed outcome codes, notes typed during the call, one place to write, then automated summaries. Starting with a timer makes notes shorter, not better.
- Fixed outcome codes
A pick-list is faster than free text and can be counted. See call disposition codes for Indian telecallers.
- Notes during the callType the objection and the next step while the customer is talking. Leave only the context line for after.
- One place to write
Every call made through our Business Dialer is logged automatically with the contact, time, duration and outcome, and a caller can add a note against that call so the context is there at the next follow-up.
- Automated summaries
Our AI Call Summaries put the customer's requirement, key discussion points, questions asked, objections raised, next follow-up and call outcome into a summary within a couple of minutes of the call ending. The caller dials the next lead and corrects the summary instead of writing it. To turn summaries into follow-ups, see how to use AI call summaries.
Repeat the seven-day sample after each change. Our recommendation is to change one thing at a time so you know which step moved the number. For a weekly view across callers, see how to track your sales team's calls.
Our Pro plan costs ₹999 + goods and services tax (GST) a month (as of October 2026). It includes three hours of talktime a day, unlimited users and contacts, call recording and history, and team analytics. Extra talktime is ₹49 + GST an hour.
Want a second pair of eyes on your 20-call sample? Talk to Our Expert.
Cut after call work with TalkEasy summaries
Frequently asked questions
No. Average call duration covers only the conversation; average handling time adds hold time and ACW.
Sources
- 1.ACXPA: After Call Work glossary entry, ACXPA, Undated; read October 2026
- 2.Amazon Connect Administrator Guide: metric definitions, Amazon Web Services
- 3.Avaya CMS: ACDTIME, Avaya
- 4.Avaya CMS: ACWTIME, Avaya
- 5.TalkEasy Business Dialer
- 6.TalkEasy AI Call Summaries
