Contact centre demand management
A 10% reduction in contact volume achieved through demand management saves more money than a 10% improvement in AHT — because it removes the contact entirely rather than handling it 10% faster. Most contact centres optimise the staffing side of the equation. This guide covers the demand side.
Value demand vs. failure demand
Before reducing demand, categorise it. Every inbound contact is either value demand (the customer wanted or needed something — the contact is legitimate regardless of how efficient it is) or failure demand (the customer would not have called if the company had done something correctly the first time).
Value demand (legitimate)
Reduce by: faster self-service, better digital journeys, proactive outbound so the customer gets what they need without calling.
- ✓New product / service enquiry
- ✓Setting up a new account or service
- ✓Making a payment or order
- ✓Changing a preference or detail
- ✓Booking an appointment
- ✓Requesting a document or certificate
Failure demand (avoidable)
Reduce by: fixing the upstream cause — not by deflecting the contact to a cheaper channel. Deflecting failure demand to self-service is not demand management, it is cost-shifting.
- ✕Chasing an order that should have arrived
- ✕Asking what a letter / bill means
- ✕Re-raising an unresolved complaint
- ✕Correcting information an agent gave incorrectly
- ✕Asking for a delivery that was promised but not given
- ✕Calling because the website / app did not work
Four demand management strategies
Outbound notification: answer the question before it is asked
Proactive outbound communications reduce inbound volume by reaching the customer with information before they decide to call. The principle is simple: if you know a customer is about to receive a bill, a delivery, a renewal notice, or a status update that typically drives contacts, send the information proactively — and the majority will not call.
| Event trigger | Proactive notification | Typical contact reduction |
|---|---|---|
| Order shipped | SMS/email with tracking link and expected delivery window | 30–50% reduction in delivery-status contacts |
| Bill / statement generated | Email with bill summary and link to payment portal | 15–25% reduction in billing query contacts |
| Service disruption detected | SMS/email to affected customers with status and ETA | 40–60% reduction in outage-status contacts during incident |
| Appointment reminder (24h before) | SMS/email reminder with reschedule link | 20–35% reduction in appointment confirmation calls |
| Renewal approaching (30 days) | Email with renewal options and direct link to self-serve renewal | 10–20% reduction in renewal contacts; improves auto-renewal rate |
| Claim or case status update | Email/SMS at each status change with next step | 25–40% reduction in claim-status contacts |
Outbound notifications are only effective if the contact address is current and the message contains the specific information the customer would have called to get. A generic 'we're processing your request' message with no actionable information will not prevent a contact — it may even increase anxiety and drive a follow-up call.
Failure demand elimination: fix the upstream cause
Failure demand cannot be sustainably reduced by the contact centre team alone — it requires cross-functional action on the root cause. The contact centre's role is to identify and quantify it; the fix lies in operations, product, communications, or IT. The contact centre team that presents failure demand in financial terms (£X per year in fully-loaded contact cost) is more likely to secure the cross-functional resource needed to fix it.
- 1.Classify contacts as value vs. failure demand using a dedicated wrap code or overlay layer — not by analysing wrap codes that were never designed for this
- 2.Identify the top 3–5 failure demand drivers by volume and cost — start with the biggest categories, not the easiest to fix
- 3.Quantify the financial case: contacts × fully-loaded cost per contact = annual cost of each failure demand driver
- 4.Map the root cause to the responsible team: a billing letter that generates 15,000 contacts/month is a communications team problem, not a contact centre problem
- 5.Escalate with the financial case and a proposed root cause fix — the contact centre should not attempt to fix the upstream cause itself
- 6.Re-measure after the fix: did failure demand in that category reduce? This closes the improvement loop and validates the intervention
Self-service deflection: at the moment of intent, not as a barrier
Effective self-service deflection means making the digital resolution accessible, fast, and trustworthy so customers choose it — not making the phone number hard to find so they have no alternative. Customers who cannot find the phone number and cannot complete the self-service journey escalate to social media or email, creating demand in a less efficient channel. Self-service only reduces contact volume when it successfully resolves the issue.
IVR deflection at the point of queuing
Offer a digital resolution path when the customer is waiting: 'While you wait, you can check your balance / track your order / view your bill at [URL]. Press 1 to receive a link by SMS.' Conversion rate: 5–15% depending on the contact type.
Search-intent SEO for common contact reasons
Customers who cannot find the answer on your website will call. FAQ and help content that ranks for '[brand] + [issue]' searches intercepts demand before the customer reaches the phone number.
In-app / logged-in self-serve for account holders
If the customer has an account, most service contact types should be resolvable without calling. High-impact self-service targets: change address, update payment method, view statement, manage subscription, cancel or pause service.
Chatbot for high-volume, low-complexity contacts
Effective for status checks, FAQs, and routing. Ineffective for complex or emotionally charged contacts. Be honest about deflection rates in vendor evaluations — successful deflection (no subsequent contact) is the metric, not containment rate (customer did not press zero).
Load levelling: shift demand from peak to off-peak
Load levelling does not reduce total contact volume — it reshapes when contacts arrive to reduce peak staffing requirements. The goal is to serve the same number of customers with fewer peak-hour agents by spreading demand more evenly across the day and week.
Scheduled callback (virtual queuing)
Customer offered a callback at an agent-convenient time rather than waiting in queue. Reduces peak queue pressure and shifts contacts to off-peak slots. Abandonment drops 20–40%; customer satisfaction is equal to or better than queue wait.
Constraint: Only effective if the callback queue management system respects the WFM schedule — unmanaged callback queues can create secondary demand spikes.
Appointment booking for complex contacts
For contacts that require 20+ minutes (complex complaints, financial advice, application support), offer a scheduled appointment rather than immediate contact. Smooths advisor demand and improves resolution quality (both parties can prepare).
Constraint: Requires appointment booking system integration with the WFM schedule. Appointment no-show rate (typically 5–15%) must be planned for.
Outbound-initiated timing of proactive contacts
Outbound notifications (see Strategy 1) generate a small return-contact rate. Timing these notifications to off-peak periods shifts the return-contact demand to off-peak. A batch email sent at 8am generates peak-hour contacts; the same email sent at 2pm generates mid-afternoon contacts.
Constraint: Requires analysis of the call-back curve per notification type — time from notification to return contact varies by customer segment and contact type.
Differential pricing or incentives
Some contact centre operations use explicit pricing to shift demand — e.g. reduced-cost resolution during off-peak hours, or prioritised service for customers who book in advance. Common in utilities and financial services.
Constraint: Requires regulatory review and careful messaging — customers who feel penalised for calling during peak times are more likely to complain.
The right order of attack
Not all demand management strategies have the same return. Apply them in this order:
Eliminate failure demand
Every contact removed is a full removal — the contact doesn't arrive, isn't handled, costs nothing. ROI can be 5–10× that of efficiency improvements.
Implementation difficulty: High — requires cross-functional coordination and senior sponsorship
Outbound notification
A proactive communication that costs pence prevents a handled contact that costs £3–8. For high-volume, predictable contact drivers the ROI is strong and relatively fast to realise.
Implementation difficulty: Medium — requires CRM data quality, contact permission, and message design
Self-service deflection
Effective where the customer is genuinely willing and able to self-serve. Returns diminish as easy contacts are already self-served and remaining contacts are more complex.
Implementation difficulty: Medium — technology investment and ongoing optimisation required
Load levelling
Does not reduce total volume. Reduces peak staffing requirements, which reduces cost. Valuable but should not be confused with demand reduction.
Implementation difficulty: Medium — requires WFM system integration for appointment/callback management
Demand management questions
What is demand management in a contact centre?
Demand management is the practice of proactively reducing or reshaping inbound contact volume rather than purely staffing to absorb it. It encompasses four strategies: outbound notifications (proactive communications that answer customer questions before they call); failure demand elimination (fixing root causes of contacts that exist because something went wrong); self-service deflection (making digital resolution accessible so customers don't need to call); and load levelling (shifting demand from peak to off-peak periods). It targets the demand side of the staffing equation rather than the staffing side.
What is failure demand in a contact centre?
Failure demand is contact volume that exists only because the organisation failed to do something correctly the first time — orders not delivered, letters customers don't understand, incorrect information from previous contacts, unresolved complaints. In most contact centres 20–40% of contacts are failure demand. It was identified and named by Professor John Seddon. Eliminating failure demand requires cross-functional action — the contact centre identifies and quantifies it, but the fix lies in operations, product, communications, or IT.
Related guides
Volume forecasting
Predicting how much demand will arrive
Channel shift
Strategic migration to lower-cost channels
Customer journey
Identifying failure demand at source
IVR design guide
Self-service deflection at entry point
Volume spike management
Reacting to unplanned demand surges
Self-service deflection
Digital deflection tactics and measurement
Deflection ROI calculator
Model the staffing saving from reduced inbound demand