Frequently Asked Questions

Allowlists and the Digital DX AI platform

To use Genesys DX, you may want to allowlist certain URLs so that its connected services are able to connect.

We recommend you add the following URLs to your network's allowlist:

  • *.boldchat.com, *bold360.com, *.bold360usercontent.com  - Genesys' service for adding chat to websites
  • *.nanorep.co ? The site for customers who have access to the Bold360 AI platform (Service, Advise, and Acquire)
  • authentication.logmeininc.com, auth.bold360.com - LogMeIn's sign-in service
  • launch.bold360.com, myaccount.logmeininc.com, profile.logmeininc.com - LogMeIn's MyAccount page, where you can manage and access all your LogMeIn products

*** Please note that *.logmeininc.com domains and IP Addresses/ranges are only needed temporarily while the BoldChat/Bold360 platforms complete their migration to Genesys architecture.

Note: This list includes sub-domains for the listed domains, so it is advisable to use wildcard rules wherever possible when you allow or block any LogMeIn service on your network. Specifically, we recommend you to allow *bold360.com and *logmeininc.com. The services themselves communicate using port 443 (HTTPS/SSL) and port 80, so you don't need to open any additional ports within a firewall.

LogMeIn IP ranges

We recommend you add LogMeIn domains and URLs to your network's allowlist instead of allowing LogMeIn IP ranges. If that is not feasible, refer to the list of LogMeIn IP addresses.

CIDR Notation Numeric IP Range Netmask Notation
67.217.80.0/23 67.217.80.0 - 67.217.81.255 67.217.80.0 255.255.254.0
95.172.70.0/24 95.172.70.0 - 95.172.70.255 95.172.70.0 255.255.255.0
173.199.52.0/23 173.199.52.1 - 173.199.53.254 173.199.52.0 255.255.254.0

IP addresses for the sign in service

To sign in to your Bold360 work environment, you must allow LogMeIn's sign-in service. To do that by IP addresses, add the following IPs to your firewall settings:

  • 34.199.209.240
  • 35.173.84.18
  • 78.108.120.24
  • 173.199.2.47
  • 173.199.4.47

Email addresses for the sign in service

Make sure you allow the following email addresses so that identity-related and authentication emails are received:

  • noreply@logmein.com
  • support@bold360.com

Third-party IP Ranges

You must also allowlist ranges for these third-party services based upon your use of these service providers:

Email Domains

For email invitations and correspondences from us and the BoldChat/Bold360 software, we recommend allowing the following email domains through your email's spam and allowlist filters.

  • noreply@logmein.com
  • support@bold360.com

*** Please note that *.logmeininc.com domains and IP Addresses/ranges are only needed temporarily while the BoldChat/Bold360 platforms complete their migration to Genesys architecture.

 

Update as of January 18, 2022

Beginning on October 9, 2021, additional changes are taking place as part of the migration process of the DX platform from LMI to Genesys. The failover will take place in 3 stages from LMI on-premise data centers to Genesys cloud-based environment which provides robustness, flexibility and better scalability to the DX platform.

[ACTION] - If you allow list Agent (formerly known as BoldChat) by domain (preferred to DNS or IP allowlisting), you will need to allowlist the following domains in your organization's network/firewall:

  • bold360.com
  • boldchat.com

Alternatively, you can allowlist the following DNS servers:

Ireland

  • eub-app16-01.boldchat.com
  • eub-app16-02.boldchat.com
  • eub-app16-03.boldchat.com
  • eub-app16-04.boldchat.com
  • eub-app16-05.boldchat.com
  • eub-app16-06.boldchat.com
  • eub-app16-07.boldchat.com
  • eub-app16-08.boldchat.com
  • eub-app16-09.boldchat.com
  • eub-app16-10.boldchat.com
  • eub-app16-11.boldchat.com
  • eub-app16-12.boldchat.com

