Difference between revisions of "UseCases/Current/PureConnect/EE11"

From Genesys Documentation
Jump to: navigation, search
m (Text replacement - "Gxxx Exxx on-premises" to "Genesys Engage on-premises")
 
(4 intermediate revisions by 4 users not shown)
Line 3: Line 3:
 
|Title=Genesys Shift Bidding
 
|Title=Genesys Shift Bidding
 
|Offering=PureConnect
 
|Offering=PureConnect
|UCIntro=The Optimizer Use Case for PureConnect is not available. Please reference the [https://repository.docs.genesys.com/Draft:UseCases/Current/PureEngage/EE11 Genesys Shift Bidding (EE11) for PureEngage] product and use case as a Workforce Engagement Management option.
+
|UCIntro=The Optimizer Use Case for PureConnect is not available. Please reference the {{Link-SomewhereInThisVersion|manual=GenesysEngage-onpremises|topic=EE11|display text=Genesys Shift Bidding (EE11) for Genesys Engage on-premises}} product and use case as a Workforce Engagement Management option.
 
|PainPoints=*Employee satisfaction in regards to shift designs leads to attrition and employee engagement issues.
 
|PainPoints=*Employee satisfaction in regards to shift designs leads to attrition and employee engagement issues.
 
|DesiredState=* <span style="display: inline !important; float: none; background-color: transparent; color: rgb(0, 0, 0); font-family: Calibri,Calibri_MSFontService,Sans-Serif; font-size: 15.8px; font-style: normal; font-variant: normal; font-weight: 400; letter-spacing: 0px; line-height: 0px; -ms-touch-select: none; -ms-user-select: text; orphans: 2; text-align: left; text-decoration: none; text-indent: 0px; text-transform: none; -webkit-text-stroke-width: 0px; white-space: normal; word-spacing: 0px;">Enable employees with self- service by allowing them to bid on their shift.</span>
 
|DesiredState=* <span style="display: inline !important; float: none; background-color: transparent; color: rgb(0, 0, 0); font-family: Calibri,Calibri_MSFontService,Sans-Serif; font-size: 15.8px; font-style: normal; font-variant: normal; font-weight: 400; letter-spacing: 0px; line-height: 0px; -ms-touch-select: none; -ms-user-select: text; orphans: 2; text-align: left; text-decoration: none; text-indent: 0px; text-transform: none; -webkit-text-stroke-width: 0px; white-space: normal; word-spacing: 0px;">Enable employees with self- service by allowing them to bid on their shift.</span>
 +
|MaturityLevel=Differentiated
 
|DocVersion=V 1.0.1
 
|DocVersion=V 1.0.1
 
}}
 
}}

Latest revision as of 21:19, November 9, 2021

This topic is part of the manual PureConnect Use Cases for version Current of Genesys Use Cases.
Important
The Optimizer Use Case for PureConnect is not available. Please reference the Genesys Shift Bidding (EE11) for Genesys Engage on-premises product and use case as a Workforce Engagement Management option.
Empower employees to influence their schedules

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.

Other offerings:

Use Case Overview

Story and Business Context

Use Case Benefits*

The following benefits are based on benchmark information captured from Genesys customers and may vary based on industry, lines of business or Genesys product line: Info needed.

*You can sort all use cases according to their stated benefits here: Sort by benefits

Summary



Use Case Definition

Info needed.

Business and Distribution Logic

Business Logic


User Interface & Reporting



Reporting

Customer-facing Considerations

Interdependencies

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
None None None None





Document Version

  • Version V 1.0.1 last updated November 9, 2021
Comments or questions about this documentation? Contact us for support!