Last updated: Aug 27, 2026
Average Speed to Answer (ASA) is the average time a call centre agent takes to answer an inbound customer call, including queue wait time but excluding IVR navigation time. ASA is one of the most important signals tied to customer satisfaction in contact centre operations.
Your call centre handles 500 calls in a day. The total queue waiting time across all calls is 1,750 minutes.
ASA = 1,750 minutes / 500 answered calls = 3.5 minutes
That result means customers wait an average of 3.5 minutes before reaching an agent. Whether that is acceptable depends on your industry, call type, and service level targets.
Build and track this metric in PowerMetrics, a modern analytics platform that lets you define metrics and connect your own data.
Get PowerMetrics Free
A widely cited reference point is the 80/20 rule: answer 80% of calls within 20 seconds. This standard originates from early telecom research and remains common in general contact centre planning, though it is not universal.
More specific ranges by sector:
| Industry | Typical ASA target |
|---|---|
| Financial services | 20 to 30 seconds |
| Healthcare | 30 to 60 seconds |
| Retail and e-commerce | 30 to 60 seconds |
| Technical support | 60 to 120 seconds |
| Government services | 2 to 5 minutes |
Source: Contact Centre Association benchmarking data and Gartner customer service research. Targets vary by organization size, call complexity, and staffing model. Use these ranges as a starting point, not a fixed standard.
Use a summary chart to visualize your Average Speed to Answer data and compare it to a previous time period.
Average Speed to Answer
ASA tells you how efficiently your support team is absorbing incoming call volume. A low ASA suggests adequate staffing and smooth call routing. A high ASA signals a mismatch between demand and capacity, which directly affects how customers experience your service before a conversation even begins.
ASA measures queue wait time only. It does not capture:
Time spent in IVR menus before reaching the queue
Handle time once an agent picks up
Abandonment by callers who hang up before being answered
Because ASA excludes abandoned calls, a rising abandonment rate alongside a stable ASA can be misleading. Customers may be leaving the queue before they are counted, making your ASA look better than the actual experience warrants. Track ASA alongside Abandonment Rate to get a complete picture.
A lower ASA is generally better, but context matters. Three scenarios illustrate how the same metric can mean different things:
ASA is below target. A customer waits 90 seconds before an agent answers. The interaction starts on a positive note, and the customer enters the conversation without frustration.
ASA is above target, but managed. A customer waits 10 minutes, but an automated message acknowledges the delay and sets an expectation. The customer stays on the line and arrives at the conversation informed rather than irritated.
ASA is above target and unmanaged. A customer waits 20 minutes with no acknowledgement. They disconnect. The support opportunity is lost, and the customer's impression of your service is shaped entirely by the wait.
The second scenario is recoverable. The third is not. When ASA exceeds your target, proactive communication limits the damage.
Several operational factors influence ASA directly:
Staffing levels: Too few agents relative to call volume is the most common cause of a high ASA. Workforce management forecasting helps align headcount to demand patterns.
Call routing efficiency: Poorly configured routing sends calls to unavailable agents or the wrong queues, adding unnecessary wait time.
Call volume spikes: Seasonal peaks, product issues, or marketing campaigns can push volume above planned capacity. Monitoring ASA in real time allows teams to respond before the impact compounds.
Agent availability: Break schedules, after-call work, and wrap-up time all reduce the number of agents available to answer. Reducing unnecessary after-call work lowers ASA without adding headcount.
ASA sits within a broader set of contact centre performance indicators. The most closely related:
First Call Resolution (FCR): resolving issues on the first contact reduces repeat calls and keeps overall volume manageable, which supports a lower ASA.
Abandonment Rate: a stable ASA alongside rising abandonment often means callers are leaving before they are counted. The two metrics together reveal what ASA alone cannot.
Service Level: the percentage of calls answered within a defined threshold. Service Level and ASA are related but distinct; a team can meet its service level target while still carrying a high average for the calls answered outside that threshold.
