Genesys Shift Bidding (EE11) for Genesys Engage cloud
What's the challenge?
As millennials make up more of your workforce, they want more control in their lives and a way to easily influence their schedules. Managers want to reduce the time it takes to manage this process as long as the contact center runs efficiently.
What's the solution?
Supervisors manage specific employees who can choose shifts or schedule they want while managing the operation of the contact center.
- 1 What's the challenge?
- 2 What's the solution?
- 3 Use Case Overview
- 4 Use Case Definition
- 5 User Interface & Reporting
- 6 Assumptions
- 7 Related Documentation
Use Case Overview
Story and Business Context
This use case focuses on operational efficiency and employee empowerment through enabling the employee shift bidding process. In this process, planners build employee profiles rather than individual employee schedules. Once schedules are created, the employees are asked to populate their individual profiles with their preferred shift combinations.
Contrary to the use of rotating patterns and agent shift preferences, Workforce Management Schedule Bidding allows supervisors to build schedules based on the best coverage available within the pre-defined business rules, constraints, and labor laws. The supervisor controls which agents can bid on schedules and the dates available for bidding, allowing for complete operational control.
Use Case Benefits*
|Use Case Benefits||Explanation|
|Improved Employee Satisfaction||Empower employees by allowing them to self-manage their schedules against pre-determined profiles that correspond with their contractual and shift obligations. Allow employees to select profile schedules based on their personal preferences|
|Reduced Administration Costs||Allow workforce planners to build employee profiles based on operational requirements to assist with overall scheduling needs. Reduce operational planning time by decreasing effort associated with approval and management of schedule requests|
|Reduced Penalties and Fines||Generate ideal schedules whilst adhering to business rules and labor laws|
Provides the capability for workforce planning teams to generate schedules based on profiles of their configured employees. Once generated, these profiles can be pushed to the employee for preference selection.
Use Case Definition
The following diagram shows the business flow of the use case:
Business Flow Description
- Base Configuration Complete (Use Case EE01).
- Supervisor creates Profiles in the WFM Contracts.
- Supervisor assigns skills to the profiles related to real agent skill sets/WFM activities.
- Supervisor creates a Bidding schedule scenario selecting Profile Agents.
- Supervisor builds schedule containing Profile Agents for optimum coverage.
- Supervisor selects which agents can bid on the schedule and enters open/close times for the Bidding period.
- The Profile Schedules are now available for agents to bid on.
- Agents enter values associated with the schedules they most / least want to work.
- The Bidding time expires, and agents can no longer bid on schedules.
- Supervisor can optionally assign a real agent to a profile schedule.
- Supervisor auto-assigns agents to schedules.
- Supervisor can optionally activate Seniority and/or Rank.
- Supervisor publishes Schedule to Master.
- Supervisor can run Schedule Bidding Report.
Business and Distribution Logic
The ability to create profiles relies on the underlying contract and shift configuration configured for each business unit, site, team, and employee.
Bidding is available for one-week schedules, allowing agents to select a group of shifts over a given period.
The supervisor user role has the following access:
- WFM Policies > Contracts > Profiles
- WFM Configuration > Agents > Activities & Skills
- WFM Schedules > full access
Contract Profiles are created with the appropriate skill assigned to provide optimum coverage and relation to real agents.
User Interface & Reporting
Customer Interface Requirements
Genesys WFM Web Supervisor is a browser-based UI that requires a Java applet. Access control for specific roles (such as Planners, Supervisors, Forecasters, and Schedulers) is handled via User Security configuration. See Supported Operating Environment Guide for specific browser support.
Agent Desktop Requirements
Agents access the WFM Web Agent UI with a supported browser. There is no Java in this UI. See Supported Operating Environment Guide for specific browser support.
The Genesys Workforce Management product contains a number of out-of-the-box historical reporting elements. Details can be found in the Workforce Management Administrator Guide.
Assumptions for PureConnect customers running Genesys Workforce Management
PureConnect Platform Assumptions:
The dependency use case covers the PureConnect Platform-specific assumptions.
Please be advised that Genesys Back office Scheduling (EE26) is currently not a dependency for this use case for PureConnect. The prerequisites for this use case on PureConnect are Genesys Workforce Management for Voice (EE01) and Genesys Omnichannel Workforce Scheduling (EE02)
- PureConnect GWFM Connector is required to utilize Genesys WFM on PureConnect
The customer has the requirement or desire to use this element of advanced WFM. The Inbound Voice use case is a pre-requisite of the base WFM package, including the definition of Queues, Stats, Agents & Skills. Because the WFM Web Supervisor uses Java, both JRE and Tomcat are requirements. See Supported Operating Environment Guide for specific versions.
Base WFM configuration completed for skills and profiles.
All required, alternate, and optional use cases are listed here, as well as any exceptions.
|All of the following required:||At least one of the following required:||Optional||Exceptions|
- WFM Application settings enabled for Bidding: WFM Web > AgentBidding\AllowAccess=true.
- Supervisor builds profile schedules.
- Agents enter bids using Web Agent application.
- Supervisor controls the bidding process using seniority, rank, or both.
- WFM Application settings managed by Cloud Ops.
- Remaining assumptions are the same as for Premise.
- v 1.1.3