ATC/Current/AdminGuide/Chat offers

Web chats present current promotions or important announcements to customers via simple chat windows.

Prerequisites

• Configure the following permissions in PureCloud:
  • 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)

Overview

A web chat is aNo results that engages your customers through a standard chat window that proactively appears while they are on your website.

To create a web chat, start by creating an action map that uses a web chat as its method of customer engagement. To design a web chat, you define the:

• Timing
• Chat offer
• Chat window

Chat offer

1. Specify the Offer title text. This text appears in the title bar of the chat.
2. Specify the Offer text. This text invites the customer to chat.
3. Specify the Accept button caption. This text appears on the button that accepts the chat offer.
4. Specify the Decline button caption This text appears on the button that declines the chat offer.
5. Click Next: Chat window.

Chat window

Your chat window includes fields that capture essential information about your customers. For example:

• Company name
• Email
• Family name
• Gender
• Given name
• Phone number

We have pre-configured several fields for you. However, you can configure the fields in the chat window however you like.

1. From the list, select the type of information.
2. In the box, type the label that customers see.
3. To make a field required, select the Required box.
4. To delete a field, click Delete.
   Important

   PureEngage: Your chat window fields must include both the Given Name and Family Name fields. These correspond to the First Name and Last Name fields in PureEngage. Web chats without this information will fail to start.
5. To add another field, click Add More.
6. When you are finished, click Done.

Monitor a web chat's performance

Use the Action Map Performance report to monitor your web chats. The following table defines the available metrics for this report:

Metric	Description
Web Actions Qualified	Number of visitors who matched a segment, activity, or outcome score that triggered the action map.
Web Actions Offered	Number of visitors to whom Genesys Predictive Engagement offered a web chat. Note: When a visitor qualifies for an action map, it does not necessarily mean that Genesys Predictive Engagement offers them a web chat immediately. For example, Genesys Predictive Engagement does not offer a web chat if the visitor matches a segment for the action map, but is not on the webpage that triggers the action. Genesys Predictive Engagement also does not offer a web chat if there are no agents available. For more information, see Progression of web actions metrics.
Web Actions Accepted	Number of visitors who accepted a web chat. These visitors are a subset of those to whom Genesys Predictive Engagement offered a web chat. For more information, see Progression of web actions metrics.
Web Actions Started	Not applicable
Web Actions Engaged	Not applicable
Web Actions Rejected	Number of visitors who dismissed or rejected an offer to chat. These visitors are a subset of those to whom Genesys Predictive Engagement offered a web chat.
Web Actions Errored	Number of visitors who experienced an error while being offered a web chat. This can happen before or after a web chat is offered.
Web Actions Timed Out	Not applicable

Progression of web chat metrics

This illustration shows when Genesys Predictive Engagement updates metrics after extending a web chat offer to a visitor.