Contact centre routing strategy and WFM
Every routing decision creates a staffing consequence. Skills-based routing breaks a single Erlang model into sub-queues. Priority routing makes standard contacts residual. Overflow routing transfers a shortfall rather than eliminating it. The WFM function must be involved in routing decisions before they are made.
Four routing strategies and their WFM impact
Skills-based routing (SBR)
How it works
Contacts are routed to agents based on skill or product qualification. A mortgage enquiry routes only to mortgage-qualified agents. A Spanish-language contact routes only to Spanish-speaking agents.
Staffing calculation impact
Cannot use a single Erlang C calculation for total volume. Each skill group must be staffed as a semi-independent queue with its own Erlang model. The combined staffing requirement is higher than a fully blended equivalent because smaller pools are less efficient. Staffing calculations must account for multi-skill agents who bridge queues — their contribution must be allocated across the queues they serve.
Schedule impact
Schedules must ensure each skill group is covered at every interval. An agent scheduled to start at 09:00 who is the only Spanish-qualified agent on the early shift creates a single-point-of-failure risk. Skill coverage must be checked at interval level, not just total headcount level.
Intraday management impact
Queue imbalances manifest differently: excess capacity in the general queue cannot automatically relieve a shortage in the specialist queue without routing configuration changes. Intraday managers must have defined protocols for rebalancing skill availability in real time — pulling multi-skill agents between queues — and the routing system must be configured to enable it.
Priority routing
How it works
Contacts from high-value customers, vulnerable customers, or critical contact types are queued ahead of standard contacts. Standard contacts wait longer in exchange for priority contacts receiving faster service.
Staffing calculation impact
Total headcount requirement is driven by the priority contact volume against the priority SL target. Standard contacts receive whatever capacity remains after priority demand is served. The WFM function must confirm that enough agents are staffed to serve priority demand at target SL before assessing what SL standard contacts will receive — standard contacts are a residual, not a first-order constraint.
Schedule impact
No specific scheduling change beyond the staffing requirement driven by priority SL targets. However, if standard contacts have a contractual SL target (e.g. outsourced BPO environment), the schedule must be built to serve both priority and standard SL targets simultaneously — which requires a more complex capacity calculation.
Intraday management impact
Priority routing failure mode: a large volume of priority contacts in a single interval can starve the standard queue entirely, producing very long wait times for standard contacts. Intraday management must monitor the standard queue position separately and escalate if the standard wait time exceeds agreed internal thresholds, even when the priority SL is being met.
Overflow routing
How it works
Contacts that have been waiting in queue for longer than a threshold (e.g. 60 seconds) are routed to a second pool of agents — either a different team or an outsource partner. Designed to prevent extreme tail-of-queue wait times in volume spikes.
Staffing calculation impact
Overflow routing does not reduce the total staffing requirement — it redistributes the shortfall from the primary team to the overflow destination. The primary team must still be staffed to handle the baseline volume; overflow handles the excess. If overflow is routinely triggered, it indicates the primary team is chronically understaffed, not that overflow routing is working as designed.
Schedule impact
The overflow destination must be staffed with available capacity at the same intervals where the primary team is most likely to overflow — which are typically the same peak intervals where the overflow destination also has its own peak demand. WFM must coordinate with the overflow destination to ensure they have capacity available when it is needed, not just that overflow routing is technically enabled.
Intraday management impact
Intraday management must monitor overflow activation rate as a leading indicator of primary-team capacity shortfall. A day where overflow is activated frequently is a day where primary staffing is below requirement — this should be documented and fed back into the short-range staffing review, not normalised as 'the overflow is working'.
Preferred-agent routing (PAR)
How it works
Returning customers are routed to the same agent who handled their previous contact, subject to that agent being available. Designed to improve continuity and CSAT for complex, relationship-sensitive contact types.
Staffing calculation impact
Preferred-agent routing creates artificial demand concentration on specific agents. If a customer always waits for their preferred agent rather than accepting any available agent, the effective capacity of the queue is reduced. The WFM staffing model must account for the proportion of contacts that will wait for a preferred agent — which increases average wait time and AHT (returning callers may be more complex) relative to a non-PAR environment.
Schedule impact
Scheduling preferred agents off the phone (training, meetings, annual leave) creates predictable customer-experience gaps if their customers call during that window. The WFM team should flag PAR agents' planned absence to the relevant team leader so that affected customers can be pre-notified or temporarily routed to a nominated backup.
Intraday management impact
Real-time adherence monitoring must distinguish between an agent who is unavailable because they are handling a contact and an agent who is effectively unavailable because all their current contacts are being held in queue awaiting their preferred agent. A high queue position against a specific agent's desk in the RTA view is a PAR signature — the intraday response is different from a general queue crisis.
Routing and WFM questions
How does skills-based routing affect Erlang C staffing calculations?
Two effects: (1) Smaller agent pools — Erlang C efficiency depends on pool size. Skills-based routing creates smaller pools for specialist contact types, requiring more agents per contact than a fully blended pool. A 50-agent blended queue is always more efficient than two 25-agent specialist queues. (2) Queue interdependency — multi-skill agents bridge queues and cannot be staffed independently using standard Erlang C. The staffing requirement for a multi-skill environment must be modelled as a connected network, not as independent queues summed together. Most WFM software handles this via simulation or multi-skill Erlang extensions. The combined staffing requirement will always exceed the sum of independent Erlang C calculations for each skill group.
Related guides
Multi-skill routing
The mechanics of skills-based routing
Erlang C explained
How the staffing model works
Intraday management
Managing routing-driven capacity imbalances
Staffing models
Erlang C vs simulation in routed environments
WFM for blended agents
Scheduling multi-skilled agents
WFM technology
WFM systems that handle routing complexity
Erlang C calculator
See the SL impact of routing-driven agent shortfalls
Multi-channel calculator
Model staffing across routed voice, chat, and email