WFM guideCustomer experience

Customer journey in contact centres

Q: What is failure demand in a contact centre?

Failure demand is contact volume that arises because something earlier in the customer journey failed — the customer is calling not because they want to buy or need help with a complex issue, but because something went wrong that the business should have handled correctly the first time. Examples of failure demand: customers calling to chase a missing delivery that was never updated in the tracking system; customers calling to query a bill they did not receive by post due to a fulfillment error; customers calling to ask why an automated payment failed when the failure was not communicated proactively. Failure demand is distinguished from 'value demand' (contacts that customers want to make: buying, checking a policy, getting advice). Failure demand is avoidable — it can be eliminated by fixing the upstream process failure. In most contact centres, 20–40% of total contact volume is failure demand.

Q: How do billing cycles affect contact centre demand?

Billing cycles create predictable, recurring contact volume spikes. Customers who receive a bill that is higher than expected, incorrect, or difficult to understand call to query it — the volume spike arrives 3–7 days after the billing date (the time it takes for bills to be delivered, opened, read, and acted upon). For a monthly billing operation: if bills are issued on the 1st of the month, expect a contact spike from the 4th to the 8th. This spike is a known, predictable demand event that must be in the volume forecast and staffing plan. Operations that treat the post-billing spike as unpredictable and staff to their average daily volume will consistently understaff for the highest-demand days of each month. The spike magnitude depends on: bill complexity, average bill value (higher bills = more queries), and the proportion of bills with errors or unusual charges.

Contact demand is not random. Most contacts are predictable, because most contact reasons are driven by customer life-cycle events — billing cycles, product onboarding, renewal notices, and delivery events. Understanding the customer journey means understanding when contacts will arrive, why they arrive, and — critically — which arrivals represent system failure that could be eliminated rather than staffed for.

Value demand vs. failure demand

Value demand

Contacts the customer wants to make. The customer has a genuine need or question that the contact centre exists to serve. This contact cannot be eliminated — only handled efficiently.

+New customer: product information, what is covered, what is not
+Billing query: legitimate question about a complex or large bill
+Policy or eligibility check: customer needs to understand their rights
+Complaint: customer has a genuine grievance that needs resolution
+Emergency: urgent assistance required

WFM response: forecast it, staff for it, resolve it efficiently.

Failure demand

Contacts that only arise because something earlier in the customer journey failed. The contact represents upstream process failure, not customer need. This contact can be eliminated by fixing the failure — it should not just be staffed for.

−Chase a delivery that was never proactively updated in tracking
−Query an automated payment failure that was not notified by SMS/email
−Ask why the engineer did not arrive (appointment confirmation not sent)
−Repeat callback after an agent gave incorrect information
−Chase a complaint that was acknowledged but never updated

WFM response: identify, measure, escalate to operations for upstream fix. In the short term: still staff for it. In the medium term: eliminate it.

Industry context: In most contact centres, 20–40% of total contact volume is failure demand. Eliminating failure demand through upstream process improvement is the highest-ROI contact reduction initiative — it reduces volume without any channel shift investment, without IVR complexity, and without AI. The challenge is that failure demand is owned by operations functions upstream of the contact centre (logistics, billing, product, IT) who do not see the contact centre cost of their failures.

Journey-driven volume spikes

