PEC-ROU/HIW - Revision history

WikiSysop at 13:48, August 18, 2022

2022-08-18T13:48:54Z

WikiSysop at 18:45, August 2, 2022

2022-08-02T18:45:59Z

Ed.jamer@genesys.com: Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

2021-11-09T20:29:13Z

Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

Peter.chaplin@genesys.com: Published

2021-10-07T09:48:25Z

Published

Peter.chaplin@genesys.com: Published

2021-10-07T09:44:03Z

Published

Brian.marshall@genesys.com: Published

2021-08-05T12:57:46Z

Published

Brian.marshall@genesys.com: Published

2021-03-17T15:32:28Z

Published

Brian.marshall@genesys.com: Published

2020-12-04T15:26:16Z

Published

Brian.marshall@genesys.com: Published

2020-12-04T15:16:13Z

Published

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

2020-07-25T02:34:34Z

Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

@@ Line 39: / Line 39: @@
 }}{{FeatureSection
 |featureheading=Routing to agents
-|relatedapps=Agent Desktop
+|relatedapps=Agent Workspace
 |users=Agents, Supervisors, Administrators
 |anchor=agent

@@ Line 35: / Line 35: @@
 |anchor=route
 |description=Use Genesys Designer to create and manage applications that contain an assisted service (routing) phase that can be customized for your particular business needs. For example, you can specify your daily hours of operation, indicate which days your offices are closed, and define the criteria that determines how certain interactions are to be handled.
-|relatedarticles=*{{Link-AnywhereElse|product=PEC-ROU|version=Current|manual=Designer|topic=GetStarted|display text=Getting Started}}
+|relatedarticles=*{{Link-AnywhereElse|product=DES|version=Current|manual=Designer|topic=GetStarted|display text=Getting Started}}
-*{{Link-AnywhereElse|product=PEC-ROU|version=Current|manual=Designer|topic=RoutingBlocks|display text=About Routing Blocks}}
+*{{Link-AnywhereElse|product=DES|version=Current|manual=Designer|topic=RoutingBlocks|display text=About Routing Blocks}}
 }}{{FeatureSection
 |featureheading=Routing to agents
@@ Line 42: / Line 42: @@
 |users=Agents, Supervisors, Administrators
 |anchor=agent
-|description=Agent Desktop enables agents to communicate with customers and team members through phone calls and Outbound Campaigns and Genesys Digital channels, including voice, chat, email, social media, SMS, WhatsApp, and workitems.
+|description=Agent Workspace enables agents to communicate with customers and team members through phone calls and Outbound Campaigns and Genesys Digital channels, including voice, chat, email, social media, SMS, WhatsApp, and workitems.
 |relatedarticles=*{{Link-Standalone|topic=PEC-AD/HIW}}
 *{{Link-AnywhereElse|product=PEC-AD|version=Current|manual=Agent|topic=ADchannels}}

@@ Line 20: / Line 20: @@
 You can manage how interactions are routed by creating a set of decisions and instructions that specify how an interaction is to be handled when certain conditions are met. For example, you might direct certain customers to an agent who has a particular type of skill, such as a high level of proficiency in the customer's preferred language. If such an agent isn't available, the criteria can then be relaxed to find the next best-skilled available agent, and so on.
-|featureoverview=The technical aspects of routing are handled behind-the-scenes by the Genesys Engage cloud platform. However, there are several key components that provide customizable features and options related to routing:
+|featureoverview=The technical aspects of routing are handled behind-the-scenes by the Genesys Multicloud CX platform. However, there are several key components that provide customizable features and options related to routing:
 *Designer applications provide both self-service (IVR) and assisted-service (routing) capabilities. If a customer is not able to resolve their issue in self-service, they can be connected with an agent for assistance.
@@ Line 26: / Line 26: @@
 *Genesys Task Routing can accept workitems submitted from an external source (such as Salesforce or NetSuite) and treats them like any other type of Genesys interaction. For example, you could use a Designer application to route workitems to the best-skilled agent.
 *Agent Setup enables you to designate incoming and outgoing mailboxes for Genesys Email classic.
-*Intelligent Workload Distribution enables you to designate incoming and outgoing mailboxes for Genesys Engage cloud Email.
+*Intelligent Workload Distribution enables you to designate incoming and outgoing mailboxes for Genesys Multicloud CX Email.
 <br />

@@ Line 69: / Line 69: @@
 |anchor=predictive
 |description=Genesys Predictive Routing (GPR) draws on accumulated agent, customer, and interaction data, enabling you to analyze omnichannel interactions and outcomes and generate models to predict outcomes. From this analysis, combined with machine learning, you can determine the best possible match between waiting interactions and available agents, and then route the interactions accordingly.
-|relatedarticles=*[https://all.docs.genesys.com/PE-GPR/9.0.0/Help Predictive Routing Help] - explains how to use the web application to view uploaded data, create predictors and models, and analyze how well Predictive Routing is working.
+|relatedarticles=*{{Link-AnywhereElse|product=PE-GPR|version=9.0.0|manual=Help|display text=Predictive Routing Help}} - explains how to use the web application to view uploaded data, create predictors and models, and analyze how well Predictive Routing is working.
-*[https://all.docs.genesys.com/PE-GPR/9.0.0/Deployment Predictive Routing Deployment and Operations Guide] - explains how to deploy the on-premise components for Predictive Routing, upload data, integrate the URS Strategy Subroutines into your Routing solution, and integrate with Genesys Historical Reporting.
+*{{Link-AnywhereElse|product=PE-GPR|version=9.0.0|manual=Deployment|display text=Predictive Routing Deployment and Operations Guide}} - explains how to deploy the on-premise components for Predictive Routing, upload data, integrate the URS Strategy Subroutines into your Routing solution, and integrate with Genesys Historical Reporting.
 }}
 }}

