Genesys Cloud workforce management explained: forecasting, scheduling, licensing

Genesys describes workforce management as the tools to forecast demand and schedule employees efficiently while giving them flexibility. It is organised in business units, management units, planning groups and staffing groups. A planning group defines a workload of one media type and one or more route paths, and a staffing group gathers agents in a business unit with similar skills, so the plan reflects how work is really routed.

Because it is part of Genesys Cloud CX rather than a separate product, it plans from the platform's own interaction history and publishes schedules straight to agents. Genesys lists voice, email, chat, callback, messaging and workitems as the media types it covers. Workitems are tasks routed to agents that do not necessarily involve a customer, which brings back-office work into the same plan as the contact centre.

Genesys offers four ways to create a short-term forecast: Automatic Best Method, Weighted Historical Index, Weighted Historical Index with source data import, and importing a forecast. Automatic Best Method is the AI-powered option, which Genesys calls its most sophisticated: it selects from more than twenty methodologies, including ARIMA, and builds an ensemble of models. Short-term forecasts run from one to six weeks, and Genesys notes the method improves with more history.

For the longer view, Genesys calculates a main forecast nightly, a year at 15-minute intervals plus weekly first- and second-year figures. It is read-only and cannot be used for scheduling. Capacity plans use an Automatic Best Method forecast to plan staff up to two years ahead, support multi-skill planning across planning and staffing groups, and allow what-if scenarios by copying a plan and changing its inputs.

Work plans set the shift types and the weekly, multi-week and weekend rules that reflect labour contracts, such as paid hours, consecutive working days and rest between shifts. Work plan rotations cycle agents through patterns week by week, and block scheduling places specific types of work at set times. Schedules can be generated automatically from the forecast to meet service goals, as long as the schedule period falls within the forecast period, or built manually.

Through the day, intraday monitoring compares what was forecast with what is happening, at 15, 30 or 60-minute intervals, for inbound work on a published, load-based schedule. Real-time adherence compares each agent's status with their scheduled activity, and historical adherence reports adherence, conformance and exceptions afterwards. Agents can submit explanations for time out of adherence, which, if approved, are taken out of the calculation.

Agents request time off against daily limits that administrators set for each management unit, and requests that meet every condition are approved automatically. Shift trades let agents swap whole shifts within a six-week window, matched on queues, languages, skills and planning groups, with automatic or manual approval. Agents can also swap shifts with the house, and can use the Genesys Tempo mobile app on iOS and Android.

Schedule bidding lets agents bid on preferred work plans, assigned by hire date or performance ranking and the slots available. Agents can also record unavailable times up to 53 weeks ahead, which workforce management treats as a hard scheduling constraint. Genesys introduced this with the Netherlands, Belgium and Luxembourg in mind, where advance availability is required, and it is useful anywhere contracts give agents a say in their hours.

Genesys documents an integration between workforce management and an external HR system that supports JSON REST APIs. It brings time-off balances from the HR system into Genesys Cloud so agents and managers see current balances, while workforce management keeps capacity limits and automatic approvals. It is configured with Architect workflows and data actions, and Genesys publishes a developer blueprint as a worked example.

That blueprint is written for BambooHR, and Genesys says other HR systems should use it as a guide. In practice the work is mapping your HR system's API to the time-off model: balances, request types and approval status. It is a short, well-defined integration, and it is the piece most organisations forget until agents start asking why their balances differ between two systems.

Plan the integration with three questions answered first: which system owns the balance, how often it changes, and what happens when the two disagree. Genesys's design keeps the HR system as the owner of balances and workforce management as the owner of capacity, which avoids double counting. Testing should cover a request approved in one system and rejected in the other, so agents are never told two different answers.

Workforce management is included in Genesys Cloud CX 3 and CX 4. For CX 1 and CX 2 organisations, Genesys offers CX 3-level workforce engagement to a subset of users through an add-on: Genesys Cloud CX 1 WEM Add-on II and Genesys Cloud CX 2 WEM Add-on I. Genesys bills an agent for the add-on when a WEM feature is used for them, such as creating a schedule, and bills users who hold WEM administrator permissions.

Whether the add-on or an upgrade to CX 3 costs less depends on how many users need it and what else they need, such as digital channels. Our cost guide's simulator compares the two at Genesys's list prices for your own user groups. QVCCS designs and implements workforce management on Genesys Cloud CX; every delivery team member holds, or is completing, Genesys Cloud certification, and we work remotely unless agreed otherwise.