Difference between revisions of "ATC/Current/AdminGuide/Chat offers"
From Genesys Documentation
DannaShirley (talk | contribs) (Published) |
DannaShirley (talk | contribs) (Published) |
||
| Line 13: | Line 13: | ||
|structuredtext=A Web chat engages your visitors through a standard chat window that proactively appears while visitors are on your website. | |structuredtext=A Web chat engages your visitors through a standard chat window that proactively appears while visitors are on your website. | ||
|fullwidth=No | |fullwidth=No | ||
| + | |Status=No | ||
}}{{Section | }}{{Section | ||
|sectionHeading=Offer Text | |sectionHeading=Offer Text | ||
| Line 22: | Line 23: | ||
|structuredtext=Specify the text that appears when the chat first appears. | |structuredtext=Specify the text that appears when the chat first appears. | ||
|fullwidth=No | |fullwidth=No | ||
| + | |Status=No | ||
}}{{Section | }}{{Section | ||
|sectionHeading=Questions | |sectionHeading=Questions | ||
| Line 31: | Line 33: | ||
|structuredtext=Specify the questions that the chat window asks the visitor. If the visitor must respond to a question before proceeding with the chat, select '''Required'''. | |structuredtext=Specify the questions that the chat window asks the visitor. If the visitor must respond to a question before proceeding with the chat, select '''Required'''. | ||
|fullwidth=No | |fullwidth=No | ||
| + | |Status=No | ||
}}{{Section | }}{{Section | ||
|sectionHeading=Apply to pages | |sectionHeading=Apply to pages | ||
| Line 62: | Line 65: | ||
/pureengage | /pureengage | ||
| + | |||
{{!}}} | {{!}}} | ||
| + | |Status=No | ||
| + | }}{{Section | ||
| + | |sectionHeading=Updates for Route chats to a team | ||
| + | |Type=Structured | ||
| + | |alignment=Vertical | ||
| + | |gif=No | ||
| + | |structuredtext=Configure how {{MINTYDOCSPRODUCT}} routes chats that this action map generates: | ||
| + | * {{#mintydocs_link:topic=Route_PureEngage|manual=AdminGuide|version=Current|link text=PureEngage}} | ||
| + | * {{#mintydocs_link:topic=Route_PureEngage|manual=AdminGuide|version=Current|link text=PureConnect}} | ||
| + | |fullwidth=No | ||
| + | |Status=Yes | ||
}}{{Section | }}{{Section | ||
|sectionHeading=Route chats to a team | |sectionHeading=Route chats to a team | ||
| Line 71: | Line 86: | ||
|image=WebChatRouteTo.png | |image=WebChatRouteTo.png | ||
|gif=No | |gif=No | ||
| − | |structuredtext= | + | |structuredtext=Click the team that receives chats from this action map. |
| − | |||
| − | |||
|fullwidth=No | |fullwidth=No | ||
| + | |Status=No | ||
}}{{Section | }}{{Section | ||
|sectionHeading=Priority | |sectionHeading=Priority | ||
| Line 84: | Line 98: | ||
|structuredtext={{MINTYDOCSPRODUCT}} uses only one action map at a time for a given segment. If two action maps of the same type target the same segment at the same time, then the priority determines which action map the visitor experiences.{{NoteFormat| If multiple action maps target the same segment at the same time, and they have the same priority, then {{MINTYDOCSPRODUCT}} will display each one a set percentage of the time. For example, if two action maps exist, then {{MINTYDOCSPRODUCT}} displays each one 50% of the time. If three action maps exist, then {{MINTYDOCSPRODUCT}} displays each one 33% of the time.|1}} | |structuredtext={{MINTYDOCSPRODUCT}} uses only one action map at a time for a given segment. If two action maps of the same type target the same segment at the same time, then the priority determines which action map the visitor experiences.{{NoteFormat| If multiple action maps target the same segment at the same time, and they have the same priority, then {{MINTYDOCSPRODUCT}} will display each one a set percentage of the time. For example, if two action maps exist, then {{MINTYDOCSPRODUCT}} displays each one 50% of the time. If three action maps exist, then {{MINTYDOCSPRODUCT}} displays each one 33% of the time.|1}} | ||
|fullwidth=No | |fullwidth=No | ||
| + | |Status=No | ||
}} | }} | ||
}} | }} | ||
Revision as of 12:46, March 28, 2019
This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.
Contents
Web chats present current promotions or important announcements to visitors via simple chat windows.
About WebChats
A Web chat engages your visitors through a standard chat window that proactively appears while visitors are on your website.
Offer Text
Specify the text that appears when the chat first appears.
Questions
Specify the questions that the chat window asks the visitor. If the visitor must respond to a question before proceeding with the chat, select Required.
Apply to pages
Use the fields to build an expression that tells Genesys Predictive Engagement where to display the chat.
The following table illustrates expressions that use the equals and like operators for the genesys.com platform.
| Operator | Note | Example expression | 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
|
Route chats to a team
Click the team that receives chats from this action map.
Priority
Genesys Predictive Engagement uses only one action map at a time for a given segment. If two action maps of the same type target the same segment at the same time, then the priority determines which action map the visitor experiences.
Important
If multiple action maps target the same segment at the same time, and they have the same priority, then Genesys Predictive Engagement will display each one a set percentage of the time. For example, if two action maps exist, then Genesys Predictive Engagement displays each one 50% of the time. If three action maps exist, then Genesys Predictive Engagement displays each one 33% of the time.Comments or questions about this documentation? Contact us for support!