Genesys Shrinkage Management (EE03) 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
Forecasting and tracking shrinkage allows a business to deliver a more efficient resource/demand plan by taking that factor into account.
Shrinkage describes the percentage of time that employees are not handling interactions. Examples of different types of shrinkage:
- Meetings / Training
- Emergency Situation
In Genesys WFM, the term shrinkage is synonymous with the term overheads.
Overheads are assigned to schedule state groups. A schedule state group a collection of schedule states linked to a site. Schedule states include breaks, meals, exceptions, time off instances and so on.
A forecaster uses shrinkage as an optional step in the forecasting process to pre-plan additional FTE requirements. For example, it is known that vacations & team meetings are going to take place and pre-planning for this to ensure it can go ahead without affecting service level goals.
Shrinkage is attached to a schedule state group, so actual, historical shrinkage achievement can easily be measured and applied to the configured overhead. This will increase the accuracy of future shrinkage planning because it can be based on accurate numbers.
A scheduler can use the schedule state totals screen in Genesys WFM to review the impact of shrinkage levels on service level performance and make changes to the day accordingly, like moving or cancelling team meetings or initiating an overtime process.
A team leader or supervisor may have a shrinkage KPI / MBO - they will want to be aware of how much and what types of shrinkage are occurring in their team. Armed with this information, they will be able to effectively manage their team’s performance which will contribute to the overall performance of their business.
Use Case Benefits*
|Use Case Benefits||Explanation|
|Improved Employee Attrition Rate||Empower agents with more control over their schedules by identifying skill gaps and extending mobility and easy-to-use web-based tools|
|Improved Employee Occupancy||Improve agent adherence to workforce schedule by gaining better control and management of variances between target and actual availability and shrinkage through visibility into current information on agent performance metrics, schedule adherence and forecast variances. Improve utilization by optimizing planning and resource utilization through accurate omnichannel forecasting & scheduling and skills|
|Reduced Administration Costs||Reduce manual workforce scheduling activities by a decrease in time and costs associated with manual WFM efforts through the automatic updates of data, schedule shifts and database for skills and schedules|
Shrinkage is a generic term used in contact centers to describe the percentage of time that employees are not handling interactions. It must be planned for to allow service targets to be met to an appropriate level of efficiency. Genesys WFM provides a variety of shrinkage management options.
Use Case Definition
The business flow described below requires the base setup of the system as described in the use case “Genesys Workforce Scheduling for Voice (EE01)”.
Business Flow Description See the "EE1 - Optimize Agent Utilization for Voice Interactions" document for a general description of the forecasting flow. The additional steps below apply to shrinkage:
- The forecaster accesses the overheads view within the forecasting module and makes a choice. Do they wish to:
- use actual historical values via a saved template, or
- manually enter projected values.
- The forecaster then chooses the activity/activities that the shrinkage values apply to.
- The forecaster builds or modifies a staffing forecast using the required staffing wizard, comparing calculated and required FTE values where:
- Calculated does not account for shrinkage
- Required does account for shrinkage so FTE requirement will be higher
- The forecaster decides to publish to master forecast as described in base package use case.
- The scheduler reviews shrinkage running totals and makes adjustments to live schedule as necessary.
- Team leaders monitor and manage live schedules.
Business and Distribution Logic
Use Case Requirements
Customer Interface Requirements
Genesys WFM Web Supervisor is a browser based UI that requires Java applet. Access control for specific roles (e.g., Planners, Supervisors, Forecasters, 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 WFM product contains a number of real time reporting elements. Details can be found in the Workforce Management Administrator Guide.
The Genesys WFM 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:
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 a re requirements. See Supported Operating Environment Guide for specific versions.
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|
Capabilities Assumption: The full use case outlined here is available on premise.
- This use Case is available in Cloud
- v 1.1.5