Frankfurt

  • eub-app17-01.boldchat.com
  • eub-app17-02.boldchat.com
  • eub-app17-03.boldchat.com
  • eub-app17-04.boldchat.com
  • eub-app17-05.boldchat.com
  • eub-app17-06.boldchat.com
  • eub-app17-07.boldchat.com
  • eub-app17-08.boldchat.com
  • eub-app17-09.boldchat.com
  • eub-app17-10.boldchat.com
  • eub-app17-11.boldchat.com
  • eub-app17-12.boldchat.com

US East (N. Virginia)

  • b-app18-01.boldchat.com
  • b-app18-02.boldchat.com
  • b-app18-03.boldchat.com
  • b-app18-04.boldchat.com
  • b-app18-05.boldchat.com
  • b-app18-06.boldchat.com
  • b-app18-07.boldchat.com
  • b-app18-08.boldchat.com
  • b-app18-09.boldchat.com
  • b-app18-10.boldchat.com
  • b-app18-11.boldchat.com
  • b-app18-12.boldchat.com
  • b-app18-13.boldchat.com
  • b-app18-14.boldchat.com
  • b-app18-15.boldchat.com
  • b-app18-16.boldchat.com
  • b-app18-17.boldchat.com
  • b-app18-18.boldchat.com
  • b-app18-19.boldchat.com
  • b-app18-20.boldchat.com
  • b-app18-21.boldchat.com
  • b-app18-22.boldchat.com
  • b-app18-23.boldchat.com
  • b-app18-24.boldchat.com
  • b-app18-25.boldchat.com
  • b-app18-26.boldchat.com
  • b-app18-27.boldchat.com
  • b-app18-28.boldchat.com
  • b-app18-29.boldchat.com
  • b-app18-30.boldchat.com
  • b-app18-31.boldchat.com
  • b-app18-32.boldchat.com
  • b-app18-33.boldchat.com
  • b-app18-34.boldchat.com
  • b-app18-35.boldchat.com
  • b-app18-36.boldchat.com
  • b-app18-37.boldchat.com
  • b-app18-38.boldchat.com
  • b-app18-39.boldchat.com
  • b-app18-40.boldchat.com
  • b-app18-41.boldchat.com
  • b-app18-42.boldchat.com
  • b-app18-43.boldchat.com
  • b-app18-44.boldchat.com
  • b-app18-45.boldchat.com
  • b-app18-46.boldchat.com
  • b-app18-47.boldchat.com
  • b-app18-48.boldchat.com
  • b-app18-49.boldchat.com
  • b-app18-50.boldchat.com
  • b-app18-51.boldchat.com
  • b-app18-52.boldchat.com
  • b-app18-53.boldchat.com
  • b-app18-54.boldchat.com
  • b-app18-55.boldchat.com
  • b-app18-56.boldchat.com
  • b-app18-57.boldchat.com
  • b-app18-58.boldchat.com
  • b-app18-59.boldchat.com
  • b-app18-60.boldchat.com

