Insurance contact centre staffing
Insurance contact centres face the full spectrum of WFM complexity: multi-AHT queues across claims, renewals, and billing; catastrophe volume spikes that dwarf normal peaks; and FCA Consumer Duty obligations that make under-staffing a regulatory risk, not just an operational one.
Note on regulatory requirements
This guide describes FCA and related regulatory requirements as they apply to regulated contact centres in Great Britain. Regulatory obligations vary by authorisation type, business model, and sector. Always verify the requirements applicable to your firm with your compliance team or legal counsel before changing regulated processes. This guide is for operational context, not legal advice.
Last reviewed: 16 June 2026.
Why insurance staffing is different
Most contact centres deal with predictable, gradual volume variation. Insurance centres deal with catastrophic and sudden spikes that are structurally impossible to pre-staff without a contingency plan, combined with regulatory requirements that make sustained under-service a legal liability.
Catastrophe planning is mandatory
A major weather event can multiply inbound FNOL volume 10–15× within hours. No contact centre can maintain a standing workforce at that size — a contingency overflow plan is not optional.
AHT varies 4× across queue types
Billing queries run 3–4 minutes; claims FNOL runs 12–20 minutes. A single blended Erlang C model massively understates claims staffing needs and overstates billing capacity.
FCA Consumer Duty is a staffing obligation
Persistent poor service — high abandonment, long waits — is now directly in scope of FCA Consumer Duty. Workforce planning shortfalls that cause customer harm create regulatory exposure.
Renewal seasonality is structural
Annual policy renewals create calendar-predictable volume peaks. Unlike catastrophe events, these are plannable months in advance — the WFM team can schedule ahead.
Insurance queue types and staffing models
Run a separate Erlang C model for each queue type. Blending AHTs across claims and billing creates a structural staffing error.
Written correspondence (FCA complaints, FOS escalations) is not a queue — it is a backlog. Model it with throughput rate and target resolution time, not Erlang C.
Volume event planning
Winter storm / flood event
Activate BPO overflow; triage non-urgent calls to callback
Renewal mailing cycle
Recruit temporary agents; extend hours; reduce training time
Product recall / market event
Mass IVR message; FAQ deflection; priority queue for urgent cases
FCA / press negative coverage
Statement on IVR; escalation team; senior agent buffer
January price-increase notices
Retention scripts ready; schedule overtime; defer training
FCA Consumer Duty and staffing
Under FCA PS22/9 Consumer Duty, firms must deliver good outcomes for retail customers. The FCA's Consumer Support outcome requires that customers can reach the firm when they need to, and are not disadvantaged by poor service accessibility.
In practice, this creates a duty to maintain adequate staffing levels. A firm that chronically understaffs its contact centre — producing high abandonment rates, long hold times, or repeated failed contact attempts — is at risk of failing the Consumer Support outcome.
Consumer Support outcome
Customers can access services they need
Vulnerable customer requirement
Priority access for vulnerable customers
Foreseeable harm duty
Understaffing that causes harm is in scope
Catastrophe staffing: the three-tier model
Insurance operations should maintain a documented catastrophe staffing response with three tiers, activated in sequence as event severity becomes clear.
Tier 1 — Business as usual + flex
Volume 1–2× normalOvertime authorised; training deferred; breaks compressed; all agents on calls
Internal resource only
Tier 2 — Extended operations
Volume 2–5× normalExtended hours (06:00–22:00); cross-trained agents recalled; customer callback offered; IVR triage for non-urgent
Internal + agreed BPO overflow (pre-contracted)
Tier 3 — Catastrophe response
Volume >5× normal24/7 operation; dedicated CAT team; SLA targets formally suspended and pre-notified to regulator; mass callback queue; media message deployed
All available resource + BPO surge + mutual aid agreements
Insurance staffing questions
How do I staff for catastrophe weather events in an insurance contact centre?
Major weather events (storms, floods, freezes) can drive FNOL claims volumes 5–15× above normal within hours. The only workable approach is a tiered contingency plan: identify your 1-in-10 and 1-in-100 event volumes from historical claims data, model the staffing requirement for each tier with Erlang C, and maintain a pre-approved overflow workforce — typically a BPO or internal float pool — that can be activated within 2 hours. For a 10× spike, standard SL targets are unachievable; pre-agree a reduced target with your regulator and document the trigger criteria.
What SLA should insurance contact centres target under FCA Consumer Duty?
FCA Consumer Duty (PS22/9) does not specify a numeric SLA, but requires firms to demonstrate that their service meets the needs of retail customers and avoids causing foreseeable harm. In practice, the FCA scrutinises abandonment rates and waiting times, particularly for vulnerable customers and during claims peaks. Most insurers target 80% of calls answered within 20 seconds as a minimum, with specific vulnerable customer call queues — often priority-routed — targeting 90% within 10 seconds.
Should I use one queue or segment by call type in an insurance contact centre?
Segmenting by call type is strongly recommended when AHT differs significantly across queues. A billing query averages 3–4 minutes; a claims FNOL call averages 12–20 minutes. If you mix them in Erlang C, you get a blended AHT that overstates capacity for billing and understates it for claims. Run separate workstreams for each AHT profile. Where agents handle multiple queues, run the Erlang model per queue, then sum the FTE — the result is slightly conservative, but accurate enough for capacity planning.
How does renewal season affect insurance contact centre staffing?
Motor and home insurance renewals follow strong calendar patterns: Q4 is consistently high as annual policies renew, with secondary spikes in spring (Easter) for travel insurance. Model renewal contact volume as a multiplier over baseline: typically 1.4–2.0× in peak weeks. Identify your top 10 renewal weeks from prior-year data and build a staffing plan that covers the peak rather than the annual average — a plan sized to the average will fail badly in peak weeks.
Model your insurance contact centre in Turnella
Separate workstreams for claims, renewals, and billing. Erlang C for each queue. Catastrophe scenario modelling with what-if volume multipliers.
Related
Erlang C calculator
Agent requirements for voice queues
Shrinkage calculator
Seated to scheduled headcount
Staffing cost calculator
FTE cost and cost per contact
Capacity planning guide
Full 7-step WFM cycle
Contact centre staffing hub
All industry guides
Financial services staffing
FCA-regulated CC planning