Journey event	Contact spike timing	Typical uplift vs. avg	WFM planning action
Monthly billing dispatch	Days 4–8 post billing date	40–80%	Overlay billing date on the 30-day rolling volume forecast. Staff 40–80% above average for days 4–8 post-billing. Treat as a recurring event, not an exception.
New product / service launch	Days 1–14 post-launch	80–200% above baseline for product-related contacts	Add event volume to base forecast (separate event layer). Coordinate with marketing on launch date, expected campaign reach, and typical response rate. Get the product team's contact estimate in writing.
Price increase notification	Days 3–10 post notification letter/email	100–250% for retention and cancellation contacts	Contact the billing and pricing team for the notification send date and expected volume. Add event volume layer. Plan for high AHT on retention/cancellation contacts (15–25 min vs. standard 8 min). Brief agents on retention offers in advance.
Policy/contract renewal date	2–4 weeks before renewal date (auto-renewal window)	20–60%	Identify the date range of mass renewals (e.g., all annual policies renewing in March). Staff retention and renewal skill group 20–60% above average. High AHT — renewal contacts include conversation, upsell, query, and potential complaints.
System outage / service failure	Hours 1–48 post-failure, spike then decay	150–500%+ in the first 4 hours	Cannot be forecast in advance. Requires intraday management response: re-open all dormant agents, move staff from non-real-time tasks, activate emergency IVR messaging. Test the intraday escalation playbook quarterly.
Regulatory change / customer communication	Days 5–15 post customer letter/email	50–150%	Work with compliance team on the customer notification date and content. Complexity of new regulation determines AHT impact. Brief agents in advance — agent confidence on regulatory contacts reduces escalation rate and AHT.

Identifying journey pain points

Journey pain points are points in the customer lifecycle where the process or product creates unnecessary contact. They show up in operational data before they show up in customer surveys:

Repeat contact rate by contact reason

How to identify

Match contacts by customer and contact reason within 7 days. High repeat-contact rate on a specific reason = the first contact did not resolve the issue OR the issue recurred. Separate these: (a) FCR failure (agent did not resolve) vs. (b) process failure (issue was resolved but the upstream problem recurred).

Example

A utility company finds 35% of 'billing query' contacts repeat within 5 days. Investigation reveals: 12% are FCR failures (agent gave wrong information). 23% are true failure demand (billing system re-charges after the first correction).

Time-of-day spike analysis

How to identify

A volume spike that arrives consistently 3–5 days after a known event (billing date, statement date, delivery window) is a journey-driven spike. Plot daily volume against known journey events. The lag between the event and the spike tells you the customer response window.

Example

A bank finds a consistent Monday 09:00–11:00 spike. Investigation: direct debit failures process over the weekend. Monday morning spike = customers checking why direct debit failed and the payment notification email arrives Sunday evening.

Contact reason analysis (wrap code / disposition)

How to identify

Contact reasons from ACD wrap codes show what customers are calling about. Cluster wrap codes by journey stage: new customer, in-service, billing, renewal, complaint, cancellation. Journey stages with disproportionately high contact volume relative to their customer count are pain point indicators.

Example

A telecoms company finds 28% of contacts are in the 'new customer / first 30 days' cluster, but new customers are only 8% of the customer base. 30-day contact rate 3.5× the base rate = new customer onboarding is a significant pain point.

Escalation rate by contact reason

How to identify

High escalation rate on a specific contact type indicates the contact is more complex than agent capability or empowerment can handle at first line. This may be a training issue (agent not prepared) or an empowerment issue (agent cannot resolve without manager), or a journey issue (customer arrives with a problem that requires multiple systems to fix).

Example

A financial services firm finds 40% escalation on 'payment taken in error' contacts. Investigation: the refund authorisation process requires 3 system steps that only senior agents can perform. Process simplification reduces escalation rate to 8%.

Customer journey questions

What is failure demand in a contact centre?

Contacts that only arise because something earlier in the journey failed. The customer is not calling because they want to — they are calling because a process failure created a need. Examples: chasing a missing delivery, querying an incorrect automated bill, following up on a complaint that was never updated. In most contact centres, 20–40% of contact volume is failure demand. It can be eliminated by fixing upstream processes, not by staffing for it indefinitely.

How do billing cycles affect contact centre demand?

Billing cycles create predictable recurring spikes. Bills issued on the 1st of the month generate a contact spike from the 4th–8th (time for bills to be delivered, opened, and acted upon). Uplift vs. average: 40–80% above daily average for billing-query contacts. Treat this as a known event in the forecast, not a surprise. Failure to account for post-billing spikes is one of the most common causes of recurring monthly service level failure.