US West (Oregon)

  • b-app19-01.boldchat.com
  • b-app19-02.boldchat.com
  • b-app19-03.boldchat.com
  • b-app19-04.boldchat.com
  • b-app19-05.boldchat.com
  • b-app19-06.boldchat.com
  • b-app19-07.boldchat.com
  • b-app19-08.boldchat.com
  • b-app19-09.boldchat.com
  • b-app19-10.boldchat.com
  • b-app19-11.boldchat.com
  • b-app19-12.boldchat.com
  • b-app19-13.boldchat.com
  • b-app19-14.boldchat.com
  • b-app19-15.boldchat.com
  • b-app19-16.boldchat.com
  • b-app19-17.boldchat.com
  • b-app19-18.boldchat.com
  • b-app19-19.boldchat.com
  • b-app19-20.boldchat.com
  • b-app19-21.boldchat.com
  • b-app19-22.boldchat.com
  • b-app19-23.boldchat.com
  • b-app19-24.boldchat.com
  • b-app19-25.boldchat.com
  • b-app19-26.boldchat.com
  • b-app19-27.boldchat.com
  • b-app19-28.boldchat.com
  • b-app19-29.boldchat.com
  • b-app19-30.boldchat.com
  • b-app19-31.boldchat.com
  • b-app19-32.boldchat.com
  • b-app19-33.boldchat.com
  • b-app19-34.boldchat.com
  • b-app19-35.boldchat.com
  • b-app19-36.boldchat.com
  • b-app19-37.boldchat.com
  • b-app19-38.boldchat.com
  • b-app19-39.boldchat.com
  • b-app19-40.boldchat.com
  • b-app19-41.boldchat.com
  • b-app19-42.boldchat.com
  • b-app19-43.boldchat.com
  • b-app19-44.boldchat.com
  • b-app19-45.boldchat.com
  • b-app19-46.boldchat.com
  • b-app19-47.boldchat.com
  • b-app19-48.boldchat.com
  • b-app19-49.boldchat.com
  • b-app19-50.boldchat.com
  • b-app19-51.boldchat.com
  • b-app19-52.boldchat.com
  • b-app19-53.boldchat.com
  • b-app19-54.boldchat.com
  • b-app19-55.boldchat.com
  • b-app19-56.boldchat.com
  • b-app19-57.boldchat.com
  • b-app19-58.boldchat.com
  • b-app19-59.boldchat.com
  • b-app19-60.boldchat.com
     

[ACTION] - If you allow-list Agent (formerly known as BoldChat) by IP, here are the IPs you will need to allow list in your organization in order to avoid connectivity issues with the new Data Center on March 5th:

Ireland

  • 34.246.13.84
  • 54.155.23.252
  • 46.137.48.149
  • 34.254.28.102 5
  • 2.49.80.82
  • 63.33.229.51
  • 54.75.218.75
  • 54.216.206.26
  • 34.246.145.123
  • 52.212.90.186 5
  • 4.77.148.81
  • 34.251.74.92

Frankfurt

  • 3.122.210.241
  • 18.192.113.151
  • 3.68.175.68
  • 18.196.140.195
  • 3.68.178.202
  • 18.194.200.171
  • 18.198.110.95
  • 18.192.7.127
  • 3.65.55.253
  • 3.64.238.21
  • 3.64.109.185
  • 18.198.123.19

US East (N. Virginia)

  • 107.20.174.150
  • 18.214.187.122
  • 18.233.1.191
  • 18.233.79.13
  • 18.233.95.16
  • 18.235.217.246
  • 23.20.109.244
  • 23.20.253.55
  • 23.21.167.45
  • 3.225.82.217
  • 3.231.116.10
  • 3.233.101.193
  • 3.233.111.68
  • 3.89.11.143
  • 34.194.220.164
  • 34.195.70.224
  • 34.206.233.8
  • 34.224.220.30
  • 34.228.50.168
  • 34.230.132.34
  • 34.234.140.16
  • 34.236.195.183
  • 34.236.241.191
  • 34.236.83.24
  • 35.153.29.169
  • 35.168.4.139
  • 35.174.34.186
  • 35.175.163.252
  • 44.193.104.84
  • 44.193.127.42
  • 44.193.247.199
  • 44.194.100.181
  • 44.194.137.67
  • 44.194.208.207
  • 44.194.25.105
  • 44.194.73.45
  • 44.195.9.217
  • 52.20.221.203
  • 52.207.76.221
  • 52.3.185.243
  • 52.44.154.238
  • 52.71.46.102
  • 52.71.71.29
  • 52.86.214.10
  • 54.144.250.111
  • 54.147.215.157
  • 54.152.188.62
  • 54.156.114.221
  • 54.156.48.172
  • 54.160.133.4
  • 54.160.196.54
  • 54.161.46.241
  • 54.163.230.72
  • 54.164.146.233
  • 54.166.248.29
  • 54.198.148.121
  • 54.226.231.169
  • 54.236.144.76
  • 54.84.163.19
  • 75.101.233.126

