How Are Contact Center Shift Schedules Built?

A shift schedule isn't names spread across days. It's an attempt to match agents on the phones to contact volume every half hour. The steps, the shift types, and a simple example.

PeekAI · · Workforce Management

"Why does my shift start at 11:30 and not at 9?" Anyone who works in planning hears this. The answer is usually that 11:30 is exactly when the center needs one more agent. A shift schedule isn't names spread across days; it's an attempt to match the number of agents on the phones to contact volume all day.

The starting point: the requirement curve

Before any schedule, the planning team has a number for every half hour: how many agents must be on the phones. It comes from the volume forecast, average handle time and target service level, using formulas such as Erlang C.

These numbers form a curve that rises and falls through the day. In many centers it climbs before midday, dips at lunch, then rises again after. The schedule's goal is to keep available agents as close to that curve as possible.

Six steps

1. Calculate the requirement per interval

Agents needed on the phones in each half hour, for each day of the week.

2. Add shrinkage

Part of paid time isn't spent answering: breaks, training, coaching, absence. It's added to the requirement using the method shown in Erlang C in Plain Language.

3. Choose shift types

TypeWhen it helpsWatch out for
Fixed full shiftThe schedule's backbone; gives agents stabilityNot enough on its own to cover peaks
Staggered startsStarts every half hour or hour, following the curve as it risesNeeds careful break coordination
Part-timeCovering peak hours onlyHard to hire enough people
Evening or night shiftCenters with long hours or 24/7 serviceFair distribution among agents

4. Spread the breaks

If everyone takes a break at 12, the queue explodes at 12. Breaks are staggered across consecutive intervals and kept away from the curve's highest points. This is the step people most often miss when building a schedule by hand for the first time.

5. Compare coverage with the requirement

Put the two numbers side by side for every half hour: required and actually scheduled. A negative gap means customers wait; a large positive gap means cost with no benefit. Adjust until the gaps are small in most intervals.

6. Consider agents, and publish early

Participants in an ICMI discussion note that neglecting agent preferences drives costly turnover, and that schedules strongly affect job satisfaction and retention. So:

  • Collect preferences and leave requests before building the schedule.
  • Share unpopular shifts fairly, with a clear rotation.
  • Publish the schedule at least two weeks ahead so agents can plan their lives.

A simple example: a Sunday morning

IntervalRequired on the phonesScheduledGap
8:00 to 9:0012120
9:00 to 10:002018−2
10:00 to 11:0026260
11:00 to 12:002825−3
12:00 to 13:002224+2

Here, the fix isn't hiring three more agents. Moving two shift starts to 9:00 and pushing two breaks from 11 to 12, where there's surplus, is enough.

Common mistakes

  • Scheduling by the hour, not the half hour: hides short peaks customers feel.
  • Forgetting real shrinkage: assuming 20% when it's actually 32% means a daily shortfall.
  • Breaks during peaks: an easy loss to avoid.
  • "Fair" on paper, unfair in practice: the same people end up with the hard shifts every time.

What this means for your team

Print yesterday's required and scheduled numbers for every half hour and underline each negative gap. You'll usually find most gaps can be fixed by moving shift starts and breaks, at no extra cost.

Browse free courses

Sources and references

  1. ICMI: Contact Center Workforce Management (#ICMIchat)