Genesys Employee Schedule Preferences (EE10-B) for Genesys Engage cloud
- 1 Use Case Overview
- 2 Use Case Definition
- 3 Use Case Requirements
- 4 Assumptions
- 5 Related Documentation
Use Case Overview
Story and Business Context
This use case focuses on operational efficiency and employee empowerment through enabling employees to request and drive their own shift exceptions, optimizing both employee satisfaction and business operational needs. The use case features:
- The ability for an agent to enter an exception into the published schedule.
- Labor-saving as agents enter exceptions that would otherwise be entered by supervisors.
- Agent empowerment, allowing agents to enter items into their own schedules.
- Supervisor control, as customers can decide whether the agent-initiated exception is pushed directly to the master schedule or is if it requires supervisor approval prior to appearing in the schedule.
Use Case Benefits*
|Use Case Benefits||Explanation|
|Improved Employee Occupancy||Eliminate the need for the planner to process these requests|
|Improved Employee Satisfaction||Allow employees to have more say in their schedule|
|Reduced Administration Costs||Allow business users to specify the types of exceptions that be requested from employees|
Deliver the capability for an employee to enter exceptions (offline activities) into their schedule via the Workforce Management User Interface without the need to supervision or effort on the planner's behalf.
Use Case Definition
The following diagram shows the business flow of the use case:
Business Flow Description
- Base configuration complete (use case EE01, EE02, or EE26).
- In Web Agent application, user navigates to Add Exception.
- Agent selects how she wants to schedule the exception:
- Best fit/optimized
- Specific time/date
- If supervisor approval is required, the supervisor navigates to Master Schedule Changes Approval view and approves/declines the agent-initiated exception.
- Exception is visible to agents and supervisors in the master schedule.
- If the supervisor declines the request it appears as declined in the master schedule view.
Business and Distribution Logic
The following business capabilities need to be in place to allow this capability to be of benefit:
- Defined rules and decisions on which exceptions employees can use.
- Confirmation from the business on the operating procedures of such exceptions.
Use Case Requirements
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 Cloud customers running Genesys Workforce Management
PureConnect Platform Assumptions:
Supervisor has a user role allowing access to Exceptions. In Web Supervisor application > Policies > Exception Types:
- check ‘Agent-Initiated’ to enable the functionality
- enter optional start/end dates if required
- PureConnect GWFM Connector is required to utilize Genesys WFM on PureConnect
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) Additional assumptions are included in the dependency use case covers the PureConnect Platform-specific assumptions.
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.
This use case should be considered only if the business intends to allow agents to have a say in how their schedules get built.
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 are managed by Cloud Ops. Base configuration (Use Case EE01) is completed by supervisors.
- v 1.1.4