US West (Oregon)

  • 34.210.135.97
  • 34.213.254.212
  • 35.160.120.77
  • 35.161.150.98
  • 35.167.75.41
  • 35.80.158.24
  • 35.80.170.11
  • 35.80.194.13
  • 35.80.219.155
  • 35.81.101.126
  • 35.81.88.49
  • 35.82.204.234
  • 35.82.9.197
  • 35.83.116.129
  • 44.224.251.121
  • 44.226.244.84
  • 44.228.212.110
  • 44.230.126.250
  • 44.230.250.92
  • 44.231.153.96
  • 44.231.91.181
  • 44.232.19.77
  • 44.233.171.9
  • 44.237.129.5
  • 44.237.13.169
  • 44.237.28.122
  • 44.237.55.136
  • 44.238.219.222
  • 44.239.247.221
  • 44.241.208.142
  • 44.242.45.116
  • 44.242.53.108
  • 52.11.10.7
  • 52.12.160.123
  • 52.12.220.61
  • 52.13.124.118
  • 52.24.130.127
  • 52.32.198.76
  • 52.32.241.86
  • 52.35.142.151
  • 52.36.48.105
  • 52.38.106.12
  • 52.38.150.246
  • 52.40.239.227
  • 52.40.30.115
  • 52.41.198.141
  • 52.41.47.191
  • 54.184.129.107
  • 54.184.178.79
  • 54.184.90.24
  • 54.188.53.58
  • 54.200.230.213
  • 54.200.68.184
  • 54.201.26.44
  • 54.203.206.223
  • 54.212.170.137
  • 54.212.95.24
  • 54.69.131.234
  • 54.69.177.37
  • 54.69.85.11
     

Set up an email account

Configure Digital DX to receive, track, and manage emails.

  1. Create or edit an email account, as follows:
    1. In the Web Admin Center, go to Channels > Email > Email Accounts. The Email Accounts window is displayed.
      Note: To verify that an email account is set up properly, click Test next to an account.
    2. Select an existing account or click Create New. The New/Edit Email Account page is displayed.
  2. Select Enable email to activate the email account.
  3. Enter basic account settings on the General tab:
    Option Description
    Configuration Name Name the account for internal reference.
    Sender Email Address To use when sending email.
    Friendly Sender Name Used as the From Email Name when sending emails via this account. For example: Support Team, Jane Doe.
    Email client

    Select the email client you are using: MS Office 365 / Gmail / Other.

    The MS Office 365 and Gmail options don't only support the recommended OAuth 2.0 authentication, the Other option supports any client with basic authentication.

  4. Select the email client that you use to communicate over email.
    Note: In the Digital DX Desktop Client, you cannot select email client.
  5. Depending on your email client, you have the following options:
    Option Description
    User Name User name of the email server. For example, in the email address support@acme.com, the user name is support.
    Password The password associated with the user name for the POP3 server. Only available when you select Other for email client type.
    Server/Port Enter the host name or IP address and port of your mail server. If your email address is support@acme.com, then your mail server host name is normally mail.acme.com or just acme.com. All inbound emails are retrieved from this POP3 server.
    Secure Connection (SSL) To use a secure connection to your mail server, check Secure Connection (SSL) and enter the Port to be used for the connection. Check with your service provider as required.
    Type Choose your server type: POP3 or IMAP.
    Note: POP3 is unavailable for Microsoft Office 365 users.
    Leave copy of messages on server Store copies of emails on your POP3 server to facilitate download to Outlook or any other mail client.
    Folder Click Refresh folder list and then select the folder in your email account that you want to use for email communication with your customers.
    Tenant ID You Microsoft Tenant ID that you can find in the Azure AD admin center. (in the Directory ID field on the Properties page). Only available for Microsoft Office 365 users.
    Client ID
    • Microsoft Office 365 users find it in the Overview page of the Azure AD admin center
    • Gmail users find it on the APIs & Services > Credentials page Google Cloud Platform
    Client Secret Your client secret that you can find right next to your client ID. Only available for Microsoft Office 365 and Gmail users.
    Outgoing server Select SMTP server to set up an SMTP server for outgoing email.
  6. Optional: (Optional) Enter additional settings on the Distribution - Organization tab:
    Option Description
    Department Associate a Department with the email account. The Department can be used to override account-level automatic distribution settings and to determine which agents can be assigned emails by the automatic distribution system.
    Maintain email thread ownership on new mails Preserve the Owner (agent) field of each email thread.
    Append email thread ID to subject Append the Email Thread ID to the subject of replies. This make it easier to keep track of conversations with customers.
    Append email thread ID to subject Append the Email Thread ID to the subject of replies. This make it easier to keep track of conversations with customers.
    Auto-bcc Specify an email address that is included in the BCC field of all outbound emails from the agent.
  7. Optional: (Optional) Enter additional settings on the Format and content tab:
    Option Description
    Encoding Encoding for outgoing and incoming messages.
    Format Choose to show incoming email as either plain text or HTML.
    Canned messages for emails Select canned message folders that agents can use with email.
    Email Footer Enable and design a footer that is appended to all emails sent from this email account.
  8. Save your changes.
  9. For Gmail and MS O365 integrations, go to the recently added email account on the Email Account view and select the Authorize option.

    Complete the steps in the dialog that appears. Once the authentication is complete, the status of the email channel changes to Ready.

