About action maps

From Genesys Documentation
Revision as of 18:44, October 10, 2019 by DannaShirley (talk | contribs) (Published)
Jump to: navigation, search

Action maps define how Genesys Predictive Engagement interacts with users on your website.


Best practices

Improve your action maps by reviewing the overall process for building them and our suggested best practices.

Build an action map

Learn how to build and manage your action maps.

Trigger an action map

Understand how action maps are triggered. Configure an action map to trigger based on segment match or user activity.

Engage your users

Design how you want an action map to engage your users.

Define outcome probabilities

Altocloud uses AI to predict the actions your users will take. Help refine its modeling by identifying outcome probabilities.

Apply to webpages

An action map can trigger on any page where you use Genesys Predictive Engagement to track user activity. When you build an action map, you identify the webpages where it triggers.

Route the action map

Configure how Genesys Predictive Engagement routes users who are ready to work directly with a person.

Prioritize the action maps

Multiple action maps can potentially trigger on a webpage. To ensure that Genesys Predictive Engagement picks the most appropriate one, configure the priority for each action map.

Activate or inactivate

To temporarily prevent an action map from triggering, inactivate it.

  • [[ATC/Current/AdminGuide/Activate_inactivate|]]

Maintain action maps

Genesys Predictive Engagement provides several features for maintaining action maps.

Monitor action maps

Use analytics to assess the effectiveness of your action maps.

Comments or questions about this documentation? Contact us for support!