Average Time between Calls

Average time between calls (ATBC) is the idle gap between one live call and the next in a contact centre. Lower ATBC means tighter flow. It covers wrap-up, ready waits, and short breaks that feed straight into staffing plans and cost-per-contact math.

Some teams call it inter-call time or agent idle time. The label matters less than the discipline behind it. Paid minutes without a live customer sit among the largest hidden cost lines in any inbound operation.

ATBC is not wrap time. Wrap is only the post-call admin tail, while ATBC includes that wrap window plus any dead time before the next call routes in.

Split the two figures correctly and a supervisor can see whether the drag sits in documentation or in routing. That single distinction changes the fix.

Key takeaways

• 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, while complex tech-support queues run 45–90 seconds.
• High ATBC points to 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 statistics. Take total logged-in time, subtract every minute spent on live calls, then divide by calls handled. What remains is the paid gap your forecast has to justify.

A common formulation looks like this:

ATBC = (total logged-in time minus total live-call time) ÷ total calls handled

Live-call time bundles talk, hold, and wrap. Everything 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 the figure natively per agent, queue, and interval.

Supervisors usually watch ATBC at 15-minute or 30-minute grain, then roll it up daily inside their workforce management reports. Anything finer turns into noise.

A rising trend across a shift almost always traces to one of three causes: an Interactive Voice Response (IVR) routing gap, an over-staffed schedule, or agents stretching after-call work to dodge the next queue.

Diagnosis order matters. Check the schedule first, because staffing slack is cheap to spot and expensive to ignore. Only then look at agent behaviour.

Here is the benchmark reference used inside most mid-market business process outsourcing (BPO) planning cycles:

Ranges draw on the 2024 ContactBabel UK Inner Circle guide and the operational benchmarks published by ICMI. Treat them as starting points, not verdicts.

Actual targets shift with call complexity, self-service adoption, and staffing maturity. A queue with strong IVR deflection will always run leaner than one where every call reaches a live agent.

One caution: ATBC read alone flatters a busy queue and punishes a quiet one. Always pair it with volume, first-call resolution (FCR), and occupancy for the same interval.

Examples

Named delivery teams treat ATBC as a coaching lever, not a punishment lever. The pattern across the largest outsourcers is the same: publish the number, tie it to a staffing decision, and give agents a way to explain a spike.

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% occupancy gain on a US telco account after rolling this out in early 2024.

Teleperformance wired ATBC into its TP Client analytics suite, showing it beside average handle time and first-call resolution for client-side account managers. Transparency pushes the conversation toward staffing decisions instead of blame.

TTEC, through its TTEC Digital arm, bundles ATBC with sentiment scoring, so a spike in inter-call time triggers a wellbeing check rather than a productivity flag.

That framing borrows from a 2024 Deloitte Global Contact Center Survey finding that agent burnout tracks closely with unexplained idle spikes.

Alorica and Foundever run similar programmes across their Philippine and Colombian delivery hubs. Both localise ATBC targets to language complexity and product SKU count instead of applying one global number — a discipline newer providers often skip.

The common thread is context. A 90-second gap on a Tier 2 technical queue in Manila means something different from 90 seconds on a retail overflow line in Bogotá.

Related terms

ATBC never travels alone. Read it next to the five metrics below and the story stops being about idle agents and starts being about how well the schedule matched the demand curve.

• Average Handle Time (AHT): the counterpart covering talk, hold, and wrap, so ATBC starts where it ends.
• Occupancy Rate: the productive-minutes ratio that ATBC pushes up or down.
• 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

Most ATBC questions come down to definition and target. The answers below cover what the interval includes, why a high number is not automatically a problem, and where the figure shows up in your reporting stack.

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 show higher ATBC because capacity outruns volume, which signals scheduling slack rather than 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 extra idle time before the next call reaches the desk.

What’s a reasonable target?

For most inbound queues, 30–90 seconds. Retail runs tighter, while 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 usually calculate it by hand from wallboard exports.

Can outsourcing reduce ATBC?

Yes, mature offshore BPO partners routinely report 15–25% lower ATBC than in-house teams, because their forecasting and IVR tuning are tighter.

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