How to enable video chat

Allow agents to chat with your visitors face to face. During video sessions, either both parties or only operators can stream video.

Who can use this feature?

  • Video chat is available on request for Premier or Enterprise subscribers. Contact your representative for details and pricing.
  • Operators can use video chat in the web client at web.boldchat.com only.
  • Visitors and operators must use Chrome for Android on mobile, or any of the last 20 versions of Chrome on desktop. Firefox, Safari, Internet Explorer and Edge are not supported at this time.
Note: Video chats are never recorded; however, when Speech-to-Text is enabled, the transcribed text remains available in the chat history.

What are the technical requirements to use video chat?

Requirement Details
Allowlisting and open ports

From both the support agent's and the customer's network, the following web resources need to be accessible:

  • *.bold360.com
  • For networks explicitly filtering outbound destination ports and protocols, the following ports are used on Bold media sessions:15000 (UDP traffic) or 443 (TCP traffic) for Bold media sessions
    Tip: It is recommended that you allow UDP traffic through port 15000. Restricting the traffic to TCP may decrease the quality of the Bold support experience.
Fix IP
  • 52.154.166.133
  • 20.106.8.231
  • 20.221.16.142
  • 20.109.225.86
  • 20.82.12.159
  • 20.103.243.187
  • 20.126.246.165
  • 20.76.254.181
Bandwidth You need a working internet connection with stable 0.5 Mbps download and 0.8 Mbps upload bandwidth.
  • Minimum quality (640x480) - ~164 KBytes/sec, both for inbound and outbound video chat (depends on whether one-way or two-way video streaming is used)
  • HD quality (720p) ? ~492 KBytes/sec
  • Full HD quality (1080p) - ~984 KBytes/sec
  • Type/bandwidth: jitsi/webrtc

Configuring the chat window

This feature is part of the Custom Chat Window definition process. A chat window definition controls the look and feel and advanced behavior of the interface that is opened when a visitor clicks an associated button or link. When enabled, video options are displayed at the bottom of the chat window.

Restriction: For security reasons, recent versions of Chrome and Firefox require that any website that implements Powerful Features, such as voice or video, must be served over a secured connection (HTTPS). BoldChat communications are always encrypted, so video chat will be launched in a separate secure window if your website is unsecured (HTTP) and the visitor is on a browser that restricts powerful features.

