Metrics & KPIs
ASA (Average Speed to Answer)
ASA is the average wait time before a queued call is picked up by an agent. Strongly correlates with abandonment and CSAT.
ASA is the average wait time before a queued call is picked up by an agent. Strongly correlates with abandonment and CSAT.
Average Speed to Answer (ASA), also called Average Speed of Answer, is a contact center metric that measures the average time between when a customer call enters the queue and when an agent picks up. ASA does not include time spent in IVR — only the wait time after the customer has selected a menu option and is queued for an agent.
ASA is one of the most directly customer-experienced metrics. Customers feel ASA immediately, and it correlates strongly with abandonment rate and CSAT.
ASA = Total wait time of answered calls ÷ Number of answered calls
ASA is reported in seconds. Example: 1,000 calls answered with combined wait time of 35,000 seconds. ASA = 35 seconds.
Note: ASA only counts answered calls. Abandoned calls (where the customer hung up before connecting) are tracked separately as Abandonment Rate.
| Service Level Target | Typical ASA |
|---|---|
| 80% of calls answered in 20 seconds | 8-12 sec ASA |
| 80% answered in 30 seconds | 15-20 sec ASA |
| 80% answered in 60 seconds | 25-35 sec ASA |
| Below industry standard | 60+ sec ASA |
A common service level standard is "80/20" — 80% of calls answered within 20 seconds. Operations meeting that level typically see ASA in the 8-15 second range. Above 60 seconds correlates with elevated abandonment rates and CSAT degradation.
| Driver | What's Happening |
|---|---|
| Understaffing | Not enough agents online for the call volume |
| Call volume spikes | Marketing campaigns, outages, or seasonality |
| Inefficient routing | Calls queuing in single skill group while others sit idle |
| High AHT | Each call taking longer reduces agent throughput |
| Schedule adherence | Agents not online when scheduled |
| Skills mismatch | Calls routed to specialists who are unavailable |
ASA is fundamentally a workforce management problem. Reducing ASA means matching agent capacity to call volume in real time.
These metrics overlap but answer different questions:
ASA can be misleading on its own. A team with 10 second average ASA could have 50% of calls answered immediately and 50% waiting 20+ seconds. Service Level distribution is more diagnostic for understanding whether wait times are concentrated or spread.
Improving ASA aggressively can hurt other metrics: - Pushing ASA down by reducing AHT (rushing calls) can hurt FCR and CSAT - Pushing ASA down by adding agents increases cost - Pushing ASA down by simplifying IVR can route more complex calls to wrong agents
The right ASA depends on what tradeoff you're managing. AI-powered call analysis identifies the calls and customer types where wait time most affects CSAT/abandonment, helping operations prioritize ASA reduction where it matters most. Real-time analytics + automated call scoring on 100% of calls makes the ASA-CSAT-FCR tradeoff visible at the segment level instead of the aggregate level.
Industry standard is 20-30 seconds. Top-quartile contact centers operate under 15 seconds. Above 60 seconds correlates with elevated abandonment and CSAT degradation.
ASA is the average wait time. Service Level is the percentage of calls answered within a target window (e.g., 80% in 20 sec). Both should be tracked — ASA shows the central tendency, Service Level shows the distribution.
No. ASA measures the time from when the customer is queued for an agent to when an agent picks up. IVR navigation time is separate.
Yes. Pushing ASA down by rushing agents reduces AHT but can hurt FCR and CSAT. The right ASA target balances wait time, agent capacity cost, and resolution quality.
Last updated: April 2026
