Planning the telco contact centre — tech faults, AI deflection, churn windows

Operations · Sector guide · ~7 minute read

Telco contact-centre planning sits between three pressures: predictable demand from billing and product change, unpredictable demand from network events, and the deflection wave from voicebots and chatbots that’s been reshaping the volume baseline for five years. Plan for one, ignore the others, and the operation breaks.

Network events — the surge most plans get wrong

A regional outage takes a telco operation from baseline volume to 3–6× in under an hour. The plan that hasn’t pre-thought the response — pre-recorded IVR messaging, surge-routing rules, overtime call-out, social media response — gets overwhelmed.

The disciplined approach: a named network-event playbook with pre-agreed thresholds, automatic IVR triggers (already routinised at most large telcos), and a pre-positioned RTA who can flex shifts within minutes. The first hour decides whether the day stays manageable or spirals.

AI deflection — the baseline-shifting wave

Telco was an early heavy user of conversational AI for self-service. The result: baseline volume has dropped 15–40% in many operations, but the remaining mix is harder. Simple "what’s my balance" is gone; emotional, complex, and complaint-heavy work is left.

The planner’s implications: AHT up materially (often 20–40%); FCR down because the easy resolutions are gone; vulnerable-customer share up; quality and coaching demands higher per contact. Don’t plan the residual workforce on the pre-deflection AHT.

Churn windows and competitive cycles

Telco demand spikes around competitive cycles — competitor price changes, regulator-driven switching campaigns, contract-end notifications. The planner who reads these cycles ahead of time positions retention capacity; the one who doesn’t loses customers at exactly the moment retention could have saved them.

A specific discipline: track competitor pricing and external regulatory pressure as forecast drivers, not as marketing’s problem. The 2–6 week lead time from a competitor move to a retention call is usually enough to pre-position capacity if you’re reading the signal.

Field-tech coordination

Telco CCs sit upstream of field engineers in a way other sectors don’t. Customer calls drive engineer scheduling; engineer outcomes drive follow-up calls; coordination failures show up as repeat-contact rate.

The planner’s contribution: forecast for the chained workload (call → visit → follow-up), not just the front-end calls. The repeat-contact rate is the planning signal — if it’s drifting up, the engineer-to-CC handoff has degraded and planning needs to surface it.

Telco CC planning — three pressures, one plan Demand sources ▸ Baseline transactional (residual after AI) ▸ Network events / outages ▸ Competitive churn cycles ▸ Product / price change spikes ▸ Field-engineer follow-up volume Planning disciplines ▸ Pre-named network-event playbook ▸ AHT recalibrated post-deflection ▸ Competitive-cycle driver forecasting ▸ Retention capacity pre-positioned ▸ Chained workload (call → visit → follow-up) ▸ Repeat-contact rate as signal AI deflection didn’t make demand smaller; it made what remains harder

The telco planner’s honest brief

Read network-event risk, recalibrate AHT for the post-deflection mix, position retention capacity ahead of competitive cycles, and watch the repeat-contact rate as your field-coordination signal. Plan for the chain, not the contact.

See also