If you are running an HTTP site with BoldChat, we recommend that you make the switch to HTTPS:

  1. Using the BoldChat Operator Client, create a new custom chat window, as follows:
    1. From the main menu of the BoldChat Operator Client, go to Setup > Account Setup. The Account Setup window is displayed.
    2. On the left menu of the Account Setup window, click Chats > Custom Chat Windows > New

    Result: The New Custom Chat Window is displayed.

  2. On the New Custom Chat Window window, make sure you are on the Chat Form tab.
    Note: Video chat is only available for layered chat windows.
  3. To activate video chat for any layered window on either desktop or mobile, select Video Chat.

    Result: Additional options are displayed.

  4. Additional options:
    • Operator Video Only: Only the operator can stream video. Audio is two-way, but video is one-way. Use this to prevent visitors from accidentally showing themselves.
    • Go Directly to Video Setup: The camera setup window is displayed to the visitor after they click the video chat button and complete the pre-chat form (if applicable). The visitor can choose video settings before calling the operator.
    • Multiple Visitor Confirmations: When enabled, the visitor is shown an additional prompt before chat begins. Use this for enhanced visitor privacy.
    • Speech-to-Text: This feature transcribes the conversation between the operator and the visitor in real time using Google's Web Speech API. Language is automatically detected based on the chat window's language setting that takes into account each participant's IP address and HTTP header. The actual spoken language may not always be accurately detected. Transcribed messages are excluded from the chat transcript and are accessible only to the operator in the Message History panel, marked with STT.
      Note: The accuracy of speech recognition is influenced by the visitor's acoustic environment, microphone quality, connection bandwidth, clarity of speech and pronunciation. In adverse conditions, transcription quality may degrade and affect the operator's chat experience.

We recommend that you use different machines for testing video chat as operator and visitor.

Having problems?

Check the following.

Symptom Action
Video chat is not available. Are you using the web client in a compatible browser? Video is only supported in Chrome version 31 or newer. If you are using the BoldChat Operator Client, go to https://web.boldchat.com/.
Webcam and/or audio access is blocked in the browser.
  1. Click the camera icon in the address bar to bring up the device permissions dialog.
  2. Ensure that either the Always allow... or Continue allowing... option is selected.
  3. Click Done.

You will not be asked again once you have given permission to access your devices.

If the issue persists, check that access to devices is not being blocked globally.

  1. Go to Settings > Show advanced settings....
  2. Under Privacy, click Content settings....
  3. Ensure that Ask when a site requires access... is selected under both Microphone and Camera.
  4. Click Manage exceptions... to ensure that BoldChat hosts are not being blocked.
  5. Click Done.
Note: You may need to reload the page for the permission settings to take effect.
Video is stuttering or breaking up. Video chat is bandwidth-intensive. Check your network connectivity and quit any application that may produce high network traffic.
Video is blank or there is no audio.
  • Clear your browser's cookies.
  • Are your drivers up-to-date? Install the latest drivers for your devices.
  • Are other applications using your webcam? Multiple capture may not be supported by your system. Ensure that the webcam light is off before starting the chat and quit all potentially interfering applications.
  • Are both audio and video streams enabled? Check the media controls.
Video chat starts in a popup window. Your site is served over an unsecured (HTTP) connection. See Configuring the chat window for how to fix the problem.

List of cookies used by BoldChat

BoldChat makes use of the cookies listed in this article.

BoldChat cookies track the actions associated with a website visitor's activity on this website to allow the website owner to provide accurate, helpful and feature-rich web chat features. This data is handled as follows:

  • Suppressible by the visitor who limits browser cookies
  • Used to identify behavior of a user on the website for purposes of BoldChat web chat features (e.g. aggregated performance/analytics reporting, chat, visit, conversion history individual reporting)
  • Only useful during the visit or upon a subsequent visit
  • Not available between customers
  • Protected by the BoldChat secure infrastructure

The first five (5) are targeting types for uniquely identifying the website user within the BoldChat service and are used for things like targeted chat invitation, allowing a chat agent to better assist the website visitor during a chat session, and for aggregate reporting. The latter four (4) are strictly necessary and only used for chat-related functionality.