@@ Line 69: / Line 69: @@
 |anchor=predictive
 |description=Genesys Predictive Routing (GPR) draws on accumulated agent, customer, and interaction data, enabling you to analyze omnichannel interactions and outcomes and generate models to predict outcomes. From this analysis, combined with machine learning, you can determine the best possible match between waiting interactions and available agents, and then route the interactions accordingly.
-|relatedarticles=*[https://all.docs.genesys.com/Draft:PE-GPR/9.0.0/Help Predictive Routing Help] - explains how to use the web application to view uploaded data, create predictors and models, and analyze how well Predictive Routing is working.
+|relatedarticles=*[https://all.docs.genesys.com/PE-GPR/9.0.0/Help Predictive Routing Help] - explains how to use the web application to view uploaded data, create predictors and models, and analyze how well Predictive Routing is working.
-*[https://all.docs.genesys.com/Draft:PE-GPR/9.0.0/Deployment Predictive Routing Deployment and Operations Guide] - explains how to deploy the on-premise components for Predictive Routing, upload data, integrate the URS Strategy Subroutines into your Routing solution, and integrate with Genesys Historical Reporting.
+*[https://all.docs.genesys.com/PE-GPR/9.0.0/Deployment Predictive Routing Deployment and Operations Guide] - explains how to deploy the on-premise components for Predictive Routing, upload data, integrate the URS Strategy Subroutines into your Routing solution, and integrate with Genesys Historical Reporting.
 }}
 }}

@@ Line 25: / Line 25: @@
 *Predictive Routing uses machine learning to predict which agent-interaction matchups can best improve your specified KPIs, or create applications specifically designed to offer surveys or callbacks to customers.
 *Genesys Task Routing can accept workitems submitted from an external source (such as Salesforce or NetSuite) and treats them like any other type of Genesys interaction. For example, you could use a Designer application to route workitems to the best-skilled agent.
-*Agent Setup enables you to designate incoming and outgoing mailboxes<!-- for Genesys Email classic-->.
+*Agent Setup enables you to designate incoming and outgoing mailboxes for Genesys Email classic.
-<!--*intelligent Workload Distribution enables you to designate incoming and outgoing mailboxes for Genesys Engage cloud Email.-->
+*Intelligent Workload Distribution enables you to designate incoming and outgoing mailboxes for Genesys Engage cloud Email.
 <br />
@@ Line 36: / Line 36: @@
 |description=Use Genesys Designer to create and manage applications that contain an assisted service (routing) phase that can be customized for your particular business needs. For example, you can specify your daily hours of operation, indicate which days your offices are closed, and define the criteria that determines how certain interactions are to be handled.
 |relatedarticles=*{{Link-AnywhereElse|product=PEC-ROU|version=Current|manual=Designer|topic=GetStarted|display text=Getting Started}}
-*{{Link-AnywhereElse|product=PEC-ROU|version=Current|manual=Designer|topic=RoutingBlocks}}
+*{{Link-AnywhereElse|product=PEC-ROU|version=Current|manual=Designer|topic=RoutingBlocks|display text=About Routing Blocks}}
 }}{{FeatureSection
 |featureheading=Routing to agents
@@ Line 51: / Line 51: @@
 |anchor=mailbox
 |description=Use Agent Setup to designate your incoming and outgoing mailboxes for email routing. You can also create email aliases that agents can choose as their From address.
-<!--With Engage cloud Email, use intelligent Workload Distribution to designate your incoming and outgoing mailboxes.-->
 |relatedarticles=*{{Link-Standalone|topic=PEC-Email/HIW}}
-*{{Link-AnywhereElse|product=PEC-AS|version=Current|manual=ManageCC|topic=Email_addresses_and_mailboxes|display text=Email addresses and mailboxes}}
+*{{Link-AnywhereElse|product=PEC-AS|version=Current|manual=ManageCC|topic=Email_addresses_and_mailboxes|display text=Email classic addresses and mailboxes}}
-<!--*{{Link-AnywhereElse|product=PEC-IWD|version=Current|manual=Administrator|topic=IWDMailboxes|display text=Engage cloud Email addresses and mailboxes}}-->
+*{{Link-AnywhereElse|product=PEC-IWD|version=Current|manual=Administrator|topic=IWDMailboxes|display text=Engage cloud Email addresses and mailboxes}}
 }}{{FeatureSection
 |featureheading=Genesys Task Routing

@@ Line 8: / Line 8: @@
 |Application=Designer
 |featurename=Routing
-|ShortDescription=Routing is the process by which an interaction received by your contact center is directed to the appropriate destination.
+|ShortDescription=Routing is the process by which an interaction is directed to the appropriate target destination.
-|overviewtext=Customers can contact you from a variety of sources, or ''channels''. For example, a customer might initiate an interaction by reaching out to you by telephone call, email, or chat. A routing strategy determines the path that each interaction will take in your organization to ensure it reaches the appropriate target, such as an agent, department, email inbox, or other destination.
+|overviewtext=Customers can contact you from a variety of sources, including:
-Different channels often involve specialized handling for that particular type of interaction. For example, you might have different rules or strategies for receiving and routing voice and digital interactions, such as:
+*voice calls
 *emails
 *chats
 *SMS (text messages)
-*social media (such as Facebook, Twitter, or WhatsApp)
+*social media platforms
-The Genesys Engage omnichannel customer experience platform provides the ability to create and customize routing solutions that are fine-tuned to the specific needs of your business or organization.
+You can manage how interactions are routed by creating a set of decisions and instructions that specify how an interaction is to be handled when certain conditions are met. For example, you might direct certain customers to an agent who has a particular type of skill, such as a high level of proficiency in the customer's preferred language. If such an agent isn't available, the criteria can then be relaxed to find the next best-skilled available agent, and so on.
-|featureoverview=Let's say your contact center receives a voice call from someone who speaks Spanish. Ideally, you would want this customer to reach someone who can speak with them in their native language. You can then set up a routing strategy to have this type of call routed to agents who have the highest skill level for Spanish. If one isn't available, you can then "relax" the criteria to find the next best available agent, and so on.
+|featureoverview=The technical aspects of routing are handled behind-the-scenes by the Genesys Engage cloud platform. However, there are several key components that provide customizable features and options related to routing:
-Of course, this is just a very basic example. You might also want to incorporate more advanced features in your routing, such as Predictive Routing, where machine learning is used to predict which agent-interaction matchups can best improve your specified KPIs, or create applications specifically designed to offer surveys or callbacks to customers. Genesys Task Routing allows you to submit workitems to Genesys from an external source, such as Salesforce or NetSuite, and treat them like any other type of Genesys interaction. For example, you could use a Designer application to route workitems to the best-skilled agent.
+*Designer applications provide both self-service (IVR) and assisted-service (routing) capabilities. If a customer is not able to resolve their issue in self-service, they can be connected with an agent for assistance.
-Genesys Engage enables you to construct highly complex and powerful routing strategies that can serve just about any business scenario or requirement.
+<br />
 |FeatureSection={{FeatureSection
 |featureheading=Routing customization
@@ Line 47: / Line 51: @@
 |anchor=mailbox
 |description=Use Agent Setup to designate your incoming and outgoing mailboxes for email routing. You can also create email aliases that agents can choose as their From address.
-|relatedarticles=*{{Link-AnywhereElse|product=PEC-AS|version=Current|manual=ManageCC|topic=Email_addresses_and_mailboxes|display text=Email Mailboxes}}
+<!--With Engage cloud Email, use intelligent Workload Distribution to designate your incoming and outgoing mailboxes.-->
 }}{{FeatureSection
 |featureheading=Genesys Task Routing

@@ Line 1: / Line 1: @@
 {{HIW
 |DisplayName=How routing works
 |TocName=How routing works
 |Platform=GenesysEngage-cloud
-|ComingSoon=No
+|Role=Administrator
-|Context=Learn how routing ensures that each customer interaction received by your contact center is directed to the appropriate destination.
+|Application=Designer
 |featurename=Routing
 |ShortDescription=Routing is the process by which an interaction received by your contact center is directed to the appropriate destination.
@@ Line 66: / Line 64: @@
 *[https://all.docs.genesys.com/Draft:PE-GPR/9.0.0/Deployment Predictive Routing Deployment and Operations Guide] - explains how to deploy the on-premise components for Predictive Routing, upload data, integrate the URS Strategy Subroutines into your Routing solution, and integrate with Genesys Historical Reporting.
 }}
 }}

PEC-ROU/HIW - Revision history

WikiSysop at 13:48, August 18, 2022

WikiSysop at 18:45, August 2, 2022

Ed.jamer@genesys.com: Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX"

Peter.chaplin@genesys.com: Published

Peter.chaplin@genesys.com: Published

Brian.marshall@genesys.com: Published

Brian.marshall@genesys.com: Published

Brian.marshall@genesys.com: Published

Brian.marshall@genesys.com: Published

WikiSysop: Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"