Percent Blocked Calls
Definition
Percent Blocked Calls
Percent blocked calls is the share of inbound calls that never reach an agent or queue because trunk, network, or capacity limits reject them first. A healthy rate stays under 2%, and anything above that points to thin lines or thin staffing.
Every blocked call is a customer who never spoke to anyone. They hear a busy tone, a fast busy signal, or a network error before any menu picks up. That silent friction drains revenue and satisfaction scores in ways queue-based metrics never capture.
Blocking happens in two places. Trunk-side blocking hits when every voice channel on your private branch exchange (PBX) or Session Initiation Protocol (SIP) trunk is already in use. Carrier-side blocking happens upstream at the telco, outside your control.
Both roll up into the same figure your workforce management team reports each morning. That is why the metric belongs on the daily operations board rather than in a quarterly review deck nobody reads until renewal season.
Key takeaways
- Formula: blocked calls divided by total inbound attempts, times 100.
- Healthy benchmark sits under 2%; anything over 5% is a hard alert.
- Peak-hour spikes usually trace to trunk provisioning, not agent shortage.
- Fixing the rate takes SIP capacity planning plus accurate intraday forecasting.
- The metric complements — but never replaces — call abandonment and average speed of answer.
How it works
Percent blocked calls counts every inbound attempt the phone platform rejects before the call enters a queue. Divide blocked calls by total inbound attempts and multiply by 100. The reject fires upstream of any agent, so downstream timing metrics never see it.
Percent blocked calls = (Blocked calls / Total inbound call attempts) × 100
A platform logs a block whenever an incoming call hits a maxed-out trunk group, a full-queue overflow rule, or a carrier congestion signal. The caller never reaches an agent, never hears a greeting, and never lands in your handle-time report.
The reject also happens before the Interactive Voice Response (IVR) menu loads — self-service deflection cannot rescue a call that never connected in the first place.
Three levers drive the number up:
- Under-provisioned SIP trunks or public switched telephone network (PSTN) lines during known peak windows.
- Poor intraday forecasting that under-staffs demand spikes.
- Overflow rules configured to block calls rather than route them to a backup queue.
| Percent blocked calls | Status | Typical cause |
|---|---|---|
| Under 1% | Excellent | Trunks and staffing well matched |
| 1–2% | Healthy | Normal peak-hour fluctuation |
| 2–5% | Watch | Forecasting or trunk gap |
| 5–10% | Alert | Under-provisioned capacity or carrier failure |
| Over 10% | Critical | Trunk group outage or a failed carrier failover |
Contact-centre research firm ContactBabel put the median blocked-call rate for UK operations at roughly 1.4% in its 2024 Decision-Maker’s Guide, with financial services and utilities queues running well above that during outage events.
Quality feeds capacity too. Weak first call resolution pushes the same customers back onto the same trunks a day later, so a repeat-call problem quietly shows up as a blocking problem during the next peak.
Examples
Blocked-call trouble shows up as short, sharp spikes tied to a season, an outage, or a platform migration. These contact centres each traced the cause to capacity rather than agent effort, and each pulled the number back inside a quarter.
Concentrix, Manila (2024). During a Q4 retail-season surge, the Ortigas campus reported blocked-call rates edging above 3% on a US electronics account. Adding 30% SIP trunk headroom over two weeks pulled the metric back under 1.5% — with no extra agents hired.
Teleperformance, Lisbon (2023). A voice-of-customer audit flagged that 4.2% of daytime calls to a European bank’s premium line were blocked at the carrier level. Bringing in a redundant SIP provider dropped the figure under 0.8% inside one quarter.
TTEC, Bogotá (2025). After migrating an insurance client onto cloud voice, TTEC’s Colombia site held blocked calls at 0.6% across a 12-month window. The client cited that number when it renewed.
Foundever, UK (2024). A healthtech account ran percent blocked calls at 2.8% for months. A joint forecasting review with the client rebuilt the intraday staffing plan and cut the rate to 1.1% without touching trunk capacity.
Work the arithmetic once and it sticks. Say a queue takes 42,000 inbound attempts in a week and the switch rejects 640 of them. That gives 1.52%, comfortably inside the healthy band.
Then slice the same week down to Monday mornings only and the rate reads 3.1%. That narrower figure is the one worth fixing, and a weekly average hides it every time.
Related terms
Percent blocked calls sits inside a family of inbound voice metrics. Read it next to the terms below and you can tell an infrastructure problem from a staffing problem in about a minute, which is usually all the time an escalation gives you.
- Call Abandonment: calls that enter the queue and then hang up before an agent answers.
- Average Handle Time: the mean length of an agent and caller interaction, including hold and wrap.
- Service Level Agreement: the contract that usually caps blocked-call thresholds explicitly.
- Occupancy Rate: the share of paid agent time spent handling live contacts.
- First Call Resolution: the quality measure that slips when repeat callers pile onto busy lines.
- Interactive Voice Response: the self-service menu callers reach only after the trunk admits them.
- Workforce Management: the discipline that forecasts and schedules the capacity blocked calls expose.
FAQ
These are the questions operations leads ask first when a blocking alert lands. Every answer holds to one rule: check capacity before you blame the roster, because most spikes start upstream of the queue and never touch an agent’s screen.
What causes percent blocked calls to spike?
Under-provisioned trunks, unexpected volume surges, and carrier congestion top the list. Poor intraday forecasting is the most common controllable cause. Most spikes trace back to a staffing model that missed a demand peak by 20% or more.
What is a good percent blocked calls benchmark?
Under 2% is healthy for most inbound queues. Financial services and healthcare targets sit tighter, often under 1%, because a blocked call may be safety-critical. Over 5% is a hard alert flagged in most service level agreements.
How is percent blocked calls different from call abandonment?
A blocked call never enters the queue, so the caller hears a busy tone or a network error. An abandoned call enters the queue and then hangs up before an agent answers. Blocked calls expose infrastructure gaps; abandoned calls expose wait-time frustration.
Does IVR affect percent blocked calls?
Only indirectly, because the IVR sits after the trunk and a call must already be admitted before the menu plays. Misrouting inside the menu can push callers back into the main queue, saturating trunks and lifting blocking on the next attempt.
Who owns percent blocked calls in a contact centre?
The workforce management team and the telecoms lead usually share it. Workforce management owns forecasting and staffing, while telecoms owns trunk capacity and carrier redundancy. Operations directors review the number weekly against the service level agreement.
How often should you review the metric?
Review it daily at minimum with intraday sampling through known peaks, since Deloitte’s 2024 Global Contact Center Survey reported that centres checking capacity metrics every four hours cut blocked-call rates roughly 40% faster than weekly reviewers.
Ready to cut blocked calls on your inbound line? Get a free BPO quote from an Outsource Accelerator advisor.
Independent
