Call Avoidance
Definition
Call Avoidance
Call avoidance is when an agent in a contact center dodges live calls on purpose — short hang-ups, padded wrap time, or long aux codes. It can read as output, but it eats at service levels, first-contact resolution, and customer trust.
Most call avoidance is not laziness. It’s a signal that something upstream, such as training, coaching, scheduling, or workload, is broken.
Key takeaways
- Call avoidance shows up as short-duration calls, sudden disconnects, inflated wrap time, and unexplained aux status.
- Root causes are usually structural: burnout, thin training, poor scripts, or bad shift design — not bad agents.
- Speech analytics and calibrated quality assurance catch patterns raw handle-time reports miss.
- Coaching plus workload redesign fixes avoidance faster than punitive policies.
How it works
Call avoidance happens when the cost of taking the next call, cognitively or emotionally, feels higher to the agent than the cost of dodging it. In a live call center, that calculus plays out in seconds, and telephony hands agents dozens of levers.
The most common tactic is the short hang-up: the agent answers, mumbles a greeting, then disconnects before the customer speaks. It reads on the report as a completed call.
The customer redials, lands on the next available agent, and the queue absorbs the friction invisibly.
Other patterns are subtler. An agent might stay in after-call work for eight minutes on a two-minute call. They might toggle to “training” or “coaching” aux codes with no scheduled session.
Some drop the line at the exact moment the customer describes a hard problem: a return, a billing dispute, a technical escalation.
Speech analytics platforms like CallMiner and Verint now flag these signals automatically.
According to CallMiner’s 2024 contact-center benchmark, agents flagged for avoidance behavior handled 22% fewer resolved interactions per shift than the peer median, and their first call resolution scores trailed by 15 to 18 points.
The Deloitte 2023 Global Contact Center Survey reported that 74% of contact-center leaders now cite agent attrition and disengagement, the twin drivers of avoidance, as their single biggest operational risk. That’s up from 44% in 2019.
| Avoidance pattern | What you see in the data | QA counter |
|---|---|---|
| Short hang-up | Talk time under 15 seconds, no customer voice on recording | Random call-review sampling with audio |
| Padded wrap | ACW over 3x the shift median | ACW-to-talk ratio dashboard |
| Aux abuse | “Training” or “coaching” codes with no session logged | Reconcile aux codes with workforce-management schedule |
| Mid-call drop | Disconnect within 30 seconds of a hard-topic keyword | Speech-analytics trigger phrases |
| Transfer dumping | High cold-transfer rate to specific queues | Warm-transfer policy plus routing audit |
Examples
Concrete cases make the pattern easier to spot. Three recent examples from 2023 and 2024 show how call avoidance surfaces across health insurance, utilities, and e-commerce, and how the real fix differed in each operation.
In 2023, a large US health-insurance BPO based in Manila — one of the top ten by seat count — found that 6% of its 1,400 agents were responsible for 41% of sub-20-second calls.
The quality analyst team paired speech analytics with random silent monitoring and traced most cases to two supervisors whose team meetings had drifted into blame sessions.
Reassigning the supervisors and rewriting the escalation script cut avoidance flags by 63% in nine weeks.
A UK utilities contact center discovered in 2024 that its “post-outage” queue had a 19% mid-call disconnect rate. The root cause wasn’t agent behavior at all. It was a softphone bug that dropped calls when agents opened the CRM.
Fixing the integration eliminated 80% of the “avoidance” cases overnight.
A Philippine e-commerce BPO tracked by ICMI in 2024 introduced a peer-coaching model where senior agents shadowed flagged colleagues instead of managers running punitive reviews.
Avoidance incidents dropped 47% in two quarters, and voluntary attrition on the affected teams fell from 34% to 21%.
The lesson across all three: avoidance is usually a symptom, not a root cause. Fix the upstream problem, whether process, tooling, or culture, and the metric moves on its own.
Related terms
Call avoidance sits inside a cluster of contact-center performance concepts, from handle-time metrics to the QA roles that police them. These related glossary entries help you frame the full picture before you act on a flagged agent:
- Average handle time (AHT): the composite metric avoidance most directly distorts.
- First call resolution: the customer-facing outcome avoidance damages most.
- Quality assurance: the discipline that detects and diagnoses avoidance patterns.
- Quality analyst: the role that runs QA calibration and pattern reviews.
- Call center: the operational context where voice-channel avoidance shows up.
- Contact center: the broader multi-channel equivalent covering chat, email, and voice.
- Agents: the frontline workers whose behavior avoidance measures.
Gartner’s 2024 CX research also frames avoidance as one of five “low-effort disengagement signals” leaders should track alongside absenteeism and unplanned aux time.
FAQ
Is call avoidance always intentional?
No. Roughly a third of flagged cases in the ICMI 2024 dataset were caused by telephony bugs, CRM latency, or training gaps, not deliberate dodging. Always investigate the tooling and process before treating a pattern as a discipline issue.
What are the top three KPIs that expose call avoidance?
Short-call rate under 20 seconds, after-call-work-to-talk-time ratio, and unscheduled aux time. Track them per agent and per team, weekly, with speech-analytics context layered on top.
How do speech-analytics tools detect avoidance?
They flag silence patterns, trigger phrases like “let me transfer you,” disconnects within seconds of a keyword, and mismatches between call transcripts and aux codes. CallMiner and Verint publish detection accuracy above 90% for the most common patterns.
Can call avoidance be fixed without firing agents?
Yes, and the data suggests it usually should be. Peer coaching, workload redesign, script fixes, and better break scheduling resolve most cases. Termination is a last resort after documented coaching cycles fail.
How often should QA calibrate its avoidance criteria?
Quarterly at minimum, since contact-center leaders in the Deloitte 2023 survey who recalibrated QA rubrics every three months reported 28% lower avoidance-flag noise than annual-review peers.
Explore how BPO providers structure QA and coaching programs across our industry hubs.
Independent
