Difference between revisions of "ATC/Current/AdminGuide/Action maps"
From Genesys Documentation
(Published) |
(Published) |
||
| Line 20: | Line 20: | ||
|Section={{Section | |Section={{Section | ||
|sectionHeading=High-level steps | |sectionHeading=High-level steps | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|alignment=Horizontal | |alignment=Horizontal | ||
|Media=Image | |Media=Image | ||
|image=GPE_create_action_map2_diagram.png | |image=GPE_create_action_map2_diagram.png | ||
| − | |structuredtext={{NoteFormat|1= | + | |structuredtext=<br />{{NoteFormat|1= |
*Some options are only available for certain actions. | *Some options are only available for certain actions. | ||
*To create an action map after you reach the limit of 200 action maps, delete an existing action map.|2=}}<ol> | *To create an action map after you reach the limit of 200 action maps, delete an existing action map.|2=}}<ol> | ||
| Line 49: | Line 30: | ||
<li>Select which action to use when the action map triggers: {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Create_messaging_offer|anchor=SelectAction|display text=web messaging}}, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Chat_offers|anchor=SelectWebChatAction|display text=web chat}}, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Configure_content_offer_action_map|anchor=SelectAction|display text=content offer}}, or {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Use_the_Architect_flow_with_an_action_map|anchor=SelectAction|display text=Architect flow}}.</li> | <li>Select which action to use when the action map triggers: {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Create_messaging_offer|anchor=SelectAction|display text=web messaging}}, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Chat_offers|anchor=SelectWebChatAction|display text=web chat}}, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Configure_content_offer_action_map|anchor=SelectAction|display text=content offer}}, or {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Use_the_Architect_flow_with_an_action_map|anchor=SelectAction|display text=Architect flow}}.</li> | ||
<li>Specify what {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Trigger|display text=triggers}} the action map (segment, visitor activity, outcome).</li> | <li>Specify what {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Trigger|display text=triggers}} the action map (segment, visitor activity, outcome).</li> | ||
| + | <li>{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Trigger|anchor=OutcomeProbability|display text=Configure an outcome probability}}. | ||
| + | </li> | ||
<li>Specify the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Apply|display text=webpages}} where you do or don't want the action map to trigger.</li> | <li>Specify the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Apply|display text=webpages}} where you do or don't want the action map to trigger.</li> | ||
<li>If the action map is for a web chat offer:</li> | <li>If the action map is for a web chat offer:</li> | ||
| Line 55: | Line 38: | ||
<li>To only present chat offers when agents are available to receive them, select a {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Schedules|display text=schedule group}}.</li></ol> | <li>To only present chat offers when agents are available to receive them, select a {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Schedules|display text=schedule group}}.</li></ol> | ||
<li>To ignore the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_settings|anchor=FrequencyCapping|display text=global frequency cap settings}} and always offer web engagements that this action map qualifies, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Override_frequency_capping|display text=override the frequency cap}} for this action map.</li> | <li>To ignore the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_settings|anchor=FrequencyCapping|display text=global frequency cap settings}} and always offer web engagements that this action map qualifies, {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Override_frequency_capping|display text=override the frequency cap}} for this action map.</li> | ||
| − | |Status= | + | |Status=No |
}}{{Section | }}{{Section | ||
|sectionHeading=AI-23 Add to High-level steps section | |sectionHeading=AI-23 Add to High-level steps section | ||
Revision as of 10:17, October 26, 2021
This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.
Contents
Learn how to create an action map that Genesys Predictive Engagement uses to engage visitors.
Prerequisites
- Configure the following permissions in Genesys Cloud:
- Journey > Action Map > Add, Delete, Edit, and View (to create action maps)
- Journey > Action Target > View (to select a team to handle interactions from the action map)
- Deploy one of the following:
- For Genesys Cloud customers using web messaging, configure and deploy Genesys Messenger.
- For all other customers, deploy the tracking snippet on the website to track so that you can trigger the action map based on pageview events. To trigger an action map based on other events, use ac('record') to send Genesys Predictive Engagement data about the events to track.
- Create segments.
- Create outcomes.
- Create the action.
High-level steps
Important
- Some options are only available for certain actions.
- To create an action map after you reach the limit of 200 action maps, delete an existing action map.
- Specify a descriptive name for the action map.
- Set the action map's priority relative to similar action maps.
- Select which action to use when the action map triggers: web messaging, web chat, content offer, or Architect flow.
- Specify what triggers the action map (segment, visitor activity, outcome).
- Configure an outcome probability.
- Specify the webpages where you do or don't want the action map to trigger.
- If the action map is for a web chat offer:
- To route the action map to a specific agent queue, select an agent queue.
- To only present chat offers when agents are available to receive them, select a schedule group.
- To ignore the global frequency cap settings and always offer web engagements that this action map qualifies, override the frequency cap for this action map.
Tip
The action map is active and ready to trigger on your site by default. To prevent the action map from triggering on your site, slide the toggle to No.Example: How to create an action map
This video shows how to create an action map for offering a proactive chat to visitors on your website.
Comments or questions about this documentation? Contact us for support!