Failure Demand: How to Find and Cut It in B2B Support

Failure demand is any contact a customer makes only because something failed them the first time, or was not done right. It is avoidable volume you created, and you are paying to handle all of it: every repeat call, every chased email, every "I still haven't heard back" is handling time you fund on top of the cost of the original failure. It pushes your cost to serve up and tells the customer, again, that dealing with you is hard.

The scale is easy to miss. In the UK, 83.2% of experiences were right first time in January 2026 (Institute of Customer Service, UKCSI). Nearly one in six was not, and a customer whose problem is not fixed the first time comes back into your queue.

Your support team feels this as volume. Tickets are up, the queue is full, and the plan is to hire another agent or buy a bigger tool. Before you spend, look at what the team is actually answering. A large part of it is not new demand; it is the same problems coming back.

Failure demand vs value demand

Value demand is the opposite: a customer coming to you for something they genuinely want, like buying more or asking about a new service.

A few examples in a B2B account:

• A customer chases an update because nobody told them what was happening.
• A customer calls again because the first answer did not fix the problem.
• A customer disputes an invoice they did not understand.
• A customer re-explains their issue to a second agent because the first one did not pass it on.

None of these should exist. Each one is work you created for yourself. The goal is not to handle them faster. It is to stop causing them.

Step 1: Tag two weeks of contacts

You do not need a new system to find failure demand. You need two weeks and a simple label.

Take every inbound contact across your channels: calls, emails, tickets, chats. Mark each one as either value demand or failure demand. If it only exists because something went wrong earlier, it is failure demand. When you are not sure, ask one question: would this contact still happen if we had done our job right the first time? If the answer is no, it is failure.

At the end of two weeks, add it up. The percentage that is failure demand is your starting number. Most teams are surprised how high it is.

Step 2: Sort the failures into causes

Now group the failure demand by what caused it. You are looking for the handful of root causes behind most of the volume. Common ones in B2B:

• Onboarding gaps: the customer was never shown how to do the thing they are now calling about.
• Silence: no proactive update, so the customer chases.
• Bad handoffs: the customer repeats themselves because context was lost between people or teams.
• Unclear admin: invoices, renewals, or changes that are confusing enough to trigger a query.

Sort your two weeks of failure contacts into groups like these. You will usually find that three or four causes drive most of the volume. Those are where the money is.

Step 3: Size what it costs

Put a number on it, using your own figures, not a borrowed example.

Take the count of failure contacts you tagged. Work out your average cost to serve one contact: agent time, plus any downstream cost like a credit or a callback. Multiply the two. That is what failure demand costs you for the period you measured. Scale it to a year.

Then split that total across the causes from Step 2. Now you can see, in money, what each cause is worth fixing. This is the number that gets a fix funded, because it is real and it is yours.

Step 4: Fix the cause, not the symptom

Take your biggest cause and remove it upstream.

If customers chase because nobody updates them, build the update into the process so it goes out before they ask. If they call because onboarding skipped a step, fix the onboarding step. If they repeat themselves after a handoff, fix what gets passed between teams. The test is simple: after the change, that contact should not happen at all, not happen faster.

Do this one cause at a time. Change it, then watch whether that group of contacts drops. If it does, the cause was right and the volume is gone for good.

Step 5: Track the repeat contact rate

Keep one number visible: the share of contacts that are failure demand, or the repeat contact rate. Re-tag a sample every month or two. If your fixes are working, the number falls, and your cost to serve falls with it. If it does not move, you fixed a symptom, not a cause, so go back to Step 4.

This is the same logic behind cost to serve: you cannot lower the cost of serving customers until you stop creating work you should never have had.

What to do next

Run the two-week tag this month. Get your failure demand percentage and your top three causes. That alone will tell you where your support cost is really going.

Fixing the cause is the harder part, and it usually sits outside the support team, in onboarding, communication, or handoffs. That is the work we do: find the problem, build the fix, and stay until the number moves.