Calls Blocked in Percent
Definition
Calls Blocked in Percent
Calls blocked in percent is the share of inbound calls that never reach an agent because trunk lines or switch capacity are already full. Callers hear a busy tone or silence. Any rate above 3% signals a capacity failure, not a staffing one.
The metric sits at the network layer of every call center, which makes it distinct from almost every agent-facing KPI you track. Every blocked attempt is a lost service opportunity, and often a lost sale nobody ever counts.
Unlike call abandonment, which happens after the caller reaches the queue, blockage happens before the queue even opens. That distinction decides your fix: blockage points to infrastructure — abandonment points to staffing.
Key takeaways
- The formula is straightforward: (blocked calls ÷ total calls offered) × 100.
- Healthy contact centres keep blockage under 2–3%, aligned with the P.01 Erlang-B grade of service telecom planners use.
- Root cause is usually trunk or switch capacity, not agent shortage.
- High blockage inflates abandonment and drags down service level agreement (SLA) compliance.
- Fixes include SIP-trunk expansion, dynamic overflow routing, and callback deflection.
How it works
Blockage happens at the network layer. When inbound volume exceeds the available voice channels, whether SIP trunks, ISDN lines, or switch ports, the carrier rejects the call before it enters the queue. The caller gets a fast-busy tone.
The core formula is: calls blocked in percent = (blocked calls ÷ total calls offered) × 100. Total calls offered includes both connected and rejected attempts. Some carriers report blockage as a raw count — so you divide by offered volume yourself.
The International Telecommunication Union recommends the Erlang-B model, published in its E.500 series, as the reference method for sizing trunks against a target blockage rate. Planners still treat it as the default.
Those grades of service translate into a simple reading of any blockage number:
| Blockage rate | Reading | Typical cause |
|---|---|---|
| Under 1% (P.01) | Healthy | Adequate trunk capacity, standard target |
| 1–3% | Acceptable | Slight peak-hour tension |
| 3–5% | Warning | Trunk saturation during peaks |
| 5–10% | Critical | Undersized carrier plan or switch ports |
| Over 10% | Failure | Outage, misrouting, or flood traffic |
Blockage caps every downstream number on the dashboard. If 8% of callers never reach the queue, no amount of occupancy tuning will rescue the customer experience, because the lost contacts were never measured in the first place.
Where you read the figure matters too. Carrier call detail records capture attempts the switch never saw, while ACD reports only count calls that already made it inside. When the two disagree, trust the carrier side.
The switch itself is a separate constraint. Automatic call distribution (ACD) ports are finite, and an automatic call distributor sized for last year’s peak will reject this year’s traffic even when SIP capacity looks fine.
Erlang-B sizing takes three inputs: busy-hour traffic in Erlangs, the target grade of service, and a lookup table of channels required. Most workforce management platforms, including NICE, Verint, and Genesys, bundle the calculator inline.
That output feeds straight into next quarter’s carrier order. Get the busy-hour figure wrong and you buy the wrong trunk count, which is why call center forecasting and capacity planning belong in one review, not two.
Deflection belongs in the same conversation. A callback interactive voice response (IVR) option releases the channel while the customer waits, so menu design is a capacity lever, not just a customer experience one.
Examples
Blockage shows up most visibly in seasonal peaks. Retail campaigns, tax deadlines, and product launches all push busy-hour traffic past provisioned capacity, and the providers that fixed it moved voice onto elastic cloud platforms instead of copper.
In 2024, Deloitte’s Global Contact Center Survey found roughly 60% of contact centres run at least one cloud channel. Concentrix, Teleperformance, and TTEC all completed cloud-first migrations between 2022 and 2025 for the same underlying reason.
Alorica, headquartered in Irvine, California, cited a 2023 move to Amazon Connect to clear legacy PBX bottlenecks that had produced double-digit blockage during Black Friday spikes. Foundever — formerly Sitel Group — reported a similar transition in 2024.
On the offshore side, Manila-based providers running U.S. retail brands typically build to a P.01 target through Q4. They over-provision trunks by 30–40%, because an idle SIP channel costs far less than a rejected caller.
Indian majors including Genpact, Infosys BPM, and Wipro published cloud-migration case studies in 2024 and 2025, citing blockage falling from mid-single digits to under 1% after leaving on-premises PBX behind. Same physics, different market.
Public services show the pattern in reverse. Benefits agencies and utilities field busy-signal complaints after policy deadlines and storms, and the cause is almost always a fixed trunk count meeting a demand spike nobody provisioned for.
The financial case is easy to model. Every one-point reduction in blockage recovers roughly 1% of daily call volume, so a 10,000-call contact center rescues about 100 conversations a day.
Related terms
Blocked calls sit inside a cluster of call centre metrics that teams routinely confuse. These are the terms to keep beside it when you diagnose whether a problem is infrastructure, routing, or staffing.
- Call Abandonment: callers hang up after reaching the queue, whereas blocked calls never enter it.
- Automatic Call Distribution (ACD): the switch that routes callers, so blockage climbs once its ports fill.
- Interactive Voice Response (IVR): front-end menu system that deflects requests and reduces raw voice volume.
- Service Level Agreement (SLA): the contract where a target blockage rate usually appears as a named clause.
- Workforce Management: the discipline that forecasts call volume against trunk and headcount capacity.
- Contact Center: the multichannel evolution of the call centre, where blockage is measured per voice channel.
- Call Center Forecasting: the volume prediction work that decides how many trunks you order.
FAQ
These are the questions operations teams ask most about blockage: what target to aim for, how it differs from abandonment, what actually moves the number, and how fast a fix should show up in reporting.
What is a good calls-blocked percentage?
Under 2% is the accepted target, and the P.01 Erlang-B benchmark of 1% is the gold standard. Rates above 5% track with SLA breaches and falling CSAT in contact centre benchmarking from the International Customer Management Institute (ICMI).
Is calls blocked in percent the same as call abandonment?
No. Blocked calls never connect to the queue because trunk or switch capacity is exhausted. Abandoned calls do reach the queue, then the caller hangs up before an agent answers.
How do I reduce calls blocked in percent?
Expand SIP-trunk capacity, add overflow routing to a partner site or cloud pool, and offer a callback instead of a hold queue. Then use forecasting to align provisioning with predicted peaks rather than last year’s averages.
Does IVR increase or decrease blocked calls?
A well-designed IVR cuts blocked calls by self-serving simple requests and releasing trunk capacity sooner. A misconfigured one that loops callers back into the queue inflates blockage during peaks.
How often should I audit my blockage rate?
Watch it live during business hours and review weekly trend reports, since a spike inside a single 30-minute window usually means a carrier fault or a misrouted campaign.
Ready to right-size your voice infrastructure? Compare vetted contact centre providers and match your peak volume to real capacity.
Independent
