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, counted after any routing menu. ASA is the queue health metric BPOs pin to almost every client contract, measured in seconds.

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 satisfaction scores erode inside a single shift.

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

Read ASA as a promise about the worst hour, not the calm ones. That’s why service level targets are written as percentiles rather than averages, and why good weekly reviews open the interval detail instead of the daily roll-up.

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 Interactive Voice Response (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 refresh the figure every 15 or 30 minutes.

A reforecast is triggered when a threshold breach persists across two consecutive intervals — which is why workforce teams watch the interval view rather than the daily average.

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 its callers before pickup can post a flattering ASA that quietly hides a real service failure.

Common inbound ASA benchmarks by vertical, drawing on ContactBabel’s UK Contact Centre Decision-Makers’ Guide and ICMI’s contact centre benchmarking research from 2024:

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, and every point below it adds roughly three seconds to intraday ASA.
• Occupancy. A sustained occupancy rate above 85% burns agents out and 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 satisfaction dashboards. A queue miss is visible to the customer experience chief inside one reporting cycle.

Callback deflection is the fastest structural fix. Offer a scheduled call back once the queue passes a set threshold, and waiting callers leave the calculation entirely, which holds ASA inside the contracted band without adding a single seat.

Examples

Global BPOs publish inbound ASA against contractual service levels, and the numbers get audited monthly. Concentrix, Teleperformance, and TTEC typically run 80/20 or 80/30 targets on tier-1 client accounts, with reforecasting built into weekly workforce 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 on Amazon Connect in Manila (2024): cut ASA from 48 seconds to 21 by moving off static schedules to intraday reforecasting every 15 minutes.

The counter-example is just as instructive. A US utility running a 55-second ASA still held abandon rate near 6% — callers tolerate a longer wait for a billing dispute than for a lost parcel.

Tolerance is vertical-specific, so copying a retail target into a utility queue overspends on seats. Watch ASA next to customer satisfaction rating (CSAT) instead, and you’ll see whether the wait actually cost you goodwill.

Related terms

ASA rarely moves alone. These are the queue and quality metrics that shift with it, plus the contract language that pins it down, so read them together whenever you diagnose a service level miss on an inbound account.

• Average Handle Time (AHT): the downstream metric that swells when ASA stays high and agents rush recovery.
• First Call Resolution (FCR): the quality measure that 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 such as 80/20.
• Call Abandonment: the twin of ASA, since abandon rate climbs as the queue lengthens.
• Interactive Voice Response (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

Buyers ask the same six questions about ASA, and the answers below reflect how BPO workforce teams actually run the metric on live inbound accounts in 2025, from target setting through intraday escalation.

What is a good ASA for an inbound call centre?

Under 30 seconds is the common working target. The 80/20 rule, meaning 80% of calls answered within 20 seconds, is the durable industry service level. Regulated verticals like insurance and healthcare often tighten that to 80/15 in their contracts.

Does ASA include IVR time?

No. ASA is measured from the moment the call enters the agent queue, after any 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 a chronically slow queue burns agents and quietly extends AHT within a week.

Can outsourcing improve ASA?

Yes — most established BPOs hit sub-30-second ASA within 60 days of go-live. Their workforce management teams reforecast intraday, and their agent pools flex across several client accounts, so a volume surge on one queue does not strand the others.

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 operation.

What causes a sudden ASA spike?

Under-forecasted volume, an adherence drop, a self-service outage, or a campaign that pushed inbound harder than the workforce plan expected sit behind roughly nine in ten intraday spikes.

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