Value Demand: The Demand Your Service Exists to Serve
Value demand is customer contact that the business exists to serve. The customer wants to buy, join, change, ask or get help with something, and the organisation is set up to provide it.
Its opposite is Failure Demand — contact caused by the business failing to do something, or failing to do it right, the first time.
Most of the industry's attention goes on cutting failure demand, and rightly so. But value demand is the half of the equation that decides whether your service is worth having, and it is routinely damaged by programmes designed to cut "contact" without asking which kind.
Why it matters
Value demand is where revenue, retention and loyalty are won.
It is the quote request, the new account, the change of plan and the "I need help" call. Make it hard and customers either go elsewhere or come back as failure demand.
Why it gets damaged
Contact reduction targets, hidden phone numbers and deflection-first bots rarely separate value demand from failure demand.
They cut both. The business saves on one line and quietly loses customers on another.
What this guide covers
A clear definition, how value demand differs from failure demand, and the main types you will find.
Then how to identify it in your own operation, design around it, measure it, and avoid the common mistakes.
What is Value Demand?
The term comes from management thinker John Seddon and Vanguard Consulting, who split all demand on a service organisation into two types.
Vanguard defines value demand as customer requests that are a normal part of providing a service. Failure demand is the rest: demand caused by a failure to do something, or do something right, for the customer.
✓ Value demand is
- Why the customer is here, from their point of view
- A request the service is designed to fulfil — buy, join, change, ask, get help
- Contact you would want even if everything else worked perfectly
- Often predictable in volume and type, so you can plan for it
✕ Value demand is not
- "Good calls" as opposed to difficult ones — an angry customer can be value demand
- The same as a short or simple contact
- Chasing, correcting or re-explaining something the business got wrong
- Automatically safe to deflect to a cheaper channel
Plain-English Definition
Value demand is the contact you would still get if your organisation did everything right.
A customer asking for a quote, moving house, reporting a bereavement or wanting advice on which plan suits them is value demand.
The test is simple: would this contact still exist if nothing had gone wrong? If yes, it's value demand.
Why Value Demand Matters in CX
Value demand is the work your service exists to do. Separating it from failure demand changes how you plan, measure and invest.
For CX leaders
Value demand shows what customers actually need from you, in their own words.
It is the most honest Voice of the Customer data you have, and it tells you where journeys must be easy rather than where they can be cheap.
For contact centre leaders
Value demand is the volume you should be resourced for. Failure demand is volume you should be removing.
Planning and Workforce Management built on total volume treat both as permanent, which locks the cost of failure into the budget. The WFM Hub has the planning tools to do it properly.
For service designers
Value demand tells you what each channel has to complete, end to end.
Design around it and digital channels resolve more. Design around the organisation's own categories and value demand turns into failure demand — which is why journey mapping works best as a team sport.
What the research says about the split
Source: Vanguard Consulting, "Failure Demand" (beyondcommandandcontrol.com). Figures are from Vanguard's own work with service organisations, not a sector benchmark.
Reading these numbers honestly
Treat these as context, not a target. They come from organisations Vanguard was engaged to help, so they lean toward operations with a known problem.
The useful point is the shape. If failure demand can be half your volume, value demand may be only half of what your contact centre handles — and the half that matters most.
The only figure that counts is your own, which you get by listening to real contacts. The method is set out below.
Value Demand vs Failure Demand
The two are opposite sides of the same analysis, so read them together.
Value demand tells you what customers need. Failure demand tells you where the organisation is getting in the way.
| Value demand | Failure demand | |
|---|---|---|
| Cause | The customer needs something the service provides | The business failed to do something, or do it right |
| Typical words | "I'd like to…", "Can you help me…", "I need to change…" | "I'm still waiting…", "I was told…", "This is the third time…" |
| The right response | Serve it well, in one go, in a channel that can complete it | Remove the cause upstream so it stops arriving |
| If volume rises | Often good news — more customers, more sales, more trust | Always bad news — something is breaking |
| Who owns it | The service and its front line | Usually a function outside the contact centre |
The link most people miss
Almost every piece of failure demand starts life as value demand.
A customer lodges a claim (value). The update never arrives, so they call to chase it (failure). Then they call again because the first agent couldn't see the notes (failure).
The fastest way to cut failure demand is to serve value demand properly the first time. That's why First Call Resolution matters more than Average Handling Time when you are dealing with value demand.
Read the companion guide
The causes of failure demand, a practical example of its cost and the upstream fixes that reduce it.
The Four Main Types of Value Demand
Vanguard's method is to categorise demand in the customer's words, so your own categories should come from listening, not from a template.
That said, most value demand falls into four broad groups, and each needs a different design response.
"I want to start something"
Quotes, new accounts, purchases, sign-ups and bookings.
This is revenue walking in the door. Friction here does not create failure demand so much as lost customers, who simply go to a competitor.
"I want to change something"
Moving house, updating details, changing plans, adding a product.
Usually simple and well suited to self-service — but only if the digital channel can finish the job without a follow-up call.
"I want to understand something"
Advice, product questions, "which option suits me?", explaining a first bill.
Watch this group closely. Some of it is genuine value demand, but a lot is failure demand in disguise, caused by unclear letters, websites or contracts.
"I need help with something"
Claims, faults, hardship, bereavement and life events outside the business's control.
Often emotional and complex. This is where human contact earns its cost, and where pushing customers to a bot does the most damage.
Some value demand you want more of
A rise in "start something" contacts usually means marketing is working. A rise in "help" contacts after a storm or outage means customers trust you to respond.
A contact centre judged only on falling total volume is being asked to turn away the work the business wants.
How to Identify Value Demand in Your Operation
Your disposition codes and Wrap Codes describe what the business did, not why the customer called. To find value demand you need to listen to real contacts and classify them yourself.
Sample real contacts across channels
Take a few hundred recent calls, chats, emails and messages from different days and times.
Read or listen to them in full. Reports can't tell you why someone made contact.
Write down the reason in the customer's words
"Customer called about their bill" is the business's view. "My first bill was double what I was quoted and I want to know why" is the customer's.
The second version tells you whether it's value or failure demand.
Ask the one question
Would this contact exist if the organisation had done everything right? Yes means value demand. No means failure demand.
If a contact holds both, count each part separately.
Group the value demand by type
Use the customer's own language to group it — start, change, understand, help, or whatever categories your contacts reveal.
Note the volume, channel and time pattern of each group.
Check whether each type is served in one go
For each value demand type, ask how often it is fully resolved at first contact, and which channel does it best.
Value demand that keeps needing a second contact is where your future failure demand is coming from.
Repeat it regularly
Demand changes with products, seasons and policy. A one-off study goes stale within months.
Build a lighter, regular sample into your quality or analytics routine so the split stays current. The Customer Service Hub has frameworks to support it.
Practical example: a home insurer samples 200 calls
The figures below are illustrative, to show how the classification works. They are not a benchmark.
| Reason for contact (customer's words) | Type | Calls |
|---|---|---|
| "I'd like a quote for my new place" | Value — start | 34 |
| "I'm moving, can you update my policy?" | Value — change | 28 |
| "A tree came down on my roof last night" | Value — help | 30 |
| "What does my excess actually cover?" | Value — understand | 12 |
| "Where is my claim up to?" | Failure | 40 |
| "I was promised a call back" | Failure | 22 |
| "You've charged me twice" | Failure | 18 |
| "The online form wouldn't let me lodge it" | Failure | 16 |
| Value demand / failure demand | 52% / 48% | 200 |
What the example shows
Thirty customers made a claim — classic value demand. Forty calls were customers chasing claims.
The biggest failure demand category was created by the biggest value demand category being served poorly. Fix how claims are communicated and both numbers improve.
Benefits of Designing Around Value Demand
Capacity aimed at the right work
When you know which volume is value demand, you can resource for it properly.
Failure demand becomes a reduction project rather than a permanent line in the roster.
Revenue and retention protected
Quote, sales and retention contacts stay easy to reach.
Cost-cutting stops accidentally blocking the customers who were about to spend money.
Less failure demand downstream
Value demand served in one go doesn't come back as chasing, complaints or repeat contacts.
It's the cheapest failure demand reduction available.
Better channel decisions
Each type of value demand can go to the channel that completes it best.
Simple changes suit self-service. Complex or emotional help needs a person.
Smarter forecasting
Value demand tends to follow stable, explainable patterns — seasons, campaigns, life events.
Separate it from failure demand, then model the staff it needs with the Erlang C Calculator.
A shared language with the business
"This is demand we want; this is demand we caused" is a conversation every executive understands.
It moves the contact centre from cost centre to source of insight.
Common Pitfalls with Value Demand
Setting a target to cut total contact volume
A blanket "reduce contacts by 20%" target can't tell value demand from failure demand, so teams cut whatever is easiest — often the value demand.
The fix: target failure demand reduction and value demand resolution, separately.
Deflecting value demand to channels that can't finish it
Sending a claim or a hardship request to a chatbot that can only collect details doesn't remove the contact. It delays it and adds a failure contact on top. Digital and the contact centre work best together.
The fix: only shift a value demand type once the new channel resolves it end to end.
Hiding the phone number
Burying contact details cuts calls on the dashboard. It also cuts quotes, sales and retention conversations, and pushes help requests into complaints.
The fix: make value demand easy to start in every channel, and remove failure demand at the source.
Rushing value demand to protect handle time
Value demand handled against a tight AHT target gets closed before it's resolved. It comes back as failure demand, so handle time looks good while total work grows. Look at the outliers, not just the average.
The fix: judge value demand on resolution, not speed.
Classifying from the business's point of view
"Billing enquiry" can hide a customer asking a fair question (value) or one whose bill is wrong (failure).
The fix: classify from the customer's words, not from your wrap codes or product lines.
Assuming all "how do I" contacts are value demand
If many customers ask how to read a letter or use a form, the letter or form has failed. That's failure demand dressed up as a question.
The fix: when one question shows up often, test whether something upstream is causing it.
Warning: If your contact volume is falling while sales, retention or customer satisfaction are also falling, you may be cutting value demand rather than failure demand.
Fewer contacts is only good news when the contacts you lost were ones you caused.
How to Measure Value Demand — and Know It's Working
Value demand isn't a number to push up or down. Measure whether you understand it and serve it well.
Track the value/failure split over time
Report value demand and failure demand as shares of total contact, from regular samples.
Success looks like failure demand falling while value demand holds or grows.
Measure resolution for each value demand type
For each type, how often is it resolved in one contact, in any channel?
Low resolution on a value demand type is an early warning of failure demand to come.
Watch the effort customers spend to get it done
Customer Effort Score on value demand journeys shows whether starting, changing or getting help is easy.
High effort on value demand drives customers to competitors, not just to your phone line.
Link value demand to business outcomes
Connect "start" demand to sales conversion and "help" demand to retention.
That turns value demand into a revenue conversation, which is where it belongs.
The rule
Judge failure demand by how much of it you've removed. Judge value demand by how well you've served it.
Using one measure for both — total contacts, cost per contact, average handle time — rewards the wrong behaviour on at least one of them.
Is your value demand going to competitors?
ACXPA's Peer & Competitor Benchmarking measures your sales and new-customer journeys head to head against the organisations you choose.
Frequently Asked Questions
What is value demand in simple terms?
Value demand is contact you would still get if your organisation did everything right.
It's customers wanting to buy, join, change, ask or get help — the reasons your service exists.
What is the difference between value demand and failure demand?
Value demand is caused by the customer needing something. Failure demand is caused by the organisation failing to do something, or do it right, the first time.
Serve value demand well. Remove failure demand at its source.
Who came up with the idea of value demand?
The distinction between value demand and failure demand comes from John Seddon and Vanguard Consulting, as part of their systems thinking approach to service organisations.
Should we set a target to reduce total contact volume?
No. A total volume target can't tell value demand from failure demand, so it rewards cutting both.
Set a goal to reduce failure demand and a separate one to resolve value demand well. If volume falls because failure demand fell, that's a real win.
Can value demand be automated or moved to self-service?
Yes, when the channel can complete the request end to end. Simple changes such as updating an address are good candidates.
Moving value demand to a channel that only starts the job — a bot that collects details then says "someone will be in touch" — creates failure demand.
Is a complaint value demand or failure demand?
Usually failure demand, because most complaints are caused by something the organisation got wrong.
Handling the complaint well is still important. But the lasting fix is upstream, in whatever caused it.
How do we classify a contact that is both?
Count each part. A customer who wants to add a car to their policy (value) and also asks why last month's payment failed (failure) gives you one of each.
The point is to see both patterns, not to force every contact into one box.
Is rising value demand a bad sign?
Not necessarily. More quote requests, more new customers or more people asking for help after a major event can all be signs the business is growing or trusted.
Plan for it rather than trying to suppress it.
Where to Next
Summary
Value demand is customer contact the business exists to serve: people wanting to start, change, understand or get help with something.
It is the opposite of failure demand, which is contact caused by the organisation getting something wrong.
The two need opposite responses. Failure demand should be designed out upstream. Value demand should be made easy and resolved in one go, in a channel that can actually complete it.
When value demand is served badly, it comes back as failure demand.
The biggest risk is treating all contact as cost. Targets to cut total volume, hidden phone numbers and deflection-first automation cut value demand along with failure demand.
Listen to real contacts, classify them from the customer's point of view, and judge each type of demand by the right measure.
