How to reduce failure demand in a contact center
Failure demand is contact caused by a failure to do something, or to do it right, for the customer the first time; value demand is contact the customer wants to make. Systems thinker John Seddon of Vanguard Consulting coined the terms. To reduce failure demand, measure it by contact reason, fix the upstream causes, and give agents the context to resolve first time.
Failure demand vs value demand
| Failure demand | Value demand | |
|---|---|---|
| What it is | Demand on a service organization caused by the organization’s failure to do something, or to do it right, for the customer | Normal requests for whatever service the organization exists to provide |
| Examples | “Where is my order?”, “Your letter didn’t make sense”, a second call because the first wasn’t resolved | A new order, a product question, a change of address |
| Who named it | John Seddon, Vanguard Consulting, who also puts it at 40 to 60% of contact center volume | |
| What to do with it | Remove the cause; it is avoidable | Serve it well; it is the work |
Definitions as summarized on Wikipedia’s Failure demand entry, 22 October 2026; the 40 to 60% range is credited to John Seddon and Vanguard Consulting.
When it fits
Any contact center that tracks contact reasons, or can start to. The five steps: measure it by tagging every contact with its reason; find the causes upstream (unclear letters, broken digital journeys, handoffs that lose context, promises not kept); fix the causes, not the symptoms, because deflection and IVR menus hide failure demand rather than remove it; resolve first time when it does arrive, with agent assist, knowledge and the full history beside the conversation; and keep watching the reason mix, because if the share of failure demand does not fall, the cause is not fixed.
When it doesn’t
If contact reasons are not captured at all, start with measurement before buying anything.
How Totalix does it
UWXP, the AI experience layer, reasons over why customers make contact and runs natively inside Totalix or beside the platform you already have; the DREAM Workshop maps your failure demand with your leadership team; Totalix tags every interaction with its contact reason, reports on it, and gives agents Agent Assist, knowledge and the conversation timeline to resolve first time.
Failure demand (glossary) → · UWXP → · Keeping AI agents under control → · DREAM Workshop → · Request a demo →
Questions buyers ask
What is the difference between failure demand and value demand?
Failure demand is caused by the organization’s earlier failure; value demand is contact the customer wants to make.
How much contact center demand is failure demand?
John Seddon and Vanguard Consulting put it at 40 to 60% of volume.
Is failure demand the same as avoidable contact?
Close, but failure demand names the cause (a failure upstream), which is what makes it reducible.
Can AI reduce failure demand?
Only if it addresses the cause or resolves the contact first time; a bot that deflects a failure-demand call leaves the failure in place.
How do we start?
Tag contact reasons for a month and sort them into failure and value demand.