Financial services contact centre staffing
Financial services contact centres operate under regulatory SLA obligations that make under-staffing a compliance risk, not just a customer experience problem. Turnella models each work type correctly and keeps the audit trail that Consumer Duty and DISP require.
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.
The financial services event calendar
Financial services contact volume is driven as much by regulatory and product events as by underlying customer need. Each event type requires a distinct forecast adjustment.
The right model for each work type
Financial services operations mix real-time queues (voice, chat) with batch-processed case work (complaints, claims). Each requires a different staffing model.
Retail banking and savings enquiries
Account enquiries, mortgage queries, card services, and fraud reporting queue as inbound voice contacts. Erlang C models the queue dynamics and gives you the exact agent count to hit your answer-rate SLA. FCA Consumer Duty requires demonstrable, documented SLA compliance.
Claims and case processing
Insurance claims, complaint investigations, and complex case work accumulate from shift to shift. These are not queues with real-time service levels — they are backlogs with SLA windows measured in days. Model as a flow: daily inflow, throughput, and target clearance time to compute FTE requirement.
Live chat and secure messaging
Online banking chat and secure messaging platforms where advisors handle 2–3 concurrent conversations. Using Erlang C for chat overstates staffing by 40–60%. The concurrency model accounts for multiple parallel sessions and gives the right agent-to-customer ratio.
Complaints and written correspondence
FCA-regulated complaints require acknowledgement within 5 business days and full resolution within 56 calendar days (8 weeks). Model each stage as a backlog: how many complaints arrive, how long each stage takes, and how many handlers are needed to avoid regulatory breach.
Consumer Duty and service level
FCA Consumer Duty (July 2023) requires firms to evidence that customers can reach them promptly and receive the help they need. This turns service level from an operational metric into a documented regulatory obligation.
A documented Erlang C model — showing the assumptions, the target, and the required headcount — provides the audit evidence that Consumer Duty MI reporting requires. Turnella stores your forecast, requirements, and assumptions per workstream.
Financial services staffing questions
How does Consumer Duty affect WFM planning?
FCA Consumer Duty (effective July 2023) requires firms to deliver good outcomes for retail customers, including that customers can contact their firm promptly and get the help they need. This means service level is no longer just an operational metric — it is a regulatory obligation. WFM plans must document the assumed SLA, the model used to compute it, and how the requirement was monitored. Erlang C provides the documented model; Turnella retains the forecast and requirements history.
How do I model FCA complaint handling staffing?
FCA DISP rules require complaints to be acknowledged within 5 business days and resolved within 8 weeks (insurance, or 15 days for payment services). Model complaint handling as a backlog with two stages: acknowledgement (fast, high volume) and investigation/resolution (slower, lower volume but high effort). Use the backlog model: daily complaint inflow + target resolution rate + SLA window = FTE requirement. When complaint inflow spikes (e.g., after a product issue or press coverage), the backlog model shows how many days your current FTE can hold the SLA before breach.
What is a typical service level target for a financial services contact centre?
Financial services contact centres typically target 80% of calls answered within 30 seconds for general service lines. Priority lines (e.g., fraud, bereavement, vulnerability) often target 80% in 20 seconds or faster. Some regulated firms have specific SLA commitments in their FCA permissions or in service agreements. The target should be modelled explicitly in Erlang C — 80/30 versus 80/20 can change your seated agent requirement by 10–15%.
How do I plan for an unforecastable event like a data breach or system outage?
Unforecastable events (cyber incident, major system failure, product recall) cannot be staffed in advance from a forecast, but you can model a plausible scenario. Build a contingency plan: if inbound volume 3×es over 48 hours, how many additional agents can be deployed? This requires knowing your cross-skilled back-office headcount, your agency relationship, and your maximum-flex standby pool. A pre-built scenario in Turnella's What-if module lets you run 'if volume is 200% of forecast, what do we need?' in seconds during the incident.
Model your SLA requirements, not just your headcount
Turnella gives you the Erlang C model, the backlog model, and the scenario comparison you need to demonstrate Consumer Duty compliance — without a six-figure enterprise WFM contract.
Related
Erlang C calculator
SLA-driven agent requirements for voice
Email / case calculator
Complaint and claims FTE modelling
Service level explained
What 80/20 means — and what to target
Shrinkage explained
Converting seated to scheduled headcount
What-if scenarios
Model contingency events in advance
CC staffing guide
End-to-end WFM planning process