Contact center

Workforce Management for Contact Centers: Forecast to Roster

A plain guide to contact centre workforce management: forecasting volume, calculating staffing, building rosters, tracking adherence and adjusting live.

Call editorial team · Published · 5 min read

Calls do not arrive evenly. They bunch up at opening, after lunch and after a marketing message or an outage. A team that is perfectly staffed on average can be overwhelmed at ten and idle at three. Workforce management (WFM) is the discipline of putting the right number of people on the phones at the right times without wearing them out or wasting their time.

A planner reviewing a staffing schedule on a screen in a contact centre office
Illustrative image

You do not need a large organisation or a specialist system to benefit. Even a team of ten can use the same ideas with a spreadsheet and a clear head. This guide walks through the five stages of the cycle, the maths behind staffing, and the human side that makes rosters work. It ends with the matching screens in Call.

The five-stage cycle

The WFM cycle

  1. ForecastEstimate how many calls will arrive in each half hour.
  2. CalculateTurn volume and handle time into the people needed.
  3. RosterBuild shifts that cover the need and respect people's limits.
  4. Manage the dayCompare reality with plan and adjust.
  5. ReviewLearn from the gaps and improve the next forecast.

Each stage depends on the one before. A weak forecast gives a weak roster; a good roster is wasted if nobody watches adherence. The sections below take them in turn.

Forecasting call volume

The best predictor of next Monday's calls is previous Mondays. Start with history, in half-hour intervals, and look for patterns by hour, weekday and season. Then add what history cannot know: campaigns, price changes, billing runs, school terms, bank holidays and product launches.

Accept that forecasts are wrong. The goal is not perfection but a useful range, and the habit of comparing forecast to actual every week so it improves. Forecasting Call Volume covers methods in more depth.

Calculating the staff you need

Once you know how many calls to expect, you need three more inputs: how long each call takes including wrap-up, the service level you want to reach, and the share of time staff are not available. A standard approach, the Erlang C model, combines them into the number of agents needed to meet a target such as answering most calls within a given time. Erlang C Explained describes it without the mathematics.

Shrinkage

The number from the calculation is the number of people who must be on the phones. Real people take breaks, attend training, are ill or take leave. The share of paid time lost to such things is called shrinkage. To get the number you must roster, divide the required staff by the share of time staff are available. If you skip this step, your team will always be a little short, and the shortage will fall on callers.

What to include in shrinkage

  • Breaks and mealsFixed and predictable, so plan them.
  • Training and meetingsSchedule them in quiet intervals.
  • Absence and leaveUse averages from past months, and add known leave.
  • System downtimeSmall but real; track it.

Where the numbers are only estimates

A staffing calculator gives a planning estimate, not a promise. Real calls vary, people differ in speed and some callers hang up. Use the result as a starting point, then watch the actual service level and adjust the model. Compare the options, for example one more agent against the service level it would buy, and choose with cost in mind.

Building the roster

The roster turns the requirement into shifts. This is where maths meets people. A roster that covers every interval on paper but ignores fairness will fail within weeks.

Skills matter as much as headcount. A queue can have enough people on shift and still have nobody qualified. Check cover by skill, not only by number. Shift Planning Basics and Time-Off Fairness go into rostering practice.

Managing the day

The day will never match the plan. The question is how quickly you notice and what you do. Three common situations need different responses.

When the day differs from the plan

Calls above forecastCalls below forecast
First moveDelay breaks and training, ask others to log inUse the time for training, coaching or call-backs
If it persistsOffer overtime, move people between queuesRelease hours or swap shifts
WatchAbandoned calls and burnoutIdle time and morale
AfterwardsCheck the forecast for what was missedCheck for overstaffing assumptions

Adherence, how closely people follow their schedule, is the main tool. Someone away from their post during a peak hurts the queue; a few minutes of lateness repeated across a team adds up. But handle adherence with care. Treat it as a coordination signal, not as a stick. If adherence is very high while occupancy, the share of time on calls, is also very high, that is a burnout warning rather than a success.

Reviewing and improving

At the end of each week, compare forecast with actual volume, required with scheduled staff and service level with target. Ask why gaps happened. Was it the forecast, the roster, the day-to-day management or an unforeseeable event? Each answer points to a different fix. See Occupancy and Utilization and Schedule Adherence for the two measures that most often cause debate.

Weekly WFM review

  • Forecast against actual, by interval and queue
  • Required against scheduled staff, and the gaps
  • Adherence and occupancy together, not alone
  • Swaps, overtime and absences
  • Skills with no cover on any day
  • Changes to make to next week's forecast

Doing it in Call

In Call, Workforce under Calls compares the staff you need with the staff you have scheduled for a day. Choose the day, then read the tiles for intervals planned, short-staffed intervals and people scheduled. The Required vs scheduled view shows, for each half hour, the headcount the forecast needs against the people on shift, with a list of what to do about the gaps, and the roster and adherence and occupancy views below it. Rebuilding the forecast is available once the workspace has an inbound queue, since each forecast is built from that queue's call history. Administrators and managers can also plan shift shapes and sites, and use the Scenario view: enter calls per half hour, average handle time, a service target, shrinkage and cost per agent hour to see how many agents are needed and what each headcount would achieve. It uses Erlang C, so treat it as a planning estimate.

Staffing ops handles the day itself: who is out of adherence now, queues without cover, today against plan, and surplus hours. Its tabs cover cover by skill and site, shift swaps and overtime, availability preferences, attendance (late starts and early finishes) and weekly patterns. Moving people between inbound and outbound is a recommendation only; nothing is moved automatically. For what supervisors watch live, see What Contact Center Supervisors Should Monitor in Real Time.

Frequently asked questions

Do small teams need workforce management?

The principles apply at any size. A small team can use a simple weekly forecast, a basic staffing estimate and a shared roster, without specialist software.

What is shrinkage?

The share of paid time that agents are not available to take calls, because of breaks, training, meetings, leave, sickness and similar things. You add it to the staff you calculate so the roster has enough people.

How accurate does a forecast need to be?

Accurate enough to guide decisions, and improving. Compare forecast and actual every week and look for patterns in the errors rather than aiming for perfection.

What is the difference between adherence and occupancy?

Adherence measures whether people follow their schedule. Occupancy measures how much of their available time is spent on calls and wrap-up. Both are needed, and very high levels of both together can signal overwork.

How do I handle a sudden surge in calls?

Delay breaks and training, ask people on other work to log in, move agents between queues, and offer call-backs. Afterwards, find the cause and update your plan.

Is overtime a good fix for understaffing?

It helps in the short run, but regular overtime leads to tired agents and higher turnover. If you rely on it, the underlying roster or headcount probably needs to change.

Compare required and scheduled staff in Call's Workforce screen

In the demo console you can try incoming calls in a simulation.

Related guides