BPO · Managed services · Outsourcing

Outsourced contact centre staffing

BPOs and managed service providers face the same core WFM challenge as in-house contact centres — plus client SLA reporting, multi-client floor planning, bill-to-productive ratios, and the margin impact of every staffing decision. Turnella handles all of it.

Start planning free →Multi-channel calculator

The BPO staffing and margin model

Every BPO staffing decision flows through a chain of calculations. Getting any step wrong compresses margin or causes SLA breach — both are expensive.

MetricWhere it comes from

Billable FTEContracted with client (e.g. 25 FTEs on voice)

Seated agents neededErlang C output from actual volume + AHT + SL target

Scheduled headcountSeated ÷ (1 − actual shrinkage %)

Effective FTE (after ramp)Scheduled headcount × (1 − % agents in ramp)

Cost per effective FTEBase rate × (1 + on-costs %) × contracted hours

Margin(Billable rate × billable FTE) − (cost per FTE × scheduled headcount)

Margin is the gap between what you bill and what you spend. Every point of shrinkage above your contract assumption, every agent in ramp who cannot perform at full rate, and every interval understaffed against SL eats directly into margin.

Five BPO-specific WFM challenges

Per-client SLA reporting

Create one Turnella workstream per client. Each workstream has its own SL target, AHT, volume forecast, and shrinkage assumptions. The dashboard aggregates across all clients.

Multi-client floor planning

For shared-agent floors, use blended volume and AHT. For dedicated-seat contracts, each client workstream represents one island. The multi-channel view shows total seat demand side by side.

Margin pressure from shrinkage

BPO margins compress when actual shrinkage exceeds the assumption in the contract pricing. Model shrinkage explicitly — the shrinkage calculator shows the exact number of scheduled agents per seated requirement.

Volume variability and client forecasts

Client-provided volume forecasts are often wrong. Build your own historical baseline from actual ACD data, overlay the client forecast as a volume driver, and use the what-if tool to model scenarios where volume comes in 10–20% above or below forecast.

Attrition and ramp capacity drain

BPO attrition is typically 40–80% annually. Model the ramp-up productivity loss using the attrition cost calculator. Buffer headcount by the fraction of agents always in ramp — otherwise your effective capacity is consistently below contracted FTE.

📐

Contract pricing and SLA modelling

BPO contracts typically specify: minimum FTE, service level target (e.g. 80/20), AHT assumption, and a penalty regime for SLA breach. These four numbers define your staffing floor and your margin exposure.

Model each contract with Erlang C: given the client's volume and AHT, what is the minimum seated agent count to hit 80/20? Apply your real shrinkage to get scheduled headcount. If scheduled headcount exceeds contracted FTE — you are taking on risk. If it is materially below — you have room to price sharper.

Erlang C calculator →Staffing cost calculator →Shrinkage calculator →

BPO staffing questions

How does WFM differ for a BPO vs an in-house contact centre?

A BPO operates multiple clients simultaneously, each with their own SLA targets, volume profiles, AHTs, and contractual terms. The core staffing models are the same — Erlang C for voice, concurrency for chat, backlog flow for email — but the WFM complexity multiplies with each client. A BPO must also manage seat utilisation across the floor (shared-agent vs. dedicated-seat models), bill-to-productive ratios, and the margin impact of any over- or understaffing versus the contracted FTE.

What is a bill-to-productive ratio and why does it matter?

The bill-to-productive ratio (or billable FTE to productive FTE ratio) is the relationship between what you bill the client (typically contracted FTE hours) and what your agents actually produce in productive handling time. If you bill for 10 FTEs but your actual productive handling capacity — after shrinkage — is only 7 FTEs, you are eating margin. Turnella lets you model this explicitly: enter contracted FTE, apply your actual shrinkage, and see the gap between what you bill and what you deliver.

How do I staff a shared-agent BPO operation?

Shared-agent BPO (where one agent handles contacts for multiple clients) requires a blended volume forecast and a blended AHT assumption. The Erlang C model applies at the team level, not per client. However, SLA reporting still happens per client — you need to track each client's SL separately even if the agent pool is shared. The multi-channel calculator in Turnella allows multiple workstreams with different assumptions, which approximates this structure.

How do I price a new BPO contract using a staffing model?

BPO pricing starts with a staffing model: (1) take the client's volume forecast and AHT; (2) run Erlang C to find the seated agents needed per interval to hit the contracted SL; (3) apply shrinkage to get scheduled FTE; (4) multiply scheduled FTE by your total cost per FTE (base pay + on-costs + overhead); (5) add your target margin. The result is the minimum monthly cost to deliver the service. This should be the floor on your price. Turnella's staffing cost calculator computes steps 3–4 for any volume scenario.