Inbound Calls Average Speed of Answer

Inbound calls average speed of answer (ASA) is the mean time a caller waits in queue before a live agent picks up, after any IVR routing. A sub-30-second ASA is the working benchmark for most inbound queues, and BPOs treat it as a top-line service-level KPI on nearly every client contract.

ASA sits alongside abandon rate and service level as the classic queue-health trio. When ASA drifts upward, callers hang up, first-call resolution suffers, and CSAT erodes within a single shift.

The metric is deceptively simple. Two contact centres with the same average can hide very different distributions — one steady, one built from a handful of long-tailed waits that torch a specific hour of the day.

Key takeaways

• ASA equals the total wait time of answered calls divided by the number of answered calls, expressed in seconds.
• The 80/20 rule (80% of calls answered within 20 seconds) is the durable industry service-level target most contracts still reference.
• ASA excludes IVR routing time; the clock starts when the call enters the agent queue.
• Forecast accuracy, schedule adherence, and occupancy move ASA far more than raw headcount alone.
• Philippines-based BPOs typically staff to a sub-25-second ASA on tier-1 inbound contracts.

How it works

ASA is calculated by dividing the total queue wait time of all answered calls by the number of answered calls in the same reporting interval. Most contact-centre platforms surface it every 15 or 30 minutes, and a reforecast is triggered when a threshold breach persists across two consecutive intervals.

The core formula is:

ASA = (Total wait time of answered calls) ÷ (Number of answered calls)

Abandoned calls sit inside the call abandonment metric, not here. That distinction matters — a queue that shed 15% of callers before pickup can post a flattering ASA that quietly hides a real service failure.

Common inbound ASA benchmarks by vertical, drawing on ContactBabel and ICMI 2024 industry reads:

Three levers move ASA more than headcount alone:

• Forecast accuracy. Under-forecasting call volume by 10% cascades into a 30-40% ASA spike at peak intervals.
• Schedule adherence. 90% is the working floor; every point below adds roughly three seconds to intraday ASA.
• Occupancy. Sustained occupancy rate above 85% burns agents out and paradoxically lengthens handle time, which then lengthens ASA.

Per Salesforce’s 2024 State of Service report, a majority of service leaders now tie ASA directly to CSAT dashboards, which means a queue miss is visible to the CX chief within one reporting cycle.

Examples

Global BPOs publish inbound ASA against contractual SLAs. Concentrix, Teleperformance, and TTEC typically operate to 80/20 or 80/30 service levels on tier-1 client contracts, with ASA reforecasting cadences built into weekly workforce management reviews.

• Concentrix (2024): reports service-level attainment on inbound retail contracts in the 80/20 band across its Philippines and India delivery hubs.
• Foundever (formerly Sitel): publishes contact-centre benchmarks showing sub-25-second ASA on financial-services queues where callback triage is enabled.
• Alorica: runs Philippines-based inbound queues to a 20-second ASA target for several US healthcare payers on multi-year contracts.
• A mid-market BPO deploying Amazon Connect in Manila (2024): cut ASA from 48 seconds to 21 by shifting from static schedules to intraday reforecasting every 15 minutes.

Related terms

• Average handle time (AHT): the downstream metric that swells when ASA is chronically high and agents rush recovery.
• First call resolution (FCR): drops when a stressed queue pushes agents past the 85% occupancy line.
• Service level agreement (SLA): the contract clause that usually pins ASA to a percentile like 80/20.
• Call abandonment: the twin of ASA; abandon rate spikes as ASA lengthens.
• Interactive Voice Response system (IVR): the pre-queue routing layer whose duration is excluded from ASA.
• Customer satisfaction (CSAT): the downstream sentiment score that tracks ASA within a single shift.
• Contact center: the operational unit whose overall service level ASA rolls up into.

FAQ

What is a good ASA for an inbound call centre?

Under 30 seconds is the common working target. The 80/20 rule (80% of calls answered within 20 seconds) is the durable industry service level, though regulated verticals like insurance and healthcare often tighten this to 80/15 in their SLAs.

Does ASA include IVR time?

No. ASA is measured from when the call enters the agent queue, after any IVR menu selection. Including IVR duration conflates self-service adoption with agent-side responsiveness, and those are two very different operational levers.

How is ASA different from average handle time?

ASA is pre-conversation queue wait; AHT is the conversation itself plus wrap-up. High ASA does not directly move AHT, but chronically high ASA burns agents and quietly extends AHT within a week.

Can outsourcing improve ASA?

Yes — most established BPOs can hit sub-30-second ASA within 60 days of go-live because their workforce-management teams reforecast intraday and their agent pools flex across multiple client accounts.

How often should ASA be reviewed?

Every 15 or 30 minutes intraday, then rolled up daily and weekly. A single 30-minute breach is noise; two consecutive breaches should trigger a mid-shift reforecast in any mature contact centre.

What causes a sudden ASA spike?

Under-forecasted volume, agent adherence drops, an outage on a self-service channel, or a marketing campaign that pushed inbound harder than the workforce plan expected. Roughly nine in ten intraday spikes trace to one of those four root causes.

Looking to hit a tighter ASA without in-house hiring? Compare vetted contact-centre partners at Outsource Accelerator.