Expected wait time
Definition
Expected wait time
Expected wait time (EWT) is the period a caller spends in queue before reaching a live customer-service agent. Call centres use it to set caller expectations, route traffic, and staff the floor. A good EWT signals healthy queue management; a long one quietly drains satisfaction, repeat business, and agent morale.
Key takeaways
- EWT is the forecast a contact centre gives callers about how long they’ll wait, calculated from queue position, average handle time, and live agent availability.
- Industry benchmarks from the 2024 ICMI contact-centre study put a good EWT at under 30 seconds and a tolerable one under two minutes.
- Cutting EWT comes down to three levers: smarter routing, better forecasting, and callback or virtual queueing options.
- Customers abandon roughly 5% to 10% of calls once wait time crosses two minutes, so EWT has a direct revenue impact.
Most contact centres surface EWT through an interactive voice response (IVR) message or a chat-window timer. The metric matters because callers tolerate a known wait far better than an unknown one. A 2024 Zendesk Customer Experience Trends report found that 73% of consumers will switch to a competitor after multiple bad service experiences, and long, unexplained queues sit near the top of that list.
EWT is one of three closely watched waiting metrics, alongside average speed of answer and average handle time. Together they form the operating dashboard for any voice or chat queue.
How it works
Expected wait time is a forecast, not a stopwatch reading. The queueing system divides the number of callers ahead of you by the rate at which agents are clearing calls, then adjusts for current staffing and historical handle time. The figure refreshes every few seconds as conditions change.
Most platforms use a variation of the Erlang C formula, the same maths telecoms have used since the 1910s to size trunk lines, refined with live agent data. The International Telecommunication Union still publishes Erlang reference tables for capacity planning.
The simplified working formula:
| Input | What it means | Typical source |
|---|---|---|
| Callers in queue | Position ahead of the current caller | ACD live counter |
| Average handle time (AHT) | Mean talk + after-call work, last 30 days | Workforce management software |
| Active agents | Logged-in agents in “available” state | ACD live counter |
| Output: EWT | (Callers in queue × AHT) ÷ Active agents | Quoted to caller |
So a queue with eight callers, an AHT of three minutes, and four active agents produces an EWT of six minutes. The IVR rounds and announces a friendly version of that number, often padded by 10% to 15% so the system under-promises and over-delivers.
EWT differs from average speed of answer in one key way: ASA is measured after the fact, EWT is predicted in real time. A centre with a four-minute EWT and a one-minute ASA either has a broken forecast or chronically overstaffs, and either signal deserves a workforce-management review.
Examples
EWT shows up in every queue you’ve ever joined, but the public benchmarks vary widely by sector and channel.
Banking — JPMorgan Chase, 2024. Chase’s mobile-app chat now quotes an EWT under 45 seconds during business hours, the result of a 2023 push that moved password resets and card replacements to self-service bots. Voice EWT for the same accounts still runs three to five minutes during weekday peaks.
Telecoms — BT Group, 2023. UK regulator Ofcom published complaint data showing BT’s average voice EWT climbed to nine minutes during a Q1 outage spike, prompting the carrier to add callback as the default queue option. By Q4 the figure dropped under three minutes.
Healthcare — Kaiser Permanente, 2024. Kaiser publishes EWT bands on its appointment line: under 90 seconds for routine bookings, under 30 seconds for the advice nurse line. The split shows how triaging callers by intent inside the IVR pulls urgent EWT down without hurting overall capacity.
Outsourced BPO — Manila and Cebu, 2024. Source Boost partners in the Philippines typically tender EWT service-level agreements of 80% of calls answered inside 20 seconds, the legacy “80/20” target from the 1990s. Most hit it by running blended shifts that follow the customer’s working day, an arbitrage that’s hard to replicate onshore.
Related terms
EWT sits inside a tight cluster of contact-centre metrics. Knowing one without the others is a recipe for gaming the dashboard:
- Average speed of answer: the actual time callers waited, measured after the call. EWT is the forecast; ASA is the receipt.
- Average handle time: talk time plus after-call work. The denominator that drives every EWT forecast.
- Service level: the percentage of calls answered inside a target threshold, classically 80% in 20 seconds.
- Abandonment rate: share of callers who hang up before reaching an agent, directly tied to long EWT.
- Interactive voice response: the menu system that quotes EWT and routes traffic.
- First call resolution: solving the issue on the first contact, which compresses repeat calls and structural EWT.
FAQ
What is a good expected wait time?
For voice support, under 30 seconds is excellent and under two minutes is acceptable. For live chat, under 45 seconds is the working benchmark, per the 2024 Gartner Customer Service Survey. Anything above five minutes triggers measurable abandonment.
How is expected wait time calculated?
Multiply the number of callers ahead of you by the rolling average handle time, then divide by the count of active agents. The automatic call distributor refreshes the number every few seconds based on live data.
What’s the difference between EWT and ASA?
EWT is the predicted wait quoted to the caller in real time. Average speed of answer is the actual wait measured after the call ends. A wide gap between the two points to a forecasting or staffing problem.
Can EWT be reduced without hiring more agents?
Yes. Tighten IVR routing so callers reach the right queue first time, lift first-call resolution to cut repeat traffic, and offer callback so queued callers don’t tie up a line. Many centres shave 30% to 40% off EWT with these three moves before adding headcount.
Why do call centres add padding to the announced EWT?
A 10% to 15% buffer protects against forecasting error and creates a small positive surprise when the caller is connected sooner. Under-promising on wait time consistently outperforms exact quoting on satisfaction scores.
Does EWT apply to chat and email too?
EWT is a voice-channel term but the logic carries across. Live chat quotes it directly; email queues use a slower-cadence version often called expected response time, measured in hours rather than seconds.
Looking to benchmark or trim your own EWT? Browse vetted contact-centre providers in the Outsource Accelerator directory to compare service-level offers side by side.
Independent
