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 the automatic call distributor (ACD) or trunk lines are already full. Callers hear a busy signal, a rejection tone, or nothing at all. A blockage rate above 3% signals a capacity failure that erodes revenue, CSAT, and brand trust.
The metric sits at the network layer of every call center, which makes it distinct from most agent-facing KPIs. Every blocked attempt is a lost service opportunity — and often a lost sale that never gets counted.
Unlike call abandonment, which happens after the caller reaches the queue, blockage happens before the queue opens. That distinction matters when you diagnose the fix: blockage points to infrastructure, while 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 used by telecom planners.
- Root cause is usually trunk or ACD 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 IVR.
How it works
Blockage happens at the network layer. When incoming call volume exceeds the number of available voice channels — SIP trunks, ISDN lines, or ACD ports — the switch rejects the call before it enters the queue. The caller experiences a fast-busy tone or a carrier-side rejection message.
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 operations teams must divide by offered volume to derive the ratio. The International Telecommunication Union recommends the Erlang-B model as the reference method for sizing trunks against a target blockage rate.
Common Erlang-B grades of service used by planners:
| 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 ACD ports |
| Over 10% | Failure | Outage, misrouting, or DDoS-style traffic |
Blockage feeds directly into the key performance indicator (KPI) dashboard because it caps every downstream metric. If 8% of callers never reach the queue, no amount of agent occupancy rate tuning will rescue the customer experience.
Erlang-B sizing itself takes three inputs: busy-hour traffic in Erlangs, the target grade of service (say P.01), and a lookup table of channels required. Most modern workforce management platforms, including NICE, Verint, and Genesys, bundle the calculator inline so planners no longer run it by hand. The output feeds directly into carrier-order size for the following quarter.
Examples
In 2024, Deloitte’s Global Contact Center Survey found that roughly 60% of contact centres run at least one cloud channel — a shift that reduced blockage in most enterprise fleets by moving trunks to elastic capacity. Concentrix, Teleperformance, and TTEC all completed cloud-first migrations between 2022 and 2025 for the same reason.
Alorica, headquartered in Irvine, California, publicly cited a move to Amazon Connect in 2023 to eliminate legacy PBX bottlenecks that had produced double-digit blockage on retail campaigns during Black Friday spikes. Foundever (formerly Sitel Group) reported a similar transition in its 2024 investor communications.
On the domestic BPO side, Manila-based providers running for U.S. retail brands typically build to a P.01 (under 1%) target during Q4 peaks, over-provisioning trunks by 30-40% because the marginal cost of an unused SIP channel is far lower than the lifetime value of a rejected caller. This is a standard business process outsourcing (BPO) capacity-planning discipline.
Indian BPO majors including Genpact, Infosys BPM, and Wipro have published similar cloud-migration case studies in 2024 and 2025, citing blockage reduction from mid-single digits to under 1% after moving from on-premises PBX to elastic cloud-voice platforms. The financial impact is easy to model: every 1-point reduction in blockage recovers roughly 1% of daily call volume, which for a 10,000-call operation translates to 100 rescued conversations per day.
Related terms
- Call abandonment: callers hang up after reaching the queue, whereas blocked calls never enter it.
- Automatic call distribution (ACD): the switch that routes callers; when its ports are full, blockage rises.
- Interactive voice response (IVR): front-end menu system that can deflect and reduce raw call volume.
- Service level agreement (SLA): the contractual target blockage rate is usually a named clause.
- Workforce management: the discipline that forecasts call volume against trunk and headcount capacity.
- Contact center: the multichannel evolution of the call center, where blockage is measured per voice channel.
FAQ
What is a good calls-blocked percentage?
Under 2% is the widely accepted target, and the P.01 Erlang-B benchmark (1%) is the gold standard. Rates above 5% consistently correlate with SLA breaches and CSAT decline, per ICMI contact-centre research.
Is calls blocked in percent the same as call abandonment?
No. Blocked calls never connect to the queue because trunk or ACD capacity is exhausted. Abandoned calls reach the queue but 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, deploy a callback IVR that offers to ring back instead of holding, and use forecasting to align trunk provisioning with predicted peaks.
Does IVR increase or decrease blocked calls?
A well-designed IVR reduces blocked calls by self-serving simple requests and freeing trunk capacity. A misconfigured IVR that loops callers back to the queue can inflate blockage during peaks.
How often should I audit my blockage rate?
Monitor it in real time during business hours, and review weekly trend reports. Sudden spikes over a 30-minute window usually indicate a carrier fault or misrouted campaign, both fixable within the same shift.
- Ready to right-size your voice infrastructure? Get a free outsourcing quote from vetted contact-centre providers.
Independent
