Using Call

Shift Schedules, Swaps and Availability in Call

Plan who is on the phones with Call: shift shapes, the rota, availability preferences, swaps and overtime, adherence checks and how to handle time off fairly.

Call editorial team · Published · 5 min read

A schedule is a promise to callers and to staff. To callers, it says someone will answer. To staff, it says when they work and when they do not. Break the first promise and customers wait; break the second and people leave. The craft of scheduling is balancing both with imperfect forecasts.

A manager at a desk arranging a weekly staff rota on a large wall calendar
Illustrative image

This guide covers how to plan and run schedules in Call, from shift shapes to swaps, and how to think about time off. For the theory, read Workforce Management for Contact Centers and Shift Planning Basics for Phone Teams.

Start with demand

The number of people you need depends on how many calls arrive, how long they take and how quickly you want to answer. Call's Workforce screen shows required against scheduled headcount for each half hour of a chosen day, with the gaps listed under What to do about it. Rebuild forecast builds the day's forecast from the queue's call history.

If you want to see what a headcount would achieve, open Scenario and enter calls per half hour, average handle time, the answer target, shrinkage and a cost per agent hour in your own currency. The calculator uses the Erlang C method and shows the required headcount and the result of each option. It is a planning estimate, not a promise. Erlang C Explained Without the Math Headache describes it.

Shift shapes and the rota

Most teams repeat the same shifts. A shift shape saves the pattern, for example Early from nine to six on weekdays, so you do not retype it every week.

From shape to rota

  1. Create the shapeOn Workforce, scroll to Shift shapes. Enter a name, start and end times and the days.
  2. Save the shapePress Save shape.
  3. Put it on the rotaChoose the shape, the From and To dates and the people in Who.
  4. ApplyPress Apply. The message reports how many shifts were created and how many days were already rostered.

New shifts are created as drafts, and each gets a standard sixty-minute break that cannot be changed on this screen. Record where people work and in which time zone under Sites, so shift times are read correctly in each place; this matters for teams across regions. See Running a Contact Center Across Several Sites.

Availability preferences

People have lives. If planners know when someone would rather work, would rather avoid working, or cannot work, they can roster better and lose fewer shifts to last-minute swaps. On Staffing ops, the Availability tab lets each person choose a day, from and to times and a preference: I would prefer these hours, I would rather avoid these hours, or I cannot work these hours.

Be open about the rules. If preferences are weighed fairly and sometimes lose to demand, say so. Staff who understand the trade-off are far more willing to accept it.

Swaps and overtime

On the Swaps and overtime tab, a shift put on the board can be claimed by a colleague, and the claim waits for a manager's approval. Admins and managers press Approve or Reject. A claim is checked again at approval, so conditions that changed in the meantime are caught. Under Overtime, a person can press Take it on an open offer; a pill shows how many slots are taken.

Handling time off fairly

The workforce screens described here cover shifts, availability, swaps and overtime. Time off is best handled with a clear written process alongside them. Whatever tool records the leave, the principle is the same: decide the rules in advance, apply them equally and plan the schedule around approved leave rather than the other way round.

Fair and unfair time-off habits

FairUnfair
RulesWritten, shared, applied to everyoneDecided case by case
TimingA clear deadline for peak periodsFirst come first served, unannounced
CoverLimits per day known in advanceRefusals explained after the fact
RecordOne shared placeMessages and verbal promises

Our guide Handling Time-Off Requests Fairly goes deeper, and Handling Seasonal Call Peaks shows how to plan leave around busy periods.

Common scheduling mistakes

Most scheduling pain comes from a short list of avoidable mistakes. The first is planning for the average day. Calls cluster, so averages hide the half hours where callers actually wait. Plan to the shape of the day, which is why the screen works by half hour. The second is ignoring shrinkage, the time agents are paid but not available for calls because of breaks, training, meetings and absence. The Scenario calculator asks for it for a reason.

A simple remedy is a short weekly review: look at where the plan and reality disagreed, ask why, and change one thing. Over a few weeks the forecasts improve and the arguments about the rota shrink.

Teams, skills and cover

A queue can have plenty of people and still have nobody to answer it, if the people lack the skill the queue asks for. Queues route on skills, so a skill nobody has is a queue with nobody in it. Under Team and Roles, admins can group people into teams with a supervisor and record each person's skills. Staffing ops then shows queues without cover, so you can spot a gap before callers do.

Keep the skills list short and meaningful, such as support, billing or a language, and review it when people join, leave or train. When planning leave, check skills as well as headcount: two people away on the same day may remove the only two who speak a particular language.

Running the day against the plan

Staffing ops, in Calls, is the day-to-day screen. Read the tiles first: Out of adherence now, Queues without cover, Today vs plan and Surplus hours. The Today tab lists each person on shift whose status does not match, with a reason, and compares the day's calls with the forecast. It suggests moves between inbound and outbound; nothing is moved automatically. People are flagged only after a few minutes' grace. Attendance, for admins and managers, shows late starts and early finishes measured from activity, not self-report.

High adherence together with high occupancy is a burnout signal, so do not chase one number. See Schedule Adherence: What It Measures and What It Doesn't and Agent Occupancy vs Utilization.

Weekly scheduling routine

  • Review last week's required against scheduled hours.
  • Check availability preferences and swap requests.
  • Apply shift shapes for the coming weeks and review drafts.
  • Plan approved leave into the rota.
  • Look at adherence and attendance with curiosity, not suspicion.
  • Tell the team what changed and why.

Frequently asked questions

What is a shift shape?

It is a saved shift pattern, such as a name, start and end times and days, that you can apply to chosen people and dates to create shifts quickly.

Are new shifts final?

No. Shifts created from a shape are drafts. Each gets a standard sixty-minute break that cannot be changed on that screen.

What does the availability tab do?

People record hours they prefer, would rather avoid or cannot work. Planners weigh preferences where cover allows, but they are not promises.

How do shift swaps work?

A shift put on the board can be claimed by a colleague, and a manager approves or rejects the claim. The claim is checked again at approval.

Does Call forecast demand?

The Workforce screen can build a day's forecast from a queue's call history, and the Scenario calculator estimates headcount with Erlang C. Both are planning aids, not promises.

Where are time-off requests handled?

This guide describes shifts, availability, swaps and overtime. Keep a clear written time-off process and plan approved leave into the rota.

Plan shifts and swaps with the workforce screens in Call

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

Related guides