Cookie _bcvm_vid_XXXXXX
Host 1st Party Website
Type 1st Party
Category Performance/Functionality
Expiration End of session
Purpose Stores a unique, anonymous identifier (VisitID) to allow the BoldChat system to recognize a particular browsing session or visit to the website.
Creation When the website user loads a page containing the BoldChat chat button/visitor monitoring script or when a chat session launches.
Cookie _bcvm_vrid_XXXXXX
Host 1st Party Website
Type 1st Party
Category Performance/Functionality
Expiration 1 year
Purpose Stores a unique, anonymous identifier (VisitorID) to allow the BoldChat system to recognize the website user during current and subsequent visits to the website.
Creation When the website user loads a page containing the BoldChat chat button/visitor monitoring script or when a chat session launches.
Cookie bc_pv_end
Host 1st Party Website
Type 1st Party
Category Performance/Functionality
Expiration 30 seconds
Purpose Improves accuracy of pageview tracking when a website user (visitor) moves between pages.
Creation When the website user changes pages.
Cookie bc-visit-id
Host boldchat.com
Type 3rd Party
Category Performance/Functionality
Expiration End of session
Purpose Same as _bcvm_vid_XXXXXX. Stores a unique, anonymous identifier (VisitID) to allow the BoldChat system to recognize a particular browsing session or visit to the website.
Creation When the website user loads a page containing the BoldChat chat button / visitor monitoring script or when a chat session launches.
Cookie bc-visitor-id
Host boldchat.com
Type 3rd Party
Category Performance/Functionality
Expiration 1 year
Purpose Same as _bcvm_vrid_XXXXXX. Stores a unique, anonymous identifier (VisitorID) to allow the BoldChat system to recognize the website user during current and subsequent visits to the website.
Creation When the website user loads a page containing the BoldChat chat button / visitor monitoring script or when a chat session launches.
Cookie _bc-curl
Host 1st Party Website
Type 1st Party
Category Strictly Necessary
Expiration End of session
Purpose Identifies the state of the layered chat window when the website user changes pages on the website so the chat window can be maintained.
Creation When the layered chat window is opened.
Cookie _url-cid
Host livechat.boldchat.com
Type 3rd Party
Category Strictly Necessary
Expiration End of session
Purpose Used to identify the cached url of the open chat window for the website user.
Creation When the layered chat window is opened.
Cookie _bc_aa*

(_bc_aas, _bc_aaq, _bc_aasi-XXX-XXX-viewed, _bc_aasc)

Host livechat.boldchat.com
Type 3rd Party
Category Strictly Necessary
Expiration End of session
Purpose Used to identify the current state of auto-answers being shown to the website user within the chat window.
Creation When auto-answers is shown and used within the chat window, and only if Local Storage is not supported by the browser.
Cookie _reboot-cid
Host livechat.boldchat.com
Type 3rd Party
Category Strictly Necessary
Expiration End of session
Purpose Used to track the chat url to be reloaded after a Rescue-initiated reboot (in order to reconstitute the chat session).
Creation When a Rescue-initiated reboot is triggered.

What do I see on the Engagements Dashboard?

The Engagements Dashboard shows the total number of engagements, engagement-related metrics, and offers a detailed view on individual engagements.

By reviewing experiences that share an outcome, for example, channeled engagements, you may gain insights into how to further drive optimization.

With this dashboard you can gain insights into the following:

  • Total number of engagements
  • Engagement self-service score
  • Deflection rate
  • Engagement trend
  • Other details about engagements such as the amount of channeled engagements, engagements with positive or negative feedback and so on
  • Details about the user?s journey such as the date and time of the engagement, the event type, and the user query

You can do the following with the data on this dashboard:

  • Change the time interval to see a subset of the data
  • Select specific knowledge bases to see data for that knowledge base
  • Create bookmarks with the filters you set
  • View the individual widgets or the Engagement Summary table in full screen
  • Download the content of the dashboard, the individual widgets, or the Engagements summary table to pdf
  • Hide columns and use drag-and-drop to change the order of columns in the Engagements summary table
  • Select a number or a percentage in a cell in the Engagements summary table to see the details of the user?s journey for each engagement

What is an engagement?

An engagement is a collection of end user events with the bot, with a live agent or both where the longest interruption between two events is no longer than 30 minutes.

