m (Text replacement - "PureEngage" to "Genesys Engage") |
m (Text replacement - "PureCloud" to "Genesys Cloud") |
||
Line 19: | Line 19: | ||
You receive: | You receive: | ||
*A reference to the region where Altocloud is accessible. For more information on using regions to consume API information, see the {{#Widget:ExtLink|link=https://developer.mypurecloud.com/api/rest/|displaytext=Region Authentication table}}. | *A reference to the region where Altocloud is accessible. For more information on using regions to consume API information, see the {{#Widget:ExtLink|link=https://developer.mypurecloud.com/api/rest/|displaytext=Region Authentication table}}. | ||
− | *An email containing instructions and credentials on how to connect to the | + | *An email containing instructions and credentials on how to connect to the Genesys Cloud Admin UI to define business logic, configure integrations, and query analytical dashboards. |
|media1= | |media1= | ||
}} | }} | ||
Line 28: | Line 28: | ||
|textwide=Work with your Genesys project team to: | |textwide=Work with your Genesys project team to: | ||
− | #Configure necessary | + | #Configure necessary Genesys Cloud permissions for administrators. For more information, see {{#Widget:ExtLink|link=https://help.mypurecloud.com/articles/altocloud-permissions-overview/|displaytext=Altocloud permissions overview}}. |
− | #Configure necessary | + | #Configure necessary Genesys Cloud permissions for agents to access the Altocloud journey dashboards within Agent Desktop. Permissions can be set globally for the entire agent population, for an agent group, or for individual agents. For more information see {{#Widget:ExtLink|link=https://help.mypurecloud.com/articles/altocloud-permissions-overview/|displaytext=Altocloud permissions overview.}} |
#Define the appropriate routing logic for chats that Altocloud proactively triggers. | #Define the appropriate routing logic for chats that Altocloud proactively triggers. | ||
#If this is the first time you have configured Web Chat with Genesys Widgets, request the corresponding API key to use the Chat API (Advanced Chat v3). You will need this later for the initial provisioning of Widgets on your website. | #If this is the first time you have configured Web Chat with Genesys Widgets, request the corresponding API key to use the Chat API (Advanced Chat v3). You will need this later for the initial provisioning of Widgets on your website. | ||
Line 64: | Line 64: | ||
|textwide= | |textwide= | ||
− | {{NoteFormat|See {{#Widget:ExtLink|link=https://all.docs.genesys.com/Draft:ATC/GPEandWidgets|displaytext=Prepare widgets for Altocloud}} to deploy Genesys Widgets for | + | {{NoteFormat|See {{#Widget:ExtLink|link=https://all.docs.genesys.com/Draft:ATC/GPEandWidgets|displaytext=Prepare widgets for Altocloud}} to deploy Genesys Widgets for Genesys Cloud. Widgets v.2 is the Genesys Cloud name used for Genesys Widgets. For Genesys Engage, see the {{#Widget:ExtLink|link=https://all.docs.genesys.com/WID/Current/Developer/GWCDeployment|displaytext=Deployment guide}} for instructions.|}} |
Once you deploy Genesys Widgets, obtain the {{#Widget:ExtLink|link=https://all.docs.genesys.com/ATC/Current/AdminGuide/Tracking_snippet|displaytext=tracking snippet}} and add it to all web pages that Altocloud should observe. | Once you deploy Genesys Widgets, obtain the {{#Widget:ExtLink|link=https://all.docs.genesys.com/ATC/Current/AdminGuide/Tracking_snippet|displaytext=tracking snippet}} and add it to all web pages that Altocloud should observe. | ||
Line 118: | Line 118: | ||
====Create leads in Salesforce==== | ====Create leads in Salesforce==== | ||
− | Predictive Engagement facilitates an integration with Salesforce by providing predefined | + | Predictive Engagement facilitates an integration with Salesforce by providing predefined Genesys Cloud data actions and an example Architect workflow. An administrator can build an action map that uses the Architect flow action along with these data actions and workflow to create leads and assign campaign attributions in Salesforce when qualified users arrive on your website. For more information, see {{#Widget:ExtLink|link= https://all.docs.genesys.com/ATC/Current/AdminGuide/ScenarioArchFlows|displaytext=Salesforce lead creation and campaign attribution}}. |
|media1= | |media1= |
Revision as of 13:45, September 18, 2020
Genesys Predictive Engagement (Altocloud)
Genesys Predictive Engagement (previously called Altocloud), a real-time journey analytics platform, can observe and analyze visitors on your digital properties, such as websites. Altocloud can predict real-time probability for visitors to achieve a desirable business outcome, and then acts to offer the most appropriate and effective channel to assist them in completing their journey. For an in-depth look at Altocloud, see the full documenatation set here.
To set up Altocloud in your Genesys Engage cloud environment, complete these initial tasks.
Prepare your tenant
With your Genesys account team, evaluate whether your environment has the necessary prerequisites.
With your Genesys project team, enable Genesys Altocloud functionality on your tenant.
You receive:
- A reference to the region where Altocloud is accessible. For more information on using regions to consume API information, see the Region Authentication table.
- An email containing instructions and credentials on how to connect to the Genesys Cloud Admin UI to define business logic, configure integrations, and query analytical dashboards.
Configure permissions and routing logic
- Configure necessary Genesys Cloud permissions for administrators. For more information, see Altocloud permissions overview.
- Configure necessary Genesys Cloud permissions for agents to access the Altocloud journey dashboards within Agent Desktop. Permissions can be set globally for the entire agent population, for an agent group, or for individual agents. For more information see Altocloud permissions overview.
- Define the appropriate routing logic for chats that Altocloud proactively triggers.
- If this is the first time you have configured Web Chat with Genesys Widgets, request the corresponding API key to use the Chat API (Advanced Chat v3). You will need this later for the initial provisioning of Widgets on your website.
Log in to Altocloud
Configure journey shaping settings
In the Web Tracking section, enable domain whitelisting. This step authorizes your website domain to be a valid originator of web journey events.
Configure your Segments. Segments categorize your website visitors into audiences that can be used in real-time to trigger engagement logic.
Configure your Outcomes.
Outcomes represent business objectives and Altocloud uses them to predict whether a visitor's behavior is leading them to achieve a desirable result on their own, or whether an agent needs to intervene.Configure your web pages
Once you deploy Genesys Widgets, obtain the tracking snippet and add it to all web pages that Altocloud should observe.
Configure your web pages with Genesys Widgets:
- If you are already running Genesys Widgets, ensure that you have the proper version.
- If needed, fetch the latest version from the public CDN (instructions in deployment guide).
Configure your widgets to enable Web Chat on every page. You must use Genesys Engage v3 API transport. For more information, see Configure widgets and services.
Obtain the API key from your Genesys customer service representative (x-api-key).
Use Live Now
Create engagement logic
Receive chats in Agent Desktop
To receive a live chat interaction, set your status to Available.
Expand the Journey tab and view a customer's journey.Additional integrations
Architect workflows
Administrators and contact center managers can now create workflows in Architect. This feature allows customers to streamline business processes by using Predictive Engagement to build in-house and third-party integrations.
For more information, see About Architect and Work with workflows.
Trigger architect flows
Predictive Engagement administrators can now use a new Architect flow action to configure action maps that trigger Architect flows that integrate with in-house and third-party systems. For more information, see About Architect flow actions.