ISP · Mobile · Broadband · TV

Telecom contact centre staffing

Telecom and ISP contact centres face the sharpest AHT divergence of any sector — billing queries at 5 minutes sit alongside broadband fault investigations at 25. A single blended staffing model will fail. This guide covers queue segmentation, outage surge planning, and Ofcom service obligations.

Start planning free →Erlang C calculator

The bimodal AHT problem

No sector has a wider AHT spread than telecom. When you blend billing and tech support into a single Erlang C model, the math produces a result that is wrong for both queues.

Example: blended vs. segmented staffing

Inputs

Billing calls: 200/hr, AHT 5 min
Tech calls: 100/hr, AHT 20 min
SL target: 80% in 20s

Blended model (wrong)

Blended AHT: 10 min
Total calls: 300/hr
Erlang C output: 64 agents

Segmented model (correct)

Billing (5 min): 22 agents
Tech (20 min): 36 agents
Total: 58 agents

The blended model overstates tech support need while understating billing capacity — and produces a 10% higher total headcount than necessary. Segment by AHT profile.

Telecom queue types and staffing models

Run a separate Erlang C model per skill group. Where agents are multi-skilled, sum the per-queue requirements to get total headcount — this is slightly conservative but correct.

Queue typeAHT rangeModelSL targetNotes

Billing & account queries4–6 minErlang C80% in 20sHigh volume, lower complexity; significant IVR deflection potential

Technical support — broadband15–25 minErlang C80% in 30sComplex diagnostics; often involves remote line tests; high repeat contact risk

Technical support — mobile10–18 minErlang C80% in 20sDevice settings, network coverage, SIM issues; vary by handset complexity

Sales & upgrades8–14 minErlang C80% in 20sAHT inflated by product explanation and credit checks

Complaints12–20 minErlang C90% in 20sOfcom and Ombudsman exposure; senior agents required

Engineer coordination5–8 minErlang C80% in 20sAppointment rescheduling; linked to compensation liability

Fault & outage updates2–4 minErlang C + IVRDeflect firstHigh volume, low agent value; IVR status message deflects 50%+

Telecom volume events

Network outage (major)

5–20× volume2–8 hours

IVR status message live within 5 min; callback queue; all available agents mobilised

Handset / product launch

2–5× volume2–5 days

Pre-plan 4–6 weeks ahead; temp agents trained on launch SKU; FAQ deflection on IVR

Price increase notices

1.5–3× volume1–3 weeks

Retention scripting ready; waiver authority delegated; overtime scheduled

Contract renewal window

1.3–2.0× volumeRolling peak

Longer-term planning; shift extension; blended agent pool (retentions + tech)

Billing system migration / error

2–8× volume1–7 days

IVR apology message; waiver credits pre-approved; daily management escalation

FCR is a staffing lever, not just a quality metric

Telecom typically has among the highest repeat contact rates of any sector — 25–40% of contacts are from customers who already called within the past 7 days. Every 1% improvement in FCR removes roughly 1–1.5% of total inbound volume.

Volume reduction impact

Improving FCR from 65% to 75% on a 300-calls/hour operation removes roughly 8–12% of volume — equivalent to freeing 5–8 agents that can be redeployed or not replaced on attrition.

Root cause targeting

The most impactful FCR improvements in telecom come from: giving agents access to diagnostic tools (line test results, real-time network status), and reducing transfers that break agent continuity.

Repeat contact rate tracking

Measure repeat contact rate at the individual agent level as well as team level. Agents with high repeat rates often lack system access or authority to resolve — it is a process problem, not a performance problem.

IVR deflection complements FCR

IVR deflection (automated fault status, bill-pay, usage balance) handles contacts that never need an agent. This is different from FCR — it reduces total contact volume before any queue forms.

Model the FCR impact on your headcount →

📡

Ofcom service obligations for telecom providers

Under the General Conditions of Entitlement, UK telecoms providers are required to handle complaints effectively and provide accessible customer service. Failure to meet these obligations can trigger Ofcom enforcement and compensation liability.

Automatic Compensation Scheme

Customers are entitled to automatic compensation for delayed repairs (>2 working days), missed engineer appointments, and delayed new service activation. Poor WFM that causes missed appointments has direct financial impact.

Complaint handling requirements

Providers must have an accessible complaints process. Ofcom has taken enforcement action against providers where the complaints process was hard to access or navigate — including excessive hold times.

Telecom staffing questions

How do I staff for a network outage in a telecom contact centre?

Major network outages can drive inbound volume 5–20× in minutes — faster than any workforce management plan can respond in real time. The only effective approach is a pre-documented incident response plan with automatic IVR deflection as the first line: a network status message that confirms the known fault, provides an estimated restoration time, and offers a callback or SMS update. This alone can deflect 40–60% of outage calls. The remaining volume should be triaged to a reduced-function mode: agents take names and numbers for callback rather than attempting live troubleshooting on an overloaded system.

Should I run one queue or segment by contact reason in a telecom contact centre?

Segmentation is almost always correct in telecom because the AHT difference between contact reasons is extreme. A billing query averages 4–6 minutes; a broadband fault investigation averages 18–25 minutes. Running a single blended Erlang C model creates a structural error: you will understaff tech support by a factor of 3–5× relative to billing. Run separate Erlang C models per skill group (billing, tech, sales, complaints). Where agents handle multiple skills, sum the FTE requirements — this is slightly conservative but correct for planning purposes.

What first contact resolution (FCR) rate should a telecom contact centre target?

Industry benchmarks for telecom FCR range from 60–75%, with top performers reaching 80–85%. Each 1% improvement in FCR reduces repeat contact volume by approximately 1–1.5% of total inbound volume, which directly reduces staffing requirements. Given average repeat contact rates of 25–40% in telecom, improving FCR from 65% to 75% can reduce total contact volume by 8–12%, equivalent to removing 1–2 agents per 10 in the team. The FCR calculator in Turnella models this relationship.

What are Ofcom's requirements for telecom contact centre service levels?

Ofcom's General Conditions require that residential and small business customers can access customer service easily and without unreasonable delays. The Automatic Compensation Scheme (2019) entitles customers to compensation for delayed repairs and missed engineer appointments — poor responsiveness can trigger compensation liability as well as Ofcom enforcement. Ofcom does not specify a numeric SL target for voice, but persistent poor service has been cited in enforcement actions. The industry norm is 80% of calls answered within 20 seconds for residential support.