Skip to main content

Agent scheduling

Agent scheduling plans who works in which team (queue) and when, shows how well the plan was kept, and estimates how many agents each hour needs. Open Scheduling (/admin/scheduling) in the Calls and routing section.

  • Planning shifts needs queues:monitor (the built-in Supervisor role has it). A supervisor whose permission is limited to departments plans the teams (queues) of those departments only.
  • Adherence and Forecast read the call history and need reports:read.
  • Agents see their own coming shifts on the Agent page (/agent).

Shifts​

A shift is one agent, one team, a day and its hours (at most 16 hours; a shift that ends at an earlier hour than it starts ends the next day), an optional break (a break, lunch or training, inside the shift) and a note.

  1. Choose the week with Previous week and Next week, and a team to see only its shifts.
  2. Under Add a shift, choose the agent, the team, the day, the hours and the break, then Save.
  3. Edit and Delete in the list change or remove a shift. An agent never has two shifts at the same time: a shift that overlaps one the agent already has is refused.
  4. Copy week to next week copies the shifts of the week shown (or of the chosen team) to the next week with the same hours and breaks. Shifts that would overlap one the agent already has are skipped, so copying twice adds nothing.
  5. Export CSV downloads the week's shifts.

Every change is recorded in the change history.

Adherence​

For each agent and team with a shift in the week (up to now), the page compares the scheduled working time (the shifts minus their breaks) with the time the agent was really logged in to that team:

  • Logged in on time: logged in during scheduled working time.
  • Logged in on a break: logged in during a scheduled break.
  • Logged in outside the shift: logged in when no shift of that team was planned.
  • Adherence: logged in on time as a share of the scheduled time. Values under 80 % are highlighted.

Logins and logouts come from the queue history: the agent's own login and logout (in the apps, with the feature codes, or by a supervisor), and statuses that log agents out of their queues. An agent who never logged out counts as logged in, as the queue treats them. An agent whom the queue took out after missed calls (auto-pause) counts as logged out from that moment, so the pause does not count as adherence. The queue history also records pauses, after-call work and the return to available. Export CSV downloads the table.

Forecast​

Choose a team to see, per weekday and hour in the company's time zone:

  • the calls expected: the average of the last 4 weeks of that queue's callers at that hour;
  • the agents needed so that 80 % of calls are answered within the queue's service level target (the queue's answered within seconds), from the calls and their average handling time (Erlang C);
  • the agents scheduled at that hour next week (working, not on a break).

Hours where fewer agents are scheduled than needed are outlined. The forecast is an estimate from history: holidays, campaigns and other changes are not predicted.

API​

The same is available through the API (/api/v1/wfm/shifts, /api/v1/wfm/adherence, /api/v1/wfm/forecast, /api/v1/me/shifts); see the API reference, tag workforce.

Working with the lists​

The shift and adherence lists work like the Users list: the ... menu at the end of a shift row has Edit and Delete. Below 640 pixels wide the table turns into cards with no sideways scrolling. A list that cannot be loaded shows the reason and Try again.