WFM (Workforce Management)
The planning discipline of matching the number of agents on shift to the volume of work arriving, interval by interval.
Demand changes by interval or day and the team needs to connect forecasts, staffing, schedules, and live control.
A planner forecasts arrivals, applies workload and shrinkage, schedules coverage, then records why the live day differed.
Calling schedule administration WFM while forecast error, service promises, and intraday decisions remain unowned.
Scheduled agents = Erlang staffing requirement / (1 - shrinkage %)WFM is the loop that decides how many people you need and when. It forecasts contact volume from history, converts that forecast into a staffing requirement (usually through an Erlang model that accounts for the randomness of arrivals), builds schedules that cover the requirement, and then tracks in real time whether agents are actually where the plan says they should be. Voice and live chat typically plan in 15- or 30-minute intervals, because averaging across a day hides the peaks that break your service level.\n\nThe step teams forget is that you can't schedule only the raw agent count the forecast asks for. Agents are paid but unavailable for a large slice of their shift — breaks, training, meetings, sick time — and that gap, called shrinkage, inflates every requirement. Miss it and you are understaffed by exactly the shrinkage percentage you ignored.\n\nWhat it hides: WFM's own scorecard can look pristine while the customer's experience is not. Schedule adherence measures whether agents followed the plan, never whether the plan was right — a confident forecast that runs systematically 15% low produces perfectly adherent, chronically understaffed intervals. And squeezing occupancy toward 100% to hit a cost target quietly buys longer handle times and burnout, which surface two quarters later as attrition rather than on any WFM dashboard.