What is Workforce Management and why it matters now

Workforce Management (WFM) forecasts demand, schedules people, and steers the day so customers reach capable agents quickly at a sustainable cost. WFM protects speed, quality, and people outcomes under uncertainty. Queueing science shows wait time rises sharply as utilisation nears full capacity and as variability increases. This nonlinearity is why small misses in forecast, adherence, or handle time create large swings in wait and abandon.¹ WFM converts variability into reliable access by pairing sound forecasts with realistic shrinkage, disciplined scheduling, and real-time intraday control. Industry bodies underline that adherence and conformance are independent levers that turn a plan into performance.²

How a modern WFM system works end to end

Leaders run WFM as a loop. Analysts forecast volume and handle time by interval. Planners translate volume into staffing using Erlang-based or simulation models and add shrinkage for leave, training, and meetings.³ Schedulers build shifts and assign skills and channels. Team leaders coach adherence and quality while intraday teams flex breaks, move people between queues, and offer callbacks to flatten peaks. Research on callback options shows they reduce abandonment and lower perceived wait when offered at the right thresholds.⁴ Observability closes the loop with service level, occupancy, abandon rate, and first contact resolution so leaders refine inputs next cycle. Good WFM looks like an operating rhythm, not a spreadsheet.

What should your forecast include

Forecasters model arrivals, handle time, and arrival patterns by interval. They remove one-off spikes, capture seasonality, and join marketing calendars and outage logs. Practitioners use multiple methods such as exponential smoothing and regression with promotions or bill cycles as regressors, then blend models. Schedulers apply talk, hold, and after call work to produce average handle time. Australian operations guides highlight that ACW often hides the biggest reducible minutes and that prefilled context and tighter wrap codes cut it without rushing calls.⁵ Forecast error should be tracked by interval because intraday misses break service level even when day totals look fine.³

How to translate demand into staffing

Analysts convert interval demand into required staff using Erlang C or simulation. Erlang C assumes Poisson arrivals and exponential service times; it is accurate enough for single-skill queues and remains the industry baseline for staffing and expected delay.³ For mixed skills and channels, simulation or multi-skill solvers produce better fits. Queueing results warn that wait time escalates when utilisation approaches one and when variation rises, so operations should set safe occupancy targets that leave headroom in peaks.¹ These targets keep service level stable and people sustainable.

What is shrinkage and how to set it

Managers measure shrinkage as the share of paid time not available to take contacts. Typical categories include leave, training, coaching, meetings, system issues, and unplanned absence. WFM best practices recommend building shrinkage bottoms-up by team and by month and separating planned and unplanned components so planners hedge correctly.³ Leaders should publish shrinkage assumptions, test them against reality, and adjust schedules and hiring plans when drift appears. Honest shrinkage prevents the recurring pattern where service level misses push overtime and burnout.

How to schedule for multi-skill and omnichannel

Schedulers align skills to intent and channel. Skill-only routing creates long queues for some intents and idle time for others. Intent-based routing trims transfers and raises first contact resolution by sending customers to the first capable resolver.⁶ Schedulers use shift templates that match arrival patterns and add protected coaching windows so performance does not trade off against access. Digital and messaging require concurrency rules and handling limits. Leaders should avoid overpacking concurrency because it raises cognitive load and reduces quality. Publish concurrency caps by channel and enforce them in the WFM tool.

How adherence and conformance protect the plan

Adherence measures whether people are in the right state at the right time. Conformance measures whether people worked the total scheduled time. Workforce experts teach the “power of one” effect so each person sees how their behaviour moves service level and wait time.² Leaders coach adherence as a service and wellbeing tool, not as surveillance. Real-time dashboards and simple alerts for late logins, overlong lunches, or early wrap keep the plan intact. Coaching improves effective staffing without adding headcount, which makes adherence one of the cheapest levers in WFM.²

What intraday management should do every hour

Intraday teams scan interval performance and act early. They move breaks, offer scheduled or virtual-hold callbacks when predicted wait breaches thresholds, and shift capable agents between queues. Callback options transform congested inbound work into paced outbound work and reduce abandonment without inflating staff.⁴ Intraday managers also monitor handle-time spikes, login failures, and knowledge or policy changes that affect speed and quality. A short stand-up each hour keeps planners, supervisors, and incident owners aligned on actions and expected recovery.

How to balance occupancy and wellbeing

Occupancy expresses how much time agents spend handling work. High occupancy looks efficient but removes resilience and increases burnout risk. Queueing theory and practice both support a safe band instead of a hard maximum.¹ Managers should vary occupancy targets by workload and daypart and should model the effect of new channels or campaigns on the occupancy band before launch. WFM plans should include recovery time after sustained peaks and should ringfence coaching and learning to prevent long-term performance drift.

