The Difference Between Value Demand, Failure Demand and Avoidable Demand
Introduction
Not all customer contact is equal.
Some contact is useful. It is the reason your contact centre exists. A customer wants to buy, apply, change, renew, ask, book, resolve or understand something. That is demand you should expect, welcome and design for.
Some contact is not useful at all. It only happens because something has gone wrong. A customer is chasing a missing update. Repeating information. Asking why a refund has not arrived. Calling back because the last answer did not solve the problem. That is failure demand.
Then there is a third category that often gets missed: avoidable demand.
Avoidable demand is contact that could have been prevented with better communication, better journey design, better self-service, better IVR routing, better digital content or better proactive updates.
For contact-centre leaders, the distinction matters.
Because if you treat all demand the same, your only options are to add more agents, push harder on average handling time, add more channels, or introduce automation to absorb the volume.
But if you understand what type of demand is coming in, you can start to reduce the work at source.
That means lower cost, better customer experience, less pressure on agents and more capacity for the contacts that genuinely need human help.
What is value demand?
Value demand is contact the customer would still need to make even if everything in the organisation was working well.
It is the customer’s original reason for contacting you.
Examples include:
“I’d like to open an account.”
“Can I get a quote?”
“I need to make a booking.”
“I want to change my address.”
“I’d like to understand which product is right for me.”
“I need to report a new issue.”
“I want to make a payment.”
“I need help with a complex situation.”
This is demand that has value from the customer’s point of view.
It does not mean every value-demand contact needs to be handled by an agent. Some value demand can be served well through digital channels, automation, clear web content, IVR self-service or proactive communication.
But the key point is this: the contact is legitimate.
The customer has a real need. The organisation exists to meet that need. The job is to design the best route for that demand, whether that is self-service, assisted service or expert support.
What is failure demand?
Failure demand is contact caused by the organisation failing to do something, or failing to do it properly, for the customer.
The concept is closely associated with John Seddon and the Vanguard Method. The classic definition is demand caused by a failure to do something, or to do something right, for the customer.
In plain English, it is the contact that should not have happened.
Examples include:
“Where is my refund?”
“I was told someone would call me back.”
“I have already explained this twice.”
“Your system says my payment has failed, but the money has left my account.”
“I received a letter I don’t understand.”
“I uploaded this document last week.”
“I was transferred to the wrong team.”
“The chatbot told me to call you.”
“I keep getting different answers.”
Failure demand is expensive because it creates work without creating value.
It also damages trust.
By the time the customer contacts you, they are often already frustrated. They may not describe the issue neatly. They may be more emotional. They may take longer to handle. They may need reassurance before the agent can even get to the practical problem.
That means failure demand often increases:
Call and chat volumes
Average handling time
Repeat contact
Complaints
Escalations
Back-office rework
Agent stress
Customer churn
The contact centre usually feels the pain, but it rarely owns the root cause.
The cause may sit in operations, billing, fulfilment, digital, marketing, IT, policy, product, compliance or another part of the organisation.
That is why reducing failure demand is not just a contact-centre performance project. It is a customer journey project.
What is avoidable demand?
Avoidable demand is contact that could reasonably have been prevented.
It overlaps with failure demand, but it is not exactly the same.
Failure demand is created by something going wrong.
Avoidable demand can also be created by poor design, lack of clarity, unnecessary complexity, weak communication or missing information.
Examples include:
Customers calling because they cannot find opening times.
Customers asking for a link that could have been sent by SMS.
Customers calling to check progress because no status updates are available.
Customers asking what documents they need because the website is unclear.
Customers choosing the wrong IVR option because the menu language is confusing.
Customers contacting an agent because the chatbot does not make its limitations clear.
Customers asking basic “how do I?” questions because instructions are buried or written in internal language.
Customers calling after receiving a letter that uses formal wording but does not clearly explain what they need to do next.
Some of these may be failure demand. Some may not.
For example, if a refund is late and the customer calls to chase it, that is failure demand.
But if the refund is still within the promised timescale and the customer calls because they were never told when to expect it, that is avoidable demand caused by a communication gap.
The difference matters because the fix is different.
Failure demand usually needs a root-cause fix.
Avoidable demand often needs a design, communication or channel fix.
A simple way to separate the three
Here is a practical test.
Ask this question for each customer contact:
Would this customer still need to contact us if the journey had worked clearly, correctly and as expected?
If the answer is yes, it is probably value demand.
If the answer is no because something went wrong, it is failure demand.
If the answer is no because the customer could have been better informed, better routed or better supported without needing to contact you, it is avoidable demand.
Here is how that looks in practice.
Customer contactDemand typeWhy“I want to open a new account.”Value demandThe customer has a genuine need the business exists to serve.“Where is my new account application? I applied three weeks ago.”Failure demandThe customer is chasing because the process has not worked as expected.“How long does an application normally take?”Avoidable demandThe contact may have been prevented with clearer expectations and proactive updates.“I need to report an emergency repair.”Value demandThe customer needs immediate service.“Nobody came to repair the issue yesterday.”Failure demandThe service promise was not met.“Is this classed as urgent or non-urgent?”Avoidable demandThe customer may need clearer guidance before deciding whether to call.“I want to make a payment.”Value demandThis is a legitimate customer task.“Your payment link does not work.”Failure demandA broken process has created contact.“Where do I find the payment link?”Avoidable demandThe link may be too hard to find or not sent at the right point.
Why contact centres often miss the difference
Most contact-centre reporting does not show value demand, failure demand and avoidable demand clearly.
It shows things like:
Call volume
Chat volume
Email volume
Average handling time
Abandonment
Service level
Wrap codes
Queue names
Transfer rates
First contact resolution
Customer satisfaction
These are useful operational measures, but they do not always explain why customers are contacting you.
A report might show that “refunds” is one of your biggest contact reasons.
But that does not tell you whether customers are:
Requesting a refund for the first time
Chasing a refund
Asking how long refunds take
Complaining that a refund was wrong
Calling because the online refund form failed
Repeating information they have already submitted
Checking whether they are eligible
Responding to unclear wording in an email
Each of those contacts points to a different problem and a different solution.
If you only look at the category “refunds”, you may decide to add more agents, create a refund chatbot or write a new knowledge article.
But if most refund contacts are actually customers chasing late payments, the real fix is not more capacity in the contact centre.
The fix is to improve the refund process, set clearer expectations and send proactive updates.
Why this matters for AI and automation
This distinction becomes even more important when organisations introduce AI, chatbots, voicebots or digital self-service.
Automation can be useful when it is applied to the right type of demand.
It can help customers complete simple value-demand tasks. It can answer straightforward questions. It can provide updates. It can route customers more accurately. It can reduce waiting time.
But automation can also hide demand rather than remove it.
If a customer is contacting you because the process has failed, a chatbot may simply become another frustrating step before they reach a human.
If customers are confused because your policy is unclear, an AI assistant may give them an answer but still leave the underlying journey broken.
If the customer has already explained the issue three times, asking them to start again with a bot is likely to make the experience worse.
Before automating demand, you need to understand it.
A useful question is:
Are we automating value demand, removing avoidable demand, or just deflecting failure demand?
That question can prevent a lot of wasted technology spend.
How to measure value, failure and avoidable demand
You do not need to start with a huge transformation programme.
Start with a practical demand review.
Take a sample of real customer contacts across your main channels. That could include calls, chats, emails, web forms, complaints and social messages.
For each contact, capture:
What did the customer want?
Why did they contact now?
Had they contacted before?
Had something gone wrong?
Could the contact have been avoided?
Which part of the journey created the contact?
What would have prevented it?
Was the customer in the right channel?
Did the agent have what they needed to resolve it?
Did the contact create more work elsewhere?
Then classify the demand as:
Value demand
Failure demand
Avoidable demand
Mixed demand
Mixed demand is important because real contacts are not always clean.
A customer may start with value demand but reveal failure demand during the conversation.
For example:
“I’d like to change my address. Also, I tried to do this online last week and it didn’t save.”
The address change is value demand.
The failed online journey is failure demand.
If you only code the call as “change of address”, you miss the improvement opportunity.
How to reduce failure demand
To reduce failure demand, look upstream.
Find the part of the journey that is creating unnecessary contact and fix the cause.
Common fixes include:
Improving first contact resolution
Reducing handoffs between teams
Making ownership clearer
Fixing broken digital journeys
Improving case notes and CRM visibility
Reducing conflicting information between channels
Improving status updates
Closing the gap between what agents promise and what the business delivers
Reviewing policies that create unnecessary customer effort
Giving agents better tools and authority to resolve issues properly
The aim is not to handle failure demand faster.
The aim is to stop creating it.
How to reduce avoidable demand
Avoidable demand is often reduced through better communication and better journey design.
Common fixes include:
Clearer website content
Better IVR wording
Proactive SMS updates
Clearer emails and letters
Better signposting between channels
Improved FAQs based on real contact reasons
Simpler forms
Better confirmation messages
Clearer timescales
Better use of callback and status tracking
More useful self-service journeys
Better chatbot escalation rules
This work often delivers quick wins because the root cause is visible once you look at demand from the customer’s point of view.
For example, if a large number of customers call to ask for a link, send the link earlier.
If customers call to check whether a repair is urgent, rewrite the guidance.
If customers call after receiving a letter, rewrite the letter.
If customers select the wrong IVR option, change the wording.
Small changes can remove a surprising amount of unnecessary contact.
The leadership challenge
The hardest part of this work is not the analysis.
It is getting the organisation to stop seeing contact volume as only a contact-centre problem.
Failure demand and avoidable demand are signals.
They tell you where the customer journey is unclear, broken, slow, disconnected or badly designed.
That means the contact centre should not just be measured on how efficiently it handles demand.
It should be used as an intelligence hub for the business.
Your agents hear the same problems every day. Your call recordings, chat transcripts, CRM notes and complaints contain the evidence. The opportunity is to turn that evidence into better journeys.
Final thought
Value demand is the work your contact centre should be there to support.
Failure demand is work the organisation has accidentally created by not getting things right.
Avoidable demand is work that could be prevented with clearer communication, better design and smarter use of channels.
Once you separate the three, you stop asking only:
“How do we handle more contacts?”
And you start asking a much better question:
“Which contacts should not need to happen in the first place?”
That is where the real opportunity sits.
Not just in lower cost.
Not just in shorter queues.
But in simpler journeys, better customer outcomes and a contact centre that has more capacity for the customers who genuinely need help.