An engagement is a user's visit in which a Bold360 capability was used at least once. An engagement may include a variety of events incorporating both Bold360 AI and Bold360 Agent events. Such events can be typing a question, selecting an article, messaging with a live agent, or filling in a chat feedback form. An engagement ends after 30 minutes of idle time.

The engagement calculator service is continuously monitoring incoming raw events and determines if an event is part of an active engagement or belongs to a new one.

What is a proactive engagement?

Proactive engagements are triggered by proactive strategies or campaigns. They are not initiated by the visitor or the agent.

What is the engagement self-service score and how is it calculated?

Engagement self-service score indicates whether the user was able to achieve their objective through self-service. It is calculated by dividing the number of engagements without negative signals with the total number of engagements.

An engagement is self-served if it meets the following criteria:

  • It doesn't include a channeling event
  • It doesn't include a negative feedback event
  • The bot was able to answer at least one user question

The engagement self-service score is expected to be lower than the interaction self-service score. Both engagements and interactions are a certain type of event grouping, with different levels of granularity. In practice, each engagement includes one or more interactions. Therefore, a single negative signal for an interaction has higher impact on engagement self-service score than on interaction self-service score.

For example, if an engagement with five interactions receives a single negative signal, we get 0% engagement self-service score and 80% interaction self-service score.

What is the deflection rate and how is it calculated?

Deflection rate shows the extent to which automated and self-help resources satisfy service demand that would otherwise be handled by support staff. It is calculated by dividing engagements without channeling events with the total number of engagements and is shown as a percentage.

What data does the Engagement Summary table contain and how are they calculated?

The Engagement Summary table shows the following pieces of information about engagements:

  • Channeled: percentage of engagements that contain at least one channeling event like chat, ticket, or phone.
  • Positive feedback: percentage of engagements that contain at least one positive feedback event.
  • Negative feedback: percentage of engagements that contain at least one negative feedback event.
  • Channeled to agent: percentage of engagements that are channeled to an agent.
  • Agent only: percentage of engagements that include agent live chat only.

What time interval is used on this dashboard?

Engagement data for the current month and the previous three months is available on this dashboard. The exact time interval is displayed under the Engagement Summary table. You can look at subsets of the data within this time interval by using the Date filter. By default, the dashboard displays engagement data for the last seven days.

How often is the data updated?

The data on this dashboard is updated one a day. The last update time is displayed at the top, above the Engagement trend widget.

How to create an API key in Bold360 AI

API keys enable you to utilize the API capabilities of Bold360 AI.

An API key is a unique identifier that you can use to integrate other systems like Bold360 Agent with Bold360 AI. You can define multiple API keys, and each one may have its own permissions.

  1. In the AI Console, go to Admin Center > API keys and select Add API Key.

  2. Name your API key at the top of the page.

    Example: If you're creating an API key for integration with Bold360 Agent, you could use the Bold360 Live Chat name.

  3. Under Permissions, select the permissions for this API key.

    Example: If you're creating an API key for integration with Bold360 Agent, grant Write access for all categories.

    Important: If you define Write permissions, restrict access to either IP ranges or referrer domains.
  4. Under Allowed knowledge bases, select the knowledge bases that this API key can access.
  5. Under Allowed IP ranges, you can restrict access to specific IP addresses or ranges.

    Enter either a single IP or a range of IPs. You can define one IP or an IP range per line. If you don't want to apply restrictions, you can indicate by enabling Allow All IP Ranges or by entering 0.0.0.0-255.255.255.255.

  6. Under Allowed referrers, you may restrict access to requests originating from specific referrer domains.

    Enter one domain per line.

  7. Choose Generate API Key.
What's Next? Copy the API key to use it during setting up the integration. Follow these steps to integrate Bold360 AI with Bold360 Agent.

Announcements

Join the DX Community!

Meet fellow DX pros, ask questions, and learn best practices.

Join the DX Community

Featured

Bold360 22.4 Release

The Bold360 22.4 release contains various bug fixes and support defects for the AI elements of the Bold360 platform.

The release is scheduled to begin on April 2nd, 2022