Average Time between Calls

Average time between calls (ATBC) measures the interval an agent sits between one live conversation and the next inside a contact centre. Lower ATBC signals tighter workflow, higher occupancy, and healthier unit economics. It captures wrap-up, idle waits, and micro-breaks that push straight into staffing and cost-per-contact models.

Some teams call it inter-call time or agent idle time. The metric matters because compensated minutes without a live customer are the largest hidden cost line in most inbound operations.

ATBC differs from wrap time, which is the post-call admin tail. It includes both the wrap window and any dead time before the next call routes in. Split correctly, the two figures tell a supervisor whether the drag comes from documentation or from routing.

Key takeaways

• Average time between calls (ATBC) equals total logged-in minutes minus talk, hold, and wrap time, divided by the number of calls handled.
• Healthy ATBC for inbound retail sits under 30 seconds; complex tech-support queues run 45-90 seconds.
• High ATBC signals routing lag, over-staffing, or heavy after-call work — three fixable levers.
• ATBC pairs with occupancy, adherence, and average handle time on every workforce management report.
• Cutting ATBC by 10 seconds per call across 300 agents recovers roughly 500 productive hours a week.

How it works

Average time between calls is arithmetic, not statistical. A common formulation looks like this:

ATBC = (Total logged-in time − Total live-call time) ÷ Total calls handled

Live-call time bundles talk, hold, and wrap. Everything else that sits between one hang-up and the next call assignment counts as inter-call time. Modern contact centre platforms — Genesys Cloud, Five9, NICE CXone, Amazon Connect — surface this figure natively per agent, queue, and interval.

Supervisors typically watch ATBC at 15-minute or 30-minute grain, then roll it up daily inside their workforce management reports. A rising trend across a shift almost always ties back to one of three causes: an IVR routing gap, an over-staffed schedule, or agents extending their after-call work to avoid the next queue.

Here is a benchmark reference used inside most mid-market BPO planning cycles:

Ranges draw on the 2024 ContactBabel UK Inner Circle guide and the operational benchmarks published by ICMI. Actual targets shift with call complexity, self-service adoption, and staffing maturity. A queue with a strong IVR deflection layer will always run leaner ATBC than one where every call reaches a live agent.

Examples

Named delivery teams treat ATBC as a coaching lever, not a punishment lever.

Concentrix publishes a “smart adherence” playbook that pairs ATBC dashboards with 30-second nudges when an agent’s ready time drifts above queue target. The company reported a 12% improvement in occupancy on a US telco account after rolling this out in early 2024.

Teleperformance wired ATBC into its “TP Client” analytics suite, exposing it alongside average handle time and first-call resolution to client-side account managers. Transparency shifts the conversation toward staffing decisions instead of blame.

TTEC, through its TTEC Digital arm, bundles ATBC with sentiment scoring so that a spike in inter-call time triggers a wellbeing check on the agent, not just a productivity flag. That framing borrows from a 2024 Deloitte Global Contact Center Survey finding that agent burnout correlates directly with unexplained idle spikes.

Alorica and Foundever run similar programmes across their Philippine and Colombian delivery hubs. Both localise ATBC benchmarks to language complexity and product SKU count instead of applying a single global target — a discipline newer BPOs often miss.

Related terms

• Average handle time (AHT): the counterpart covering talk plus hold plus wrap. ATBC starts where AHT ends.
• Occupancy rate: the productive-minutes ratio that ATBC directly influences.
• Shrinkage: planned unavailable time such as breaks and training, which ATBC deliberately excludes.
• Workforce management: the planning discipline where ATBC feeds forecast and schedule accuracy.
• Adherence: whether agents actually follow their scheduled availability windows.

FAQ

What counts as time “between calls”?

Everything after wrap on one call and before talk-start on the next. That includes short pauses, ready-state waits, and unplanned idle stretches inside a logged-in shift.

Is a high ATBC always bad?

No. Overstaffed queues intentionally show higher ATBC because capacity outruns volume. It signals scheduling slack, not agent slack. The fix is a leaner forecast, not a coaching plan.

How is ATBC different from wrap time?

Wrap time is the post-call admin tail immediately after a customer hangs up. ATBC includes that wrap plus any additional idle time before the next call arrives at the desk.

What’s a reasonable target?

For most inbound queues, 30-90 seconds. Retail runs tighter, healthcare and enterprise support run wider. Compare against your own 60-day baseline before chasing an external number.

Which platforms report ATBC natively?

Genesys Cloud, Five9, NICE CXone, Amazon Connect, and Talkdesk expose it in real-time supervisor views. Legacy PBX setups often calculate it manually from wallboard exports.

Can outsourcing reduce ATBC?

Yes. Offshore BPO partners with mature workforce management routinely deliver 15-25% lower ATBC than newly-built in-house teams, because their forecasting cycles and IVR tuning are more disciplined.

Ready to benchmark your contact centre metrics against vetted outsourced operators? Get a free quote from BPO providers on Outsource Accelerator.