Longest delay in queue
Definition
Longest delay in queue: definition and how to track it
Longest delay in queue (LDQ) is the maximum time any single caller waits in the hold queue before an agent picks up. Contact centers watch this figure in real time because one long-suffering caller often signals broader routing failures, understaffing, or a spike your workforce plan did not catch.
LDQ is a peak metric, not an average. Average speed of answer (ASA) can look healthy while a lone caller sits for 20 minutes — LDQ surfaces that outlier before it turns into a complaint or a churn event.
Most cloud contact-center platforms display LDQ on the supervisor wallboard and trigger alerts once a threshold is crossed, giving team leads a chance to reroute, add capacity, or bump the caller to a callback offer.
Key takeaways
- LDQ measures the single longest live hold time, not the queue average.
- It exposes routing gaps and staffing shortfalls that averages hide.
- Most centers pair LDQ with abandonment rate and service level.
- Common alert thresholds sit between 3 and 10 minutes, sector-dependent.
- Callback offers and skills-based routing are the fastest LDQ fixes.
How it works
LDQ is calculated live: the platform starts a timer the moment a call enters the queue and stops it when an agent connects. The current longest-waiting caller becomes the reported LDQ value until they are answered, abandon, or are outbid by a newer, longer-waiting call.
Supervisors usually see LDQ on a wallboard next to calls-in-queue and longest available agent. When LDQ crosses a preset threshold, a visual or audio alert fires so the floor can react.
| Contact center type | Typical LDQ target | Common alert threshold |
|---|---|---|
| Retail / e-commerce support | Under 2 minutes | 3 minutes |
| Financial services | Under 3 minutes | 5 minutes |
| Healthcare triage | Under 90 seconds | 2 minutes |
| Utilities / telco | Under 5 minutes | 8 minutes |
LDQ pairs naturally with the service level metric and abandonment rate. Reading the three together tells you whether a spike is a staffing issue, a routing issue, or a demand surge. Underneath the wallboard, the math is queueing theory: the Erlang C formula is the industry-standard model that predicts how many agents you need to hold LDQ below a target given call volume and handle time. Track LDQ as one input inside your broader key performance indicator stack.
Examples
LDQ shows up wherever inbound voice volume is unpredictable. A few common scenarios illustrate how teams read the number:
- Retail returns line, Black Friday 2024: a mid-sized US retailer saw LDQ jump from 90 seconds to 14 minutes within an hour after a shipping-carrier delay went viral. The supervisor triggered a callback offer and pulled two agents from live chat.
- US health insurer, open enrollment: LDQ regularly hits 8–12 minutes on the first Monday of December. The team pre-schedules 30% more agents that day and still watches the wallboard hourly.
- Telecom outage handling: LDQ spikes to 20+ minutes during regional outages. Most carriers route these calls to an IVR message and log the caller for automated callback once the outage clears.
- BPO customer-service pod: an offshore team supporting a SaaS client caps LDQ at 4 minutes and uses skills-based routing to keep it there. Anything longer triggers a Slack alert to the client’s ops lead.
According to HubSpot’s research on customer satisfaction, 33% of customers name long hold times as the most frustrating part of a service call, so tracking LDQ is not academic. It maps directly to CSAT. Contact-center training body ICMI publishes ongoing benchmarks and playbooks that most operations leads consult when setting LDQ thresholds.
Related terms
LDQ sits inside the queue-metric family and is best read alongside the neighbouring measures below. Each definition below expands the picture LDQ paints on its own.
- Average speed of answer: the mean queue wait across all answered calls.
- Abandonment rate: share of callers who hang up before an agent picks up.
- Service level: the percentage of calls answered inside a target window, usually 80/20.
- Average handle time: the mean length of the agent interaction itself.
- First call resolution: the share of issues closed on the first contact.
- Call center: the operational unit these metrics describe.
FAQ
What is a good longest delay in queue?
Most centers target LDQ under 3 minutes and set an alert threshold between 5 and 8 minutes. Regulated industries such as healthcare aim tighter, often under 90 seconds, because a delayed triage call carries a real safety cost.
How is LDQ different from average speed of answer?
ASA is the mean of every answered call, while LDQ is the single longest live wait. A healthy ASA can hide a caller who has been on hold for 20 minutes; LDQ makes that outlier visible in real time.
Which tools report LDQ?
Every mainstream cloud contact-center platform — Amazon Connect, Five9, Genesys, NICE CXone, Talkdesk — surfaces LDQ on the supervisor wallboard. Most let you set custom thresholds and route alerts to Slack, Teams, or email.
How do I reduce longest delay in queue?
The fastest levers are skills-based routing, callback offers during peak, and pulling agents in from non-voice channels when LDQ trends up. Longer-term, better forecasting inside your workforce management tool prevents most spikes.
Does LDQ include calls that abandon?
No. LDQ measures the wait of the current longest-waiting live caller. Once a caller abandons, they drop out of the LDQ calculation and roll into the abandonment-rate metric instead.
For teams outsourcing voice support to the Philippines’ top outsourcing destination or exploring the Top 40 BPO companies in the Philippines, map LDQ into the SLA before signing, and size the pod using the Outsourcing Cost Calculator. Explore OA’s outsourcing hubs to compare providers who report LDQ transparently.
Independent