Which metrics prove WFM is working

WFM needs a paired scorecard. Leading indicators include forecast error by interval, schedule fit, adherence, occupancy, and handle-time stability. Lagging outcomes include service level, average speed of answer, abandon rate, first contact resolution, and cost per contact. ICMI emphasises that FCR belongs in the WFM conversation because poor routing and broken handoffs create repeat volume that any schedule will struggle to absorb.⁷ Leaders should add callback take-up and time-in-queue distribution to confirm that relief valves are working at peaks. This scorecard keeps the team steering against both reliability and customer outcomes.

What risks undermine WFM and how to avoid them

Three risks recur. First, organisations plan to an average. Kingman’s result shows that variation drives wait, so planners must track variance and design buffers, not rely on mean loads.¹ Second, teams over-pursue average handle time and damage first contact resolution. Industry guidance urges modernising metrics toward effectiveness and friction removal, not shaving seconds.⁷ Third, leaders underfund shrinkage and then blame agents when service level misses. WFM leaders must publish shrinkage assumptions and align them to reality or schedules will never land.³ Add a change freeze and a change log so last-minute meetings do not silently erode plan quality.

How to implement WFM in 60 days without drama

Executives deliver WFM in three phases. Phase one baselines 90 days of arrivals, handle time, service level, abandon, occupancy, adherence, and shrinkage by team. Phase two selects a solver, sets shrinkage and occupancy targets, and publishes shift templates and coaching windows. Phase three launches an intraday playbook with callback thresholds, break-move rules, and cross-queue moves. Research and practitioner sources agree that callbacks at defined thresholds, realistic shrinkage, and adherence coaching move service and cost without adding staff.² ⁴ ³ Publish a weekly one-pager that lists forecast error, adherence, callback take-up, and service outcomes to keep focus tight.

What technology belongs in your WFM stack

Leaders combine a forecasting and scheduling engine with real-time adherence, intraday automation, and reporting. Mature stacks integrate CCaaS data, quality, and knowledge systems so schedule changes reflect reality and so planners see the effect of policy or knowledge changes on handle time. Vendors and standards bodies point to ISO 18295 for contact centre requirements that touch people, processes, and technology governance.⁸ The right stack supports intent-based routing, callback orchestration, and cross-channel schedules so customers experience continuity, not silos.

FAQ

What is the fastest lever to stabilise service levels this quarter?
Offer virtual hold or scheduled callbacks when predicted wait exceeds a threshold and coach schedule adherence with real-time views. Both smooth peaks without new hires.² ⁴

How accurate should our forecast be?
Track error by interval. Aim for single-digit percentage error on top queues intraday. Day-level accuracy can hide intraday misses that break service level.³

What occupancy should we target?
Set a safe band that leaves headroom, then tune by hour and by queue. Queueing theory shows wait time rises sharply as utilisation nears one, so avoid running near saturation.¹

How do we decide shrinkage?
Build it bottoms-up by team with planned and unplanned components. Publish assumptions and reconcile them monthly to protect the plan.³

Does chasing AHT hurt FCR?
Yes when pursued in isolation. Use FCR and repeat-within-window as guardrails. Resolve on first contact even if average handle time rises slightly.⁷

When is Erlang C enough and when do we need simulation?
Use Erlang C for single-skill, single-channel queues. Use simulation or multi-skill models when skills overlap, concurrency exists, or arrival assumptions break.³

Sources

1. Kingman’s formula — Wikipedia contributors, 2025, Wikipedia. https://en.wikipedia.org/wiki/Kingman%27s_formula

2. Schedule Adherence: Have Your Cake and Eat It, Too — ICMI, 2016, ICMI.com. https://www.icmi.com/resources/2016/schedule-adherence-have-your-cake-and-eat-it-too

3. Workforce Management Best Practices — NICE, 2024, NICE.com. https://www.nice.com/resources/workforce-management-best-practices

4. Optimal Scheduling in Call Centers with a Callback Option — Benoît Legros, 2016, European Journal of Operational Research. https://www.sciencedirect.com/science/article/abs/pii/S0166531615000930

5. After Call Work: Tips and Tactics — ACXPA, 2024, ACXPA.com.au. https://acxpa.com.au/glossary/after-call-work/

6. Intent-based Routing in the Contact Center — Genesys, 2024, Genesys Blog. https://www.genesys.com/blog/post/intent-based-routing

7. First Contact Resolution: Definition and Approach — ICMI, 2008, ICMI Resource. https://www.icmi.com/files/ICMI/members/ccmr/ccmr2008/ccmr03/SI00026.pdf

8. ISO 18295 — Customer Contact Centres (Parts 1 & 2) — International Organization for Standardization, 2017, ISO. https://www.iso.org/standard/63167.html

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.