Editing UseCases/Current/GenesysEngage-onpremises/CE01

{{SMART UseCase
|ID=CE01
|Title=Connect a Voice Interaction to the Right Resource
|Offering=GenesysEngage-onpremises
|SMART_Benefits={{SMART Benefits
|UCBenefitID=Increased Revenue
|UCBenefit=The ability to route a sales calls to the best skilled sales representative increases sales conversions.
}}{{SMART Benefits
|UCBenefitID=Improved Customer Experience
|UCBenefit=Shorter wait times and more accurate resolutions by connecting inbound calls or leads to the best matched representative make better customer experiences and improve Net Promoter score
}}{{SMART Benefits
|UCBenefitID=Reduced Transfers
|UCBenefit=Reduce the number of transfers due to better voice call routing through Genesys routing.
}}{{SMART Benefits
|UCBenefitID=Improved First Contact Resolution
|UCBenefit=Captured omni-channel data is analyzed to drive process improvements to enable a superior customer journey and allows agents to be equip with the ability to handle calls on a First Contact basis.
}}{{SMART Benefits
|UCBenefitID=Reduced Handle Time
|UCBenefit=Genesys' routing is far more efficient as it takes full customer context into consideration. This advantage in routing allows for more accurate and timely routing to the best agent to reduce wait time and costly mis-routes.
}}
|UCOverview=Organizations want to provide an exceptional customer and sales service experience by reducing transfers, hold time and repetition.

To achieve this experience, they need customizable software to fit complex rules, distributed using skills-based routing while automaticity capturing each call disposition for analysis.

When companies enable call routing within their Genesys environments, benefits can include:
|UCSummary=Customer wants to contact the company for a specific service or for further information around a product or offer and then calls the company. The system performs hours of operation, special day, and emergency checks, and then plays corresponding messages. The customer selects an option from a menu (prompt and collect) that maps to an agent skill expression. If no agents are available, the target expands to include an additional agent skill or skill-level before routing to an optional overflow number.

After the initial implementation, customers can enhance the service with more Genesys routing capabilities.
|PainPoints=*Poor customer experience scores due to excessive wait times, transfers, hold times, agents who do not have needed expertise, and the need for repeat contacts
*High staffing costs to meet service levels
*Inefficient use of agents who are responding to simple inquiries or requests
*Inability to use context of previous interactions to optimize each customer call


|DesiredState=*Optimize customer experience by connecting them to a knowledgeable, efficient agent available within a configured time period
*As customers wait in queue, remove skill requirements to expand the pool of available agents
*Route interactions without conversations leaving the queue to better understand why customers are calling and keep your data clean for clear reporting
|BuyerPersonas=Chief Marketing Officer, Business Analyst, IT Administrator
|QualifyingQuestions=# How easy is it for your customers to get repetitive or easy issues fixed?
# How often do your customers have first contact resolution?
# How often is a transfer required, due to agents’ experience or knowledge?
# What service level issues are you experiencing?
|MaturityLevel=Consistent
|SellableItems=CIM, CIM (HA), Interaction Workspace, Genesys Infomart, Genesys Infomart - HA (optional), Genesys Interactive Insights, SIP Interaction, SIP Interaction HA (optional), GVP, GVP HA (optional), SIP Business Continuity (Optional), ASR and TTS (Optional)
|CloudAssumptionsAdditional_Sales=This use case is available in the Cloud
|PremiseAssumptionsAdditional_Sales=Capabilities Assumption:This use case can be addressed utilizing SIP qualification and Parking OR can be delivered using GVP solution.
|BusinessImageFlow={{SMART BusinessImageFlow
|BusinessFlow=The flow describes the use case from the perspective of the caller and contact center agent. The following diagram shows the business flow of the use case:
|BusinessImage=https://www.lucidchart.com/documents/edit/ee59a752-1e08-4be8-8caa-e0fe31f5f353/0
|BusinessFlowDescription=#The caller initiates an inbound voice call to the contact center. Optionally, Skype For Business Platform can be used.
#The system checks if the day is configured as a special day. In this case a special day announcement is played and the call is disconnected.
#The system checks if the call is within the contact center's business hours. If not an out-of-office announcement is played and the call is disconnected.
#The system checks if an emergency announcement is activated. In this case an emergency announcement is played and the call is disconnected.
#A call steering message (DTMF menu) is played with various menu options (optional).
#A greeting announcement is played.
#The caller chooses a menu option using a DTMF tone entered on the handset. If the caller does not choose an option or chooses an unavailable option, the menu is repeated up to 2 times. If the caller still does not choose a valid menu option the call is handled with default routing parameters.
#The call is distributed to the best-fit agent for the chosen topic based on the agent's skill and skill level (see Distribution Logic for details).
#At the end of the call the agent sets a disposition code to record the call outcome for reporting purposes.
}}
|BusinessLogic=This chapter describes the business logic and business rules which drive the decisions made by the Genesys system within the business & routing flow above described in the chapters above, i.e. the parameters used by Genesys to drive routing decisions and how these are configured.

These parameters allow the user to configure a number of operational parameters related to routing logic, including the target skills for each menu option, priority tuning, timers and overflows.Some parameters are only available at DNIS / Route Point level. These are either needed only once at the beginning of the call flow (e.g. greeting message) or will be used across the whole call flow independent of subsequent DTMF menu choices of the customer. Other parameters are available at both the DNIS / Route Point level (to be used if no call steering has been activated) and at the level of the choice of a specific touch point. The following tables illustrate example parameters which may be configured through Genesys configuration tools.
===Parameters to configure Service Line Announcements===
The following parameters can be configured by service line:
{{{!}} class="wikitable"
{{!}}-
!{{!}}Name
!{{!}}Description
{{!}}-
{{!}}{{!}}Business hours
{{!}}{{!}}Sets the hours that you are open and accepting calls
{{!}}-
{{!}}{{!}}Special day
{{!}}{{!}}A list of exceptions to the regular open hours, for a holiday or other reason
{{!}}-
{{!}}{{!}}Emergency declared
{{!}}{{!}}Activates the emergency announcement (i.e. power outage, general closure)
{{!}}}
===Parameters to define the Call Steering / DTMF Menus===
The use case allows users to define Menu options externally through parameters, thereby simplifying the flow. Based on the menu options chosen, corresponding caller segmentation can be done by this context. 

Up to 4 levels of DTMF menus can be configured with maximally 9 different sub-options for each choice in the previous level. The combination of choices of the customer within the DTMF menu will determine the service requested and the agent skill required to best satisfy this request. This possibility provides highest flexibility to adapt the use case to a specific company requirement, but it is generally not recommended to use all available levels and number of menu choices to not provide a bad customer experience via a complicated and lengthy DTMF menu.
===Distribution Parameters===
The following list of parameters define the behaviour of the distribution logic. These parameters can be configured per combination of possible DTMF choices in the Call Steering.
{{{!}} class="wikitable"
{{!}}-
!{{!}}Name
!{{!}}Description
{{!}}-
{{!}}{{!}}Primary Target
{{!}}{{!}}The skill and skill level expression to which the call will be routed. Alternatively, a DN or a specific Agent/Agent Group can be configured as routing target.
{{!}}-
{{!}}{{!}}Secondary Target
{{!}}{{!}}The skill and skill level expression to which the call will be routed in the first target expansion step. Alternatively, a DN or a specific Agent/Agent Group can be configured as routing target.
{{!}}-
{{!}}{{!}}Tertiary Target
{{!}}{{!}}The skill and skill level expression to which the call will be routed in the second target expansion step. Alternatively, a DN or a specific Agent/Agent Group can be configured as routing target.
{{!}}}
The skill expression to define the target is defined by a combination of skill(s) and skill levels. Best practice is to use the same skill(s) with decreased skill level in subsequent targets to gradually expand the pool of agents after each timeout, rather than using a different skill.Priority tuning is configured via the following parameters:

*Priority increment (the amount to increase the priority after the interval time)
*Priority interval (the time between priority increases)
*Priority limit (the maximum priority)
*Priority start (the starting priority)

===Reporting Parameters===
The following five business parameters represent reporting categories and are completely customizable to your business model. You can assign different combinations of these parameters to each of your Inbound and Distribution parameter groups, to distinguish them in reporting and enable you to identify the unique properties of the parameter group.
{{{!}} class="wikitable"
{{!}}-
!{{!}}Name
!{{!}}Description
{{!}}-
{{!}}{{!}}Department
{{!}}{{!}}Business organization used as a category for reporting
{{!}}-
{{!}}{{!}}Flow
{{!}}{{!}}A business flow used as a category in reporting
{{!}}-
{{!}}{{!}}Intent Category
{{!}}{{!}}Business categories typically used as the top level of the call steering menu choices
{{!}}}

=== Audio Resources ===
The following audio resources are configurable by service line:
{{{!}} class="wikitable"
{{!}}-
!{{!}}Name
!{{!}}Example
{{!}}-
{{!}}{{!}}Business Hours
{{!}}{{!}}A message announcing office closure and inviting to call again at opening time
{{!}}-
{{!}}{{!}}Please Wait on Hold
{{!}}{{!}}A message inviting to wait
{{!}}-
{{!}}{{!}}Welcome
{{!}}{{!}}A Greeting message
{{!}}-
{{!}}{{!}}Emergency
{{!}}{{!}}An emergency message
{{!}}-
{{!}}{{!}}Special Day
{{!}}{{!}}A message announcing office closure due to special day (i.e. a bank holiday)
{{!}}-
{{!}}{{!}}Music waiting in queue
{{!}}{{!}}Music
{{!}}-
{{!}}{{!}}Main DTMF Menu Message
{{!}}{{!}}The main Call Steering menu accouncement
{{!}}-
{{!}}{{!}}Sub-DTMF Menu Messages (multiple messages)
{{!}}{{!}}The sub-menu messages for the Call Steering as required.
{{!}}}
|DistributionImageFlow={{SMART DistributionImageFlow
|DistributionImage=https://www.lucidchart.com/documents/edit/ba39e741-d78c-431f-80cd-458408bc26e7/0
|DistributionFlowDescription=#The system checks whether any agents corresponding to the target are logged in. If no agents are logged in, the flow will continue with step 8.
#If agents are logged in, the call is queued to the first target.
#The system checks whether any agents are available.
#If agents with the required target are available, the call will be distributed to the available agent who is longest idle.
#If no agent is available, music is played while the caller is in queue.
#The priority is increased according to priority tuning parameters.
#The system checks whether the target timeout has expired (if configured). If the timeout has not expired, the call continues to wait for an available agent.
#If the timeout has expired, then the system checks whether an additional target has been configured. If no additional target has been configured, the call continues to wait for an available agent.
#If the next target is still internal, Genesys will attempt to distribute to the expanded target. Up to a maximum of two iterations of target expansion can be configured. The flow continues at step 1.
#If the next target is configured to be an external number, the call will be forwarded to this number.
}}
|DistributionLogic='''General distribution functionality'''

The distribution logic will include the following functionality:

*The target will be configurable by (final) DTMF choice. Additional targets are optional.
*RONA-functionality: If an agent does not accept the voice interaction, the voice call will be automatically put back into the distribution flow after a time out. The agent will be set to not-ready.
*Blending with other media types will be possible. Priority settings for voice interactions will be configurable to enable proper priority ranges between different media types. Capacity rules will be configured for the agents / agent groups to define what interactions can be handled in parallel (if any).
|CustomerInterfaceRequirements=N/A
|AgentDeskRequirements=Agent Desktop provides a suite of out-of-the-box and configurable features to enable you to maximize routing:

*Agents can view the menu selection (service) and/or the DNIS when a call is [https://all.docs.genesys.com/PEC-AD/Current/Agent/ADVoice routed to them]
*Agents can [https://all.docs.genesys.com/PEC-AD/Current/Agent/ADintinter transfer calls] to other individual agents and specific route points enabled for the agent.
*Configuration of [https://all.docs.genesys.com/PEC-AD/Current/Agent/ADQuickStart#Setting_your_status_to_Not_Ready_with_a_Reason not-ready reason codes] (for example, Admin Work, Lunch, Meeting, Pause, RONA, and Training).
*Configuration of [https://all.docs.genesys.com/PEC-AD/Current/Agent/ADQuickStart#How_do_I_set_a_disposition_code.3F disposition codes] for reporting of business outcome (for example, Cross Sell, Need Follow-Up, Not Right Skill, Processed, Terminated, Transferred, Up Sell). Agents select the disposition while handling the interaction.

If Skype for Business Platform is used for Inbound call (option), agents must Workspace Desktop Edition integrated with Skype for Business endpoint.
|RealTimeReporting='''Genesys Pulse''' enables at-a-glance views of real-time contact center statistics through dashboards and wallboards.

Each Genesys Pulse report presents information within graphical widgets, which show graphs or tables that provide information about incoming voice call queues, agent groups, or individual agents. You can personalize Genesys Pulse reports based on functional, geographical, or organizational considerations.

Genesys Pulse provides templates for the most popular reports. You can use these templates to quickly add report widgets to your dashboard. 

The following Genesys Pulse standard reports are particularly relevant for this use case:

*Agent Group Status &mdash; Displays the current number of agents in their various interaction handling states by group.
*Agent KPIs &mdash; Displays agent key performance indicators for agent groups and individual agents within those groups.
*Agent Login &mdash; Displays agents that are logged in, what type of work they have been assigned, and their current status.
*Queue KPIs &mdash; Displays call activity associated with the interaction queues.

See [https://docs.genesys.com/Documentation/EZP/latest/User/RTRTemplatesA Standard Report Templates] for more information.
|HistoricalReporting='''Genesys CX Insights''' (GCXI) provides customizable reports and dashboards that can help you track the benefits of this use case. The metrics and attributes in these reports measure and filter Info Mart data based on interaction-related activities conducted by active agents, on the agent queue(s) through which customer interactions pass, and on Business Attributes attached data, and enable you to examine low-level interaction details, including handling attempts, flow, and transfers.

Some of the most relevant reports include:

*[https://docs.genesys.com/Documentation/GCXI/9.0.0/User/HRCXIAgentSmryActvtyActv Agent Summary Activity Report (Active)] &mdash; Provides a breakdown of the duration of the different states that an agent can be in (Ready, Not Ready, Busy, and Other).
*[https://docs.genesys.com/Documentation/GCXI/9.0.0/User/HRCXIAgntPerfDshbrd Agent Performance Dashboard] &mdash; Provides at-a-glance key information about agents, focusing on metrics related to handle time and agent conduct.
*[https://docs.genesys.com/Documentation/GCXI/9.0.0/User/HRCXIAgentUtilization Agent Utilization] &mdash; Provides detailed information about agent performance with respect to the customer and consults interactions that are processed within the contact center for a range of days that you specify, and illustrates the percentage of interactions accepted by agents.
*[https://docs.genesys.com/Documentation/GCXI/9.0.0/User/HRCXIQuOutln Queue Outline Report] and [https://docs.genesys.com/Documentation/GCXI/9.0.0/User/HRCXIQuSmry Queue Summary Report] &mdash; Collect detailed counts related to customer interactions and consult interactions, showing how the number of interactions/consultations that entered a particular queue or queue group break down into the various queue-related metrics that provide interaction counts, including abandoned, or distributed and handled by any routing target, such as an agent.
*[https://docs.genesys.com/Documentation/GCXI/9.0.0/User/HRCXIIxnHndlngAttmpt Interaction Handling Attempt Report] &mdash; Summarizes segment-related details with regard to agent handling of contact center interactions.
*[https://docs.genesys.com/Documentation/GCXI/9.0.0/User/HRCXITransferDtls Transfer Detail Report] &mdash; Learn more about the initiating and receiving parties of those contact center interactions that involve a transfer including the technical result, the mediation devices through which the interaction passed, the business attribute, and the entire duration of the interaction.
*Other reports relevant to this use case are found in the [https://docs.genesys.com/Documentation/GCXI/9.0.0/User/HRCXIAgentsReports Agents], [https://docs.genesys.com/Documentation/GCXI/9.0.0/User/HRCXIBusResReports Business Results], [https://docs.genesys.com/Documentation/GCXI/9.0.0/User/HRCXIDetail Detail], and [https://docs.genesys.com/Documentation/GCXI/9.0.0/User/HRCXIQueuesReports Queues] folders.

For more information about the Genesys CX Insights reports, see [https://docs.genesys.com/Documentation/GCXI/9.0.0/User/Welcome ''Genesys CX Insights 9.0 User's Guide''].
|GeneralAssumptions=* SIP connectivity is offered as a standard solution for Gxxx Exxx on-premises and Cloud.

* Optionally Skype for business can be offered for Gxxx Exxx on-premises only (not supported for Genesys Multicloud CX).

* Implementation based on SIP Server (SIP Voice Blueprint).
* Routing parameters are configured through GAX operational parameter groups, which are referenced in the underlying strategy / routing application.
* Text To Speech and Speech Recognition are not included.
* No Genesys Voice Portal - all customer input is via DTMF prompt and collect.
* Genesys Infomart and Interactive Insights will be used for historical reporting.
* Workspace Desktop Edition will be used as agent desktop.
* Genesys Pulse will be used for real-time reporting.
* No Integration with third party systems.


'''For Skype for Business Connectivity (Option):'''

*<span class="s1">Integration with Skype for Business based on Multimedia Connector (Skype for Business Blueprint)</span>
*The agent uses Workspace Desktop Edition integrated with Skype for Business endpoint.
*No integration with 3rd party recording. GIR is the only available recording option with Multimedia Connector for Skype for Business.
*GIA is not supported as a standard option.
*PS team should be consulted for Skype for Business Platform deployment.
|DocVersion=v 1.2.2
|SMART_HybridAssumptions={{SMART HybridAssumptions
|Hybrid_Assumption=v 1.2.0
}}
|RelatedDocs={{TSSection
|sectionheading=Agent Desktop
|description=Agent Desktop enables agents to handle routed interactions, transfer interactions, and set interaction disposition.
|relatedarticles=* [https://all.docs.genesys.com/PEC-AD/Current/Agent/AD Agent Desktop 9 Help]
* [https://all.docs.genesys.com/PEC-AD/HIW How Agent Desktop Works]
}}{{TSSection
|sectionheading=Workspace Desktop Edition
|description=Workspace Desktop Edition enables agents to handle routed interactions, transfer interactions, and set interaction disposition.
|relatedarticles=*[https://docs.genesys.com/Documentation/IW/8.5.1/Help/Welcome Workspace Desktop Edition Agent Help]
*[https://docs.genesys.com/Documentation/IW/8.5.1/User/Welcome Workspace Desktop Edition User's Guide]
}}
|SMART_Interdependencies_Requires={{SMART Interdependencies Requires
|Requires=CE02, CE04
}}{{SMART Interdependencies Requires
|Requires=EE01
|Conditions=Optional to enable Video Chat
}}
|SMART_Interdependencies_Incompatible={{SMART Interdependencies Incompatible
|Incompatible=SL02
}}
|UCBenefitID=Improved Agent Competency
|UCBenefit=This UC improves NPS by XYZ.
|Personas=Edith (VP Customer Experience), Bettina (VP Digital Engagement), Carl (Contact Center Director)
|Cloud=Yes
|Premise=Yes
|Benefits=* Increase revenue due to improved match of customer with best agent (Revenue)
* Enhance customer retention by matching caller with highly skilled agent (Revenue)
* Reduce transfers through skills-based routing (Efficiency)
* Reduce Average Handle Time by matching every caller with the best available agent (Efficiency)
* Improve NPS by optimally handling customer issue/inquiry (Experience)
* Reduce customer frustration by matching with knowledgeable agent (Experience)
|GenersalAssumptions=test
}}