Failure demand isn’t a new concept, but it is one that CX teams often overlook.
It’s the kind of interaction that clogs up your lines, eats into agent time, and chips away at customer satisfaction.
It isn’t because someone is asking for help; it’s because something has already gone wrong. And more often than not, the problem didn’t start in the contact center.
“You’re getting demand that’s not necessarily fixable in the contact center,” explains Simon Adnett, VP of Sales for the UK&I / EMEA at Enghouse Interactive.
It’s happening because a process has gone wrong in another part of the business. But your agents are the ones dealing with it – over and over again.
It’s a cost, both in terms of time and money, that doesn’t show up neatly on your dashboards. And because it’s caused by issues outside of CX, it’s often ignored.
With the rise of AI-powered analytics and quality monitoring, failure demand is finally becoming visible. This means that, for the first time, it’s also fixable.
Not All Demand is Good Demand
Most contact center leaders know the shape of their demand. What they often miss is the quality of it.
Some contacts are productive. When a customer needs support, a quote, or an update, that’s value demand.
But when someone’s calling because they didn’t get a delivery, or because they’re chasing an SLA that’s already slipped, or because a repair wasn’t done when promised, that’s failure demand.
And it stacks up fast.
Adnett details how “most contact centers have the same challenge.
“ You have significant demand coming in and a headcount that often doesn’t match.
“So what do you do? You look at automation, at AI, at anything to close that gap. But if a chunk of that demand is self-inflicted? You’re solving the wrong problem.”
Failure demand has a unique sting.
It doesn’t just waste resources; it actively damages the customer experience. And the frustrating part is that it usually originates somewhere else entirely.
Broken Processes, Missed Promises, and the Domino Effect
Failure demand rarely looks like a neat root-cause ticket.
It will often surface as a repeat call, a chase-up, or a vague question that usually starts with: “just checking on…”
These instances all sound harmless enough until you spot the pattern.
Although it can often be attributed to a logistics issue, sometimes it’s internal friction where data hasn’t been passed between teams or responsibilities are unclear.
In these scenarios, while SLAs are technically being hit, customers are still unhappy, as Adnett explains:
It might be a supplier issue or a breakdown between teams. But the result is the same: unnecessary, preventable contact.
And most of the time, it slips under the radar.
Why Traditional QA Misses the Signs
One major reason customer service and experience teams miss failure demand is that most QA programs sample just a fraction of total interactions.
Some companies analyze just one or two percent of their interactions. This is enough to check a compliance box, but not enough to spot recurring friction.
“I remember a CX leader sharing how they’d built a strong QA team, invested in tools, everything,” says Adnett.
“But the complaints kept coming. So they brought in auditors, who systematically went through every interaction over a set period and found the issue . It was a broken process.