Maximum delay to answer
Definition
Maximum delay to answer
Maximum delay to answer is the longest a caller should ever wait before a live agent picks up. It is a hard ceiling, not an average, and contact centers write it into service contracts so a single stranded caller counts as a breach.
The cap protects the tail of the queue, not the middle. Average speed of answer can read a healthy 28 seconds while 5% of callers sit past three minutes.
Those tail callers churn, complain, or call back. That is why the cap is contractual as well as operational: most Business Process Outsourcing (BPO) contracts write it into the service level clause with money attached.
Workforce planners staff to the cap, not the average. The paired percentage decides how strict it really is — a 90/20 target forbids more breaches per hundred calls than an 80/20 target at the same ceiling.
Key takeaways
- Maximum delay to answer caps the worst acceptable hold time, not the typical wait.
- The usual pairing, 80% of calls answered within 20 seconds, is an industry default, not a published standard.
- Timing starts when the caller leaves the IVR and stops when an agent answers.
- Breaching the cap triggers service level penalties in most BPO contracts.
- Voice caps sit tighter than chat, and emergency queues run tightest at 10 seconds.
How it works
The clock starts the second a caller leaves the IVR menu and stops when an agent answers. If that gap crosses the cap, the platform flags a breach in real time and logs it against the contract.
Most workforce management platforms treat the cap as a hard threshold. Genesys, NICE CXone, Five9 and Talkdesk stream breach counts to live dashboards, so supervisors watch the meter creep and reroute early.
Every modern call center platform stamps each call with a queue timestamp and an answer timestamp. Subtract one from the other and you have the interval behind every breach report.
Reroute logic reads those rates the moment they cross a warning threshold. When the daytime peak threatens a 20 second cap, the system spills overflow to a nearshore site or promotes agents from a lower priority queue.
Treat the famous 80/20 pairing with care. It is an industry default rather than a figure any standards body publishes, and the bodies usually credited with it prescribe no such target.
SQM Group, which benchmarks more than 500 North American contact centers, does publish a service level standard of 80% of calls answered in 20 seconds. Its abandonment benchmark sits beside it — 6% is standard and under 5% counts as good.
Cap targets shift by channel and by urgency. The bands below are common contract language rather than published standards:
| Channel | Typical cap | Common service level target |
|---|---|---|
| Inbound voice (sales) | 20 seconds | 80% answered in 20s |
| Inbound voice (support) | 30 seconds | 80% answered in 30s |
| Emergency and safety lines | 10 seconds | 90% answered in 10s |
| Premium and VIP queues | 15 seconds | 90% answered in 15s |
| Web chat | 45 seconds | 80% answered in 45s |
| Outbound callback | 60 seconds | 80% in 60s |
| Social and messaging | 5 minutes | 80% in 5 min |
Breach reporting varies. Some platforms treat the cap as a rolling 15 minute average, others as a hard per call flag. The primer in Wikipedia’s contact center overview uses the per call reading.
Some contracts blend the cap with abandonment rate. If a caller hangs up mid wait, the cap gets a pass; if they hold past it, the breach counts once.
Examples
Caps get set by consequence, not convention. A sales queue can live with 20 seconds, an emergency dispatch line cannot, and a chat window buys the agent more room than a ringing phone.
TP, formerly Teleperformance, is the world leader in outsourced customer experience management. It employed over 485,000 people across nearly 100 countries at the end of 2025 and handles over 1 billion interactions a year.
TP publishes no company wide answer cap of its own — caps live in client contracts, not in a provider’s annual report. Ask a prospective partner for the cap on your queue, not its corporate average.
Emergency dispatch centers run the tightest caps of all. The 911 service in the United States and 999 in the United Kingdom work to a 10 second answer target — a 45 second wait can decide an outcome.
Healthcare triage lines sit in the middle. A 20 second cap on a nurse hotline is common, tightening to 10 seconds when the screening IVR flags chest pain.
Retail banks running premium concierge lines target 90% answered inside 15 seconds. The Harvard Business Review study on customer effort backs that: cutting effort, wait time included, builds loyalty faster than trying to delight.
Web chat runs looser because typing gives the agent breathing room. Live sports betting and trading desks still push it back to 20 seconds at peak.
Airlines split the cap during disruption. Elite tier callers stay on a 15 second cap while economy flows to 60 seconds with a call back option, which protects the agreement without stranding anyone.
Utilities got caught out during the 2023 and 2024 winter storms, missing the 30 second cap on outage lines and paying credits to the worst affected callers.
Providers in Outsource Accelerator’s verified BPO directory publish cap targets and breach rates beside their quality scores, so buyers compare like for like.
Related terms
These terms sit next to maximum delay to answer on almost every contact center scorecard. Each carries its own target and its own line in the agreement. They intersect with the cap but never replace it.
- Average Speed of Answer: the mean wait across answered calls, not the ceiling.
- Service Level: the paired percentage that sets how many breaches a contract tolerates.
- Abandonment Rate: the share of callers who hang up before an agent answers.
- First Call Resolution: whether the caller’s issue closes on the first contact.
- Average Handle Time: how long each answered call lasts once connected.
- Call Center: the operational unit where the cap is enforced.
- Workforce Management: the scheduling discipline that staffs to the cap.
FAQ
Common questions about maximum delay to answer: how contact centers set the cap, how they measure it in practice, and how it sits against the service-level agreements built around it.
What is a maximum delay to answer in a call center?
Maximum delay to answer is the longest a caller should wait before a live agent picks up. Centers set it in seconds, usually paired with a target of 80% answered within 20 seconds. Calls past the cap breach the agreement.
How is maximum delay to answer different from average speed of answer?
The cap is the ceiling and average speed of answer is the mean. A center can hit a 28 second average while breaching the cap on 5% of calls, and those tail callers are the ones who leave first.
What is a typical maximum delay to answer for inbound support?
Most support agreements cap voice at 30 seconds with an 80/30 target. Sales queues tighten to 20 seconds and emergency lines to 10, while web chat runs looser at 45.
What happens when the cap is breached?
Most BPO contracts trigger service level penalties worth a share of the monthly fee. Repeat breaches escalate to contract review or termination, and the provider loses any bonus tier tied to over performance.
Who owns the maximum delay to answer metric?
Workforce management owns the staffing maths and operations owns real time recovery when the queue tips. Finance owns the penalty exposure downstream. Everyone reads the same dashboard.
Does chat use the same cap as voice?
No: chat caps usually run 45 seconds because typing hides the delay, while voice caps sit tighter at 20 to 30 seconds.
Explore more contact center terminology and provider guidance at Outsource Accelerator.
Independent
