Difference between revisions of "ATC/Current/AdminGuide/Action maps"
DannaShirley (talk | contribs) (Published) |
DannaShirley (talk | contribs) (Published) |
||
Line 3: | Line 3: | ||
|DisplayName=Action maps | |DisplayName=Action maps | ||
|Platform=PureEngage, PureConnect, PureCloud | |Platform=PureEngage, PureConnect, PureCloud | ||
+ | |ComingSoon=No | ||
|Context=An action map represents the steps {{MINTYDOCSPRODUCT}} takes when engaging with customers who meet certain criteria. | |Context=An action map represents the steps {{MINTYDOCSPRODUCT}} takes when engaging with customers who meet certain criteria. | ||
+ | |Prereq='''Prerequisites''' | ||
+ | * [https://help.mypurecloud.com/articles/altocloud-permissions-overview '''Journey '''>''' Action Map '''>''' Add''', '''Delete''', '''Edit''', and '''View''' permissions] (to create action maps) | ||
+ | * [https://help.mypurecloud.com/articles/altocloud-permissions-overview '''Journey '''>''' Action Target '''> '''View''' permission] (to select a team to handle interactions from the action map) | ||
|Section={{Section | |Section={{Section | ||
|sectionHeading=About action maps | |sectionHeading=About action maps | ||
Line 78: | Line 82: | ||
|Status=No | |Status=No | ||
}}{{Section | }}{{Section | ||
− | |sectionHeading=Trigger based on | + | |sectionHeading=Trigger based on user activity |
|Type=Structured | |Type=Structured | ||
|anchor=VisitorActivity | |anchor=VisitorActivity | ||
Line 84: | Line 88: | ||
|image=CustomerActivityPEPC.png | |image=CustomerActivityPEPC.png | ||
|gif=No | |gif=No | ||
− | |structuredtext=To trigger the action map based on what the | + | |structuredtext=To trigger the action map based on what the user does: |
− | # Under ''' | + | # Under '''Select trigger,''' click '''User activity'''. |
− | # Under '''Set conditions''', define the customer behavior you want to track. Use | + | # Under '''Set conditions''', define the customer behavior you want to track. Use a combination of {{Link-SomewhereInThisProduct|version=Current|manual=AdminGuide|topic=VisitorAttsJourney|display text=attributes and operators.}}<br /> |
− | {{NoteFormat|Specify as many | + | {{NoteFormat|Specify as many attributes as you want. {{MINTYDOCSPRODUCT}} evaluates them in the order in which you define them.|1}} |
|fullwidth=No | |fullwidth=No | ||
|Status=No | |Status=No |
Revision as of 10:39, May 17, 2019
Contents
- 1 About action maps
- 2 Prerequisites
- 3 Design action maps
- 4 View your action maps
- 5 Create an action map
- 6 Trigger based on user activity
- 7 Trigger based on segment assigned
- 8 Trigger based on outcome probability
- 9 Configure user engagement
- 10 Design the engagement
- 11 Apply to pages
- 12 Set the priority
- 13 Activate or inactivate the action map
- 14 Delete an action map
An action map represents the steps Genesys Predictive Engagement takes when engaging with customers who meet certain criteria.
Prerequisites
- Journey > Action Map > Add, Delete, Edit, and View permissions (to create action maps)
- Journey > Action Target > View permission (to select a team to handle interactions from the action map)
About action maps
AnNo results represents the steps that Genesys Predictive Engagement takes to engage selected customers to achieve a particular result. For example, you can create an action map that presents a chat to visitors who go to the page for your current promotional campaign. The chat might ask the customer whether they want to talk directly with someone in sales who could then help them complete their purchase.
When you create an action map, you define what triggers it. The types of triggers that you can define are:
- Who the customer is (what group or "No results" the customer belongs to)
- What actions the customer takes on your website
In addition, Genesys Predictive Engagement automatically triggers action maps based on a customer'sNo results.
Prerequisites
Before you create action maps:
Design action maps
When you design action maps, consider the following points:
- If a customer is progressing towards a business outcome, do not impede their progress by popping an unnecessary chat window. Intervene only when a customer's activity indicates that they are no longer on track to achieve the outcome you want.
- Genesys Predictive Engagement automatically tracks when a customer does any of the following things:
- Completes fields in a form
- Searches for something
- Responds to a chat offer
- Does not respond to a chat offer
- Initially responds to a chat offer but then remains inactive until the offer times out
- Genesys Predictive Engagement can also track custom events that you define. You can then configure the action map to trigger if one of these custom events occurs. For example:
- A customer adds an item to their shopping cart but then removed items or abandoned the shopping cart
View your action maps
- Click Admin.
- Under Altocloud, click Action Maps.
Create an action map
- Click Admin.
- Under Altocloud, click Action Maps.
- Click Create action map.
- In the Name box, give the action map a descriptive name.
- Define what triggers the action map:
- Define how Genesys Predictive Engagement should engage the customer.
Trigger based on user activity
To trigger the action map based on what the user does:
- Under Select trigger, click User activity.
- Under Set conditions, define the customer behavior you want to track. Use a combination of attributes and operators.
Trigger based on segment assigned
To trigger the action map based on the segment that the customer belongs to:
- Under Choose customer engagement, click Segment Assigned.
- Select the segments.
- To engage all visitors regardless of their segment, click All visitors.
- To engage visitors based on their segment, click the applicable segments.
- To create a new segment for this action map, click New segment.
Trigger based on outcome probability
Configure user engagement
- Select how Genesys Predictive Engagement interacts with a customer.
- Create a web chat offer present special opportunities to visitors in a chat window.
- Select when the engagement begins.
- Immediately
- After the visitor leaves and returns to the same page
- After a delay (in seconds or minutes)
- Configure the time range and end date.
Design the engagement
Apply to pages
The following table illustrates expressions that use the equals and like operators.
Operator | Note | Example | Matched pages |
equals | This operator requires a full URL. | equals:platform | https:www.genesys.com |
like | This operator accepts a partial URL. | like:platform | All pages on:
/pureconnect /purecloud /pureengage
|
Set the priority
Activate or inactivate the action map
When you create an action map, it is automatically activated. This means it is ready to trigger immediately on your site. To determine whether the action map triggers, use the Active switch which appears at the bottom of the page when you create or edit an action map.
To activate or inactivate an action map from the main Action Maps page:
- Click Admin.
- Under Altocloud, click Action Maps. Click the Active button for the action map so it is either On or Off.
Delete an action map
To delete an action map:
- Click Admin.
- Under Altocloud, click Action Maps.
- Click the Delete button for the action map.