Web Admin Articles

What cookies and local storage entities are used by Digital DX AI widgets?

The following table lists all customer-side cookies used in widgets to provide reporting and analytics capabilities. Customers stay anonymous and their unique visitor IDs are only used to group customer queries in reports.

Cookie name Example value Description
bc.visitor_token 5d1ab47f-f7de-14c9-0045-b8d7c8a7c18b Identifies the visitor in Business Insights, used also when navigating across subdomains and by the customer information hub.
u v2,EU1,38DA82AC634C0F31 The cookie is used by visitors' engagement tracking in Bold360Ai's reporting system and leveraged by internal analytics tools. If the 'u' cookie is blocked, then the Engagement and Interaction data in legacy AI reporting is distorted.
35EBBB48 cv_4#t_ED43D8F69#v_1#lv_ ED43D8F57#e_00000000 Legacy visitor journey tracking cookie. There is one cookie per visitor journey.

Digital DX AI also uses customer-side localStorage entities in Conversational widgets to provide widget state persistence. You can change it to sessionStorage with the public widget API, but the content of the storage remains the same:

Storage key Storage value Description
bc.visitor_token 5d1ab47f-f7de-14c9-0045-b8d7c8a7c18b To provide better persistence and reporting, the unique visitor token is also currently stored in the localStorage of the customer's website.
nanorep.float.conversational. product_demo.kb904641352 {"convId":"7835951554271442645", "convLog":[...]} Stores widget state, including current conversation ID, chat history, active live-chat channel information and so on.


List of cookies used by Digital DX

Genesys DX/Bold360 cookies track the actions associated with a website customer'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 customer who limits browser cookies
  • Used to identify behavior of a user on the website for purposes of Digital DX 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 Digital DX secure infrastructure

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

Personalization

This cookie is used for providing the proper content based on context settings (query parameter).

Cookie nrContext2
Host 1st Party Website
Type 1st Party
Category Performance/Functionality
Expiration End of session
Purpose Bold360Ai is providing context-based, tailored content to customers in order to find the most relevant answers to their problem. The 'nrContext2' cookie is stored for collecting the right context from the user's machine.  
Creation When the website user loads a page containing a chat button/customer monitoring script or when a chat session launches.

Harmony

These cookies are used for seamless integration of AI interactions (search, botchat) and live agent chats.

Cookie _bc-chat-ended
Host 1st Party Website
Type 1st Party
Category Performance/Functionality
Expiration End of session
Purpose Stores a unique, anonymous identifier (VisitID) to allow Digital DX to recognize a particular browsing session or visit to the website.
Creation When the website user loads a page containing a chat button/customer monitoring script or when a chat session launches.
Cookie _bcContinueChat
Host 1st Party Website
Type 1st Party
Category Performance/Functionality
Expiration End of session
Purpose Stores a unique, anonymous identifier (VisitID) to allow Digital DX to recognize a particular browsing session or visit to the website.
Creation When the website user loads a page containing a chat button/customer monitoring script or when a chat session launches.
Cookie _bcvm_vid_{visitorParam}
Host 1st Party Website
Type 1st Party
Category Essential
Expiration End of session
Purpose Stores a unique, anonymous identifier (VisitID) to allow Digital DX to recognize a particular browsing session or visit to the website.
Creation When the website user loads a page containing a chat button/customer monitoring script or when a chat session launches.
Cookie _bcvm_vrid_{visitorParam}
Host 1st Party Website
Type 1st Party
Category Essential
Expiration Persistent
Purpose Stores a unique, anonymous identifier (VisitorID) to allow Digital DX  to recognize the website user during current and subsequent visits to the website.
Creation When the website user loads a page containing a chat button/customer monitoring script or when a chat session launches.
Cookie bc_pv_end
Host 1st Party Website
Type 1st Party
Category Performance/Functionality
Expiration End of session / 30 seconds
Purpose Improves accuracy of pageview tracking when a website user (customer) moves between pages.
Creation When the website user changes pages.
Cookie bc-visit-id
Host bold360.com
Type 3rd Party
Category Performance/Functionality
Expiration End of session
Purpose Same as _bcvm_vid_{visitorParam}. Stores a unique, anonymous identifier (VisitID) to allow Digital DX to recognize a particular browsing session or visit to the website.
Creation When the website user loads a page containing a chat button / customer monitoring script or when a chat session launches.
Cookie bc-visitor-id
Host bold360.com
Type 3rd Party
Category Essential
Expiration Persistent
Purpose Same as _bcvm_vrid_{visitorParam}. Stores a unique, anonymous identifier (VisitorID) to allow Digital DX to recognize the website user during current and subsequent visits to the website.
Creation When the website user loads a page containing a chat button / customer monitoring script or when a chat session launches.
Cookie _bc-curl
Host 1st Party Website
Type 1st Party
Category Performance/Functionality
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 Performance/Functionality
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 Performance/Functionality
Expiration End of session
Purpose Used to identify the current state of auto-answers being shown to the customer 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 Essential
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.
Cookie _bcck
Host livechat.boldchat.com
Type 1st party
Category Performance/Functionality
Expiration 2 hours
Purpose Used for chat validation, chat start.
Creation When the website user loads a page containing a chat button / customer monitoring script or when a chat session launches.
Cookie _bc-escalation
Host livechat.boldchat.com
Type 1st party
Category Performance/Functionality
Expiration End of session
Purpose Stores the escalation state.
Creation When the website user loads a page containing a chat button / customer monitoring script or when a chat session launches.
Cookie _bc-escalation-time
Host livechat.boldchat.com
Type 1st party
Category Performance/Functionality
Expiration 2 hours
Purpose Keeps chat in sync when refreshed or new tabs are opened.
Creation When the website user loads a page containing a chat button / customer monitoring script or when a chat session launches.
Cookie _bc-prechat-submitted_{chat_id}
Host livechat.boldchat.com
Type 1st party
Category Performance/Functionality
Expiration 24 hours
Purpose Keeps prechat form in sync when refreshed or new tabs are opened. Only placed when prechat feature is used.
Creation When the website user loads a page containing a chat button / customer monitoring script or when a chat session launches.
Cookie csrf-token
Host livechat.boldchat.com
Type 1st party
Category Performance/Functionality
Expiration End of session
Purpose Stores security token for safe form submission.
Creation When the website user loads a page containing a chat button / customer monitoring script or when a chat session launches.

How to enable video chat

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

Who can use this feature?

Important: Video chat is available on request. Contact your Customer Success representative for details.
  • Agents can use video chat in the legacy web client at web.boldchat.com only.
  • Visitors and agents 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). Bold360 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 Bold360, we recommend that you make the switch to HTTPS:

  1. Using the Desktop Client, create a new custom chat window, as follows:
    1. From the main menu of the Desktop 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 agent 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 agent.
    • 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 agent 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 agent 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 agent's chat experience.

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

Having problems?

Check the following.

Symptom Action
Video chat is not available. Are you using the web client at https://web.boldchat.com/ in a compatible browser? Video is only supported in the last 20 versions of Chrome.
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 Digital DX 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.

How to work with the BoldChat API

Frequently Asked Questions for Admins

Chat button isn?t showing on website or chat button shows that chat is unavailable

Make sure someone is signed in to the Agent Workspace and set that user to available.

My chats are not automatically assigning to agents (Routing/ACD/Queues/rule exports)

Make sure ACD is enabled either at the Channel level or at the Department level. If enabled, check any routing rules that assign chats to the relevant department.

Why are my customers building an endless chat queue?

Make sure you enable a concurrent chat limit within ACD, and then you can set your queue limits.

How can I see what Routing Rule is causing my chats to go to a different location?

Export your Routing Rules into an Excel file and enable filtering in Excel. You can now filter by the specific actions or criteria that cause the chats to be routed. Find out which rule has a higher rank, meaning the system will trigger that rule first.

If someone else made changes to something I was working on, or if I?m not sure what I changed, is there an easy way to find out what happened or revert back?

There is no way to revert to settings you previously saved unless you made a copy of the item. However, you can use the Audit Log to see exactly what changes have been made on the account. Simply locate the changed item in the Audit Log by the date and time the change may have occurred and you?ll be able to see exactly what settings where changed, what were they changed to, and see whether something was created, updated, or deleted. See View changes in the Admin Center.

Note: Make sure you are in a permission group that provides access to the audit log.

My agents or I cannot access anything

If you cannot see a chat folder, edit canned messages, or handle any other tasks in any Bold360 console, you may need to check you or your agent?s Permission Group to see if you have access to the item.

How can I see what my agents are working on?

Go to agent.bold360.com/monitor to be able to see our Monitor View where you get up to four queues depending on your subscription type: AI Chatbot chats, Queued chats, chats Assigned to an Agent, and Closed chats. You can click each item to see the conversation and information about the customer and information about the chat conversation. You can also filter by agent Departments as well as Folders to see just a specific queue/group of items or agents.

How do I understand my peaks, trends, and questions on Agent performance?

Our reporting helps you see a breakdown of your chat/customer volume. We have many different reports that look at agent efficiencies, visits to your website and where chats are started or ended, and many more use cases depending on the KPI you are measuring for. Find out more about reporting.

I have an issue that I believe is a bug. How should I escalate my issue to LogMeIn?

To raise a support case or bug, please collect a few necessary items before contacting Support to make your experience as smooth as possible:

  • a .HAR file captured while replicating the issue
  • full-screen screenshots and not just a screenshot of a particular error message
  • the Chat ID of any chats which had an issue

For more information, see How do I contact Bold360 support about the Agent platform?

Your base reports or dashboard are good but don?t present all the information our Organization requires

You can create custom reports or a dashboard using our API. You can find our documentation at https://developer.bold360.com, which contains information on how to export your raw data to then create custom reports or a dashboard.

Are there any other best practices I need to be aware of?

To ensure you?re set up for future success, create folders on a 1:1 ratio with your department names (for example, Sales department also has a chat folder, titled "Sales") so that your teams can view their work items and supervisors can report on only their team?s work items.

You can also make sure your agents can efficiently handle as many chats as are assigned to them. The best way to help your agents is to create predefined messages, called Canned Messages, that agents can quickly use to keep the conversation going.

Lastly, it is recommended to include brackets {} at the beginning of the Agent Name that contain either the person?s role (Agent, Admin, Supervisor, etc.) or their permission group (Agent, Sales, Developer, etc.) so when looking at reporting you can tell exactly what part of the Organization the person belongs to.

Frequently Asked Questions for Developers

I have deployed the code snippet, I have agents available, but the button still doesn?t show on the website

When deploying the code snippet, make sure that you paste it directly from the code generation dialog in the Bold360 Admin interface. If the code snippet was sent to you for deployment in a Microsoft Word document, it?s possible that the code was broken with Microsoft Word styling or line breaks. Request the code snippet again in a plain text document.

I might want to use Proactive Invites at some point; what do you recommend?

You will need to redeploy code if you choose to integrate an Invitation Ruleset. We recommend disabling the default Invite Ruleset in the Admin Center and deploying the Invitation Ruleset with your button code. If you decide to use chat invites, you can easily enable the Invitation Ruleset and add some rules for your use cases.

What is the best way to manage the code deployment?

If you have a Tag Manager, it is recommended you deploy your code using the tag management system. This enables you to trigger the Bold360 code on specific pages from a tag manager, which makes it easier to manage over time. If you deploy to each page of your website, then it will be much more difficult and time-consuming to deploy and manage the code.

I had customized a few items with my Chat Window or Button and now things are not working correctly on my site

Copy your standard code snippet created in the Admin Center and paste it in a blank page to try and reproduce. If your code works on the blank page but not your website, there are probably some CSS or other variables on your site causing an issue. Please note that our support team cannot troubleshoot issues stemming from your site?s CSS.

I?m having issues with an API Trigger not working

First, you need to investigate if the Trigger itself is the issue. To do so, set up two triggers, one to a staging/test website and one to your production site. If the trigger works in one space, we can assume there is something with the webhook causing an issue.

SMS Activity Summary report

This report contains details such as the number of texts sent and received, average time to respond, number of answered, ended answered and ended unanswered texts along with average speed to answer and average time to end for answered.

Fastpath: report.boldchat.com > New Report > SMS > SMS Activity Summary

See activity for a specified date range.

Sent
Messages sent within the specified date range.
Received
Messages received within the specified date range.
ATTR (HH:MM:SS)
Average time to respond for sent messages that were in reply to a received message.
Answered
Messages that were answered within the specified date range.
ASA (HH:MM:SS)
Average Speed to Answer for answered messages.
Ended Ans
Messages ended in the specified date range that were answered at some time.
Ended Unans
Messages ended that have never been answered
ATTC (HH:MM:SS)
Average Time to End for Answered, Ended messages (from Answered to Ended)

SMS Login reports

See the amount of time that your agents spent on handling text messages.

Fastpath: report.boldchat.com > New Report > Login

SMS Login Summary

See the amount of time that your agents spent logged in Digital DX with regards to handling SMS. For a given date range, this report shows the number of hours and minutes each agent was logged in as either Available or Away.

Reported data:

Operator
Name of the agent.
SMS Available - Total
The total time the agent spent in available status.
SMS Available - .NET
The total time the agent spent in available status in the Desktop Client.
SMS Available - Web
The total time the agent spent in available status in Agent Workspace.
SMS Available - Mobile
The total time the agent spent in available status in the iPhone app or using the web client on a mobile device.
SMS Away - Total
The total time the agent spent in Away status.
SMS Away - .NET
The total time the agent spent in Away status in the Desktop Client.
SMS Away - Web
The total time the agent spent in Away status in Agent Workspace.
SMS Away - Mobile
The total time the agent spent in Away status in the iPhone app or using the web client on a mobile device.
% Forced
Percentage of total Away time that was forcibly put in Away status by ACD for not answering an item.

SMS Login Details

See the time of day associated with both login and logout behavior of agents with regards to handling SMS. The report can be grouped by date or agent and shows the time of day associated with a variety of login/logout behavior. The report shows the client the agent used and what action they took, whether that was logging in as Available or Away, or logging out.

Reported data:

Operator
Name of the agent.
Time
The time of changing the agent's status.
Client
The client where the agent's status was changed.
Action
The action that was taken to change the agent's status.

SMS Performance reports

Create reports on your agents' performance over your SMS channel.

Fastpath: report.boldchat.com > New Report > SMS > Performance

SMS Answer Performance Summary report

For a specified date range, analyze the distribution of the time to answer message conversations and performance within the defined time interval.

SMS Assignment Answer Performance Summary report

For a specified date range, analyze the distribution of the time to answer message assignments and performance within the defined time interval.

SMS End Time Performance Summary report

For a specified date range, analyze the distribution of the time to close message threads and performance within the defined time interval.

SMS Assignment End Time Performance Summary report

For a specified date range, analyze the distribution of the time to end message assignments and performance within the defined time interval.

Facebook Messenger Login reports

See the amount of time that your agents spent on handling Facebook messages. Facebook Messenger reports are only available for Digital DX subscribers.

Fastpath: report.boldchat.com > New Report > Login

Trouble logging in to your Facebook account?

FB Messenger Login Summary

See the amount of time that your agents spent logged in Digital DX with regards to handling Facebook Messenger conversations. For a given date range, this report shows the number of hours and minutes each agent was logged in as either Available or Away. A breakdown by Digital DX client application is also included.

Reported data:

Operator
Name of the agent.
FB Messenger Available - Total
The total time the agent spent in available status.
FB Messenger Available - .NET
The total time the agent spent in available status in the Desktop Client.
FB Messenger Available - Web
The total time the agent spent in available status in Agent Workspace.
FB Messenger Available - Mobile
The total time the agent spent in available status in the iPhone app or using the web client on a mobile device.
FB Messenger Away - Total
The total time the agent spent in Away status.
FB Messenger Away - .NET
The total time the agent spent in Away status in the Desktop Client.
FB Messenger Away - Web
The total time the agent spent in Away status in Agent Workspace.
FB Messenger Away - Mobile
The total time the agent spent in Away status in the iPhone app or using the web client on a mobile device.
% Forced
Percentage of total Away time that was forcibly put in Away status by ACD for not answering an item.

FB Messenger Login Details

See the time of day associated with both login and logout behavior of agents with regards to handling Facebook Messenger conversations. The report can be grouped by date or agent and shows the time of day associated with a variety of login/logout behavior. The report shows the client the agent used and what action they took, whether that was logging in as Available or Away, or logging out.

Reported data:

Operator
Name of the agent.
Time
The time of changing the agent's status.
Client
The client where the agent's status was changed.
Action
The action that was taken to change the agent's status.

Facebook Messenger Performance reports

These reports show performance metrics for Facebook Messenger conversations.

Fastpath: report.boldchat.com > New Report > FB Messenger > Performance

FB Messenger Answer Performance Summary report

For a specified date range, analyze the distribution of the time to answer messenger conversations and performance within the defined time interval.

FB Messenger Assignment Answer Performance Summary report

For a specified date range, analyze the distribution of the time to answer messenger assignments and performance within the defined time interval.

FB Messenger End Time Performance Summary report

For a specified date range, analyze the distribution of the time to close message threads and performance within the defined time interval.

FB Messenger Assignment End Time Performance Summary report

For a specified date range, analyze the distribution of the time to end messenger assignments and performance within the defined time interval.

Manage incoming email according to routing rules (Email Rules Engine)

The email rules engine compares the properties of incoming email against criteria and performs the rule's action when there is a match.

Important: You must have Account > Can Setup Rules Engines permission to manage your email rules.

What is the difference between Email Management Rules and Email Routing Rules?

Email Management Rules are the successor of Email Routing Rules. In the Web Admin Center, you can only create Email Management Rules, which let you define additional Criteria and Actions on top of regular Email Routing Rule definitions. If you have previously created Email Routing Rules, those are listed separately for you on the Channels > Email > Routing Rules page. If you never had Email Routing Rules, then you see only a list of Email Management Rules.

You can still use your Email Routing Rules, but you cannot create new ones; you can only edit and convert those to Email Management Rules, which is highly recommended. Once converted, these rules cannot be edited in the Desktop Client. Digital DX prioritizes Email Management Rules over Email Routing Rules.

You can export your Email Management Rules to a JSON file. Similarly, you can add new Email Management Rules by importing those from JSON files.

  1. Create an email folder if you haven't done so already:
    1. In the Web Admin Center, go to Channels > Email > Email Folders.
    2. Hover your mouse over the Email folder and click the Create folder () icon.
    3. Name your folder.
  2. Create or edit an Email Rule, as follows:
    1. In the Web Admin Center, click Channels > Email > Routing Rules.
    2. On the Routing Rules for Email page, select an existing rule or click Create New.

    Result: The Edit/New Rule page is displayed.

  3. On the Criteria tab, name the rule.

    Each rule should have a unique name for easy identification.

  4. Select one or more criteria.
    Tip: To enter multiple values in a field, type a string and press Enter.

    Multiple selected criteria within a group are evaluated according to OR condition logic, while selected criteria across groups are evaluated according to AND condition logic.

    • Anywhere Contains. This uses OR logic when looking for matches in any "Contains" field.
    • Subject Contains
    • Body Contains
    • User's Email Address Contains
    • Destination Email Address contains
    • Has Attachments
    • Email Account
    • Email Type
    • Department

    Result: The rules engine compares incoming items against the criteria and performs the rule's action when there is a match.

  5. Optionally, select Apply rule to each email in thread to specify whether the rule should be applied to every outgoing email in a thread or only to the first one.
  6. On the Actions tab, choose how to route items when criteria are met:
    • Folder, to send the item to a specific folder
    • Department, to make the item available to members of a specific department
  7. On the Actions tab, assign attributes to an item when criteria are met:
    • Category
    • Status
    • Custom Field 1 or 2
    • Urgency
    • Difficulty

    Result: Agents can use this information to make decisions about how to handle or organize emails.

  8. Optionally, on the Actions tab under Reply with Canned Message, you can define an automatic reply when an email is received from a specific email address. If you also want to include the customer's email in your reply, select Reply to original email thread.
    Note: In the Web Admin Center, you can only create Email Management Rules, which let you define additional Criteria and Actions on top of regular Email Routing Rule definitions.
  9. Save the rule.
  10. Continue to create rules and arrange them in the order they should be evaluated (Move Up, Move Down).
    Important: Rules are evaluated in the order they appear in the rules list. In addition, Digital DX prioritizes Email Management Rules over Email Routing Rules.
Rules are applied to all your email accounts. To run rules on a specific account, you must define an Email account as criteria.

Block customers from sending emails to agents

Admins can set up routing rules to prevent customers from sending emails to your agents and essentially denylist email addresses.

Important: You must have Account settings > Setup Rules Engines permission to manage your email rules.
  1. In the Web Admin Center, click Channels > Email > Routing Rules.
  2. On the Routing Rules for Email page, select an existing rule or click Create New.

    Result: The Edit/New Routing Rule for Email page is displayed.

  3. Name the rule.

    Rules are displayed in the rules list by Rule Name. Each rule should have a unique name for easy identification.

  4. In the User's email address contains field, type the email address of the customers you want to block.

    You can add multiple email addresses.

  5. On the Actions tab, select a folder and a department that are not part of any other routing rules.
  6. Save your routing rule.
Your unwanted emails will still be available in Bold360, but will be routed to a department and folder that is not attended by any agent.

Set up automatic distribution for email

Automatic Email Distribution (AD) allows you to automatically and intelligently distribute and assign incoming emails to your agents.

  1. In the Web Admin Center, click Channels > Email > Automatic Distribution.

    Result: The Automatic Distribution for Email page is displayed.

  2. Select Enable automatic distribution.

    Result: This activates AD for all incoming email in your account.

  3. Options:
    Option Description
    Reassign unanswered messages (minutes) When selected, emails are reassigned to another agent when the originally assigned agent does not accept the thread within the specified period of time. An agent who fails to answer in time is set to Away status to prevent new threads from being assigned.
    Concurrent message limit When selected, the number of threads that can be assigned to each agent is limited. When an agent reaches the limit, they are no longer assigned new threads. This setting can be overridden at an individual agent level.
    Agents waiting for assignment When there are fewer incoming email threads than agents can handle, some agents will be waiting for an assignment. Threads are assigned to highest ranked agents first, but you can choose an assignment method for agents of the same rank.

    To determine which waiting agent gets the next email, choose an assignment method:

    • Least Busy. Assign the next incoming thread to the agent who has the fewest active threads and has waited the longest. This naturally means that if you have multiple agents available with no email threads, ACD will assign the next incoming email to the agent who has been in Available status for the longest period of time. Choose this to balance the workload between agents.
    • Most Busy. Assign threads to your busiest agents. The next incoming thread is assigned to the agent who is handling the most threads until their limit is reached, and thereafter to the agent who has been idle for the shortest period of time. Choose this option if your agents must manage non-email tasks along with their email related work. Those who are managing email will stay busy with email, while others can stay focused on non-email tasks. To prevent overload on a single agent, make sure concurrent limits are set.
    • Round Robin Rotate assignment among all available agents regardless of waiting time or number of active threads (until their concurrent limit is reached). Choose this option to balance the number of threads assigned per agent. Lower ranked agents will only be assigned a thread if all higher ranked agents have reached their limit.
  4. Under Manual Reassignment, tell Bold360 how to place customers into the queue when they are reassigned by an agent rather than automatic distribution.

    You can set this option independently for customers reassigned within a department (From same department) as opposed to between departments (From other departments).

    Note: For answered items that are manually reassigned, the queue time is always reset. For automatically assigned items, customers always maintain their place in the queue.
    • To place customers at the end of the queue regardless of how long they have been waiting, select Move to end of queue (time is reset)
    • To place customers in the queue based on time already spent waiting, select Maintain place in queue (time is preserved)
  5. Save your changes.

    Result: Settings are applied to your entire account except where overridden at the department or agent level.

Set up automatic email replies

You can send automated messages to customers when your agents are not available.

  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.
    2. Select an existing account or click Create New. The New/Edit Email Account page is displayed.
  2. On the Auto Responder tab, select Auto responder enabled.
  3. Click Create New.
  4. Enter a name for your auto responder rule set and Click Add Criteria.
  5. Select the relevant criteria and actions as follows:
    Option Description
    Email Delivery Time Set business hours for automatic email replies and select whether these messages should be sent inside or outside business hours.
    Destination Address You can define an email address as the target of the customer's email. Depending on whether customers send emails to this address, they will receive an automatic reply.
    Email Type Select the type of emails that you want to reply.
    From Address If you want to send automatic replies only to certain customers, then you can define a string that the customer's email address should include or exclude. For example, you may not want to send automatic replies to email addresses containing the donotreply string.
    Subject Line Define the subject of emails that you want to send automatic replies.
  6. Under Actions, select the email address that the customer will see as the sender of the email and select the Canned Message that will be body of the email.

Email Status Summary reports

(on Web Reports: Assignment Status Summary and Thread Status Summary) These reports provide the status of new email threads created in the date range specified, including details about the number of unanswered and answered emails for open as well as closed email threads.

Fastpath: report.boldchat.com > New Report > Email > Status Summary

Report availability: Enterprise

Assignment Status Summary report

This report provides the status of new email assignments created in the date range specified. It includes details about the number of unanswered and answered emails for open as well as closed email threads.

Reported data:

New
The number of new email assignments during the specified date range.
Open Answered
The number of answered assignments (automatic or manual) that were still open during the specified date range either because they were reassigned or the thread was closed.
Open Unanswered
The number of assignments (automatic or manual) that were still open during the specified date range without being answered either because they were reassigned or the thread was closed.
Closed Answered
The number of answered assignments (automatic or manual) that were closed during the specified date range either because they were reassigned or the thread was closed.
Closed Unanswered
The number of assignments (automatic or manual) that were closed during the specified date range without being answered either because they were reassigned or the thread was closed.

Thread Status Summary report

This report provides the status of new email threads created in the date range specified. It includes details about the number of unanswered and answered emails for open as well as closed email threads

  • Sent = The number of emails sent during the specified date range.
  • Received = The number of emails received during the specified date range.
  • ATTR (HH:MM:SS) = The "Average Time to Reply" for each email sent as a reply during the specified date range. Calculated as follows: [time when sent] minus [time when received]. If multiple emails were received, only the most recent is used.
  • Answered = The number of threads for which an answer was sent during the specified date range. Each thread with an answer is represented.
  • ASA (HH:MM:SS) = The "Average Speed to Answer" for threads answered during the specified date range. Calculated as follows: [time when first answer was sent] minus [time when thread was created].
  • Closed Answered = The number of answered threads that were closed during the specified date range. Only threads with an end time within the specified date range are reported.
  • Closed Unanswered = The number of threads that were closed during the specified date range without being answered.
  • ATTC (HH:MM:SS) = The "Average Time to Close" for each thread that was closed during the specified date range for which an answer was sent. Calculated as follows: [time when the thread was closed] minus [the time when the first answer was sent].

Email Status Summary reports

These reports provide the status of new email threads created in the date range specified, including details about the number of unanswered and answered emails for open as well as closed email threads.

Fastpath: report.boldchat.com > New Report > Email > Status Summary

Assignment Status Summary report

This report provides the status of new email assignments created in the date range specified. It includes details about the number of unanswered and answered emails for open as well as closed email threads.

Reported data:

New
The number of new email assignments during the specified date range.
Open Answered
The number of answered assignments (automatic or manual) that were still open during the specified date range either because they were reassigned or the thread was closed.
Open Unanswered
The number of assignments (automatic or manual) that were still open during the specified date range without being answered either because they were reassigned or the thread was closed.
Closed Answered
The number of answered assignments (automatic or manual) that were closed during the specified date range either because they were reassigned or the thread was closed.
Closed Unanswered
The number of assignments (automatic or manual) that were closed during the specified date range without being answered either because they were reassigned or the thread was closed.

Thread Status Summary report

This report provides the status of new email threads created in the date range specified. It includes details about the number of unanswered and answered emails for open as well as closed email threads

  • Sent = The number of emails sent during the specified date range.
  • Received = The number of emails received during the specified date range.
  • ATTR (HH:MM:SS) = The "Average Time to Reply" for each email sent as a reply during the specified date range. Calculated as follows: [time when sent] minus [time when received]. If multiple emails were received, only the most recent is used.
  • Answered = The number of threads for which an answer was sent during the specified date range. Each thread with an answer is represented.
  • ASA (HH:MM:SS) = The "Average Speed to Answer" for threads answered during the specified date range. Calculated as follows: [time when first answer was sent] minus [time when thread was created].
  • Closed Answered = The number of answered threads that were closed during the specified date range. Only threads with an end time within the specified date range are reported.
  • Closed Unanswered = The number of threads that were closed during the specified date range without being answered.
  • ATTC (HH:MM:SS) = The "Average Time to Close" for each thread that was closed during the specified date range for which an answer was sent. Calculated as follows: [time when the thread was closed] minus [the time when the first answer was sent].

How to create an email signature for an agent

Create an email signature that can be attached to outgoing email messages.

  1. Create or edit an agent, as follows:
    1. In the Web Admin Center, go to Organization > Agents.
    2. On the Agent Management page, select an existing agent or click Create New.

    Result: The New/Edit Agent page is displayed.

  2. On the Email Settings tab, set the following options:
    Option Description
    Email Name The name to show in the email From field.
    Email Account The email account to associate with the agent.
    Use Email Signature

    Never ? Do not add the email signature to outgoing emails.

    First Outgoing Only ? Add the email signature to the first outgoing email (new email or first reply).

    All Outgoing ? Always add the email signature to outgoing emails.

  3. To set up the signature, use the HTML and/or plain text editor.
  4. Save your changes.

Email Assignment Summary report

Analyze data such as email assignments accepted during the time period (per agent), average time to accept email assignments, average speed to answer email assignments, and more.

Fastpath: report.boldchat.com > New Report > Email > Assignment Summary

Report availability: Enterprise

Reported data:

Operator
Name of the agent.
Accepted
Number of accepted email assignments by the agent.
Average Time to Accept
Average time to accept email assignments.
Answered
Number of answered emails.
Average Speed to Answer
Average Speed to Answer for answered chats. Calculates time from chat Started to Answered by a live agent. Time from when the chat started to the time it was answered by the agent.
Still Active
Number of email assignments that are still active.
Closed Answered
Number of emails that were answered before they were closed.
Closed Unanswered
Number of emails that were not answered before they were closed.
Average Time to Close (Unanswered)
The average time to close for each assignment that was closed during the specified date range for which an answer was sent. Calculated as follows: [time when the assignment was reassigned or the thread was closed] minus [the time when the first answer was sent].
Average Emails
Received
The number of emails received during the specified date range.
Sent
The number of emails sent during the specified date range.
Average Time to Respond
The average time to reply for each email sent as a reply during the specified date range. Calculated as follows: [Time when sent] minus [time when received]. If multiple emails were received, only the most recent is used.

Email Assignment Summary report

Analyze data such as email assignments accepted during the time period (per agent), average time to accept email assignments, average speed to answer email assignments, and more.

Fastpath: report.boldchat.com > New Report > Email > Assignment Summary

Reported data:

Operator
Name of the agent.
Accepted
Number of accepted email assignments by the agent.
Average Time to Accept
Average time to accept email assignments.
Answered
Number of answered emails.
Average Speed to Answer
Average Speed to Answer for answered chats. Calculates time from chat Started to Answered by a live agent. Time from when the chat started to the time it was answered by the agent.
Still Active
Number of email assignments that are still active.
Closed Answered
Number of emails that were answered before they were closed.
Closed Unanswered
Number of emails that were not answered before they were closed.
Average Time to Close (Unanswered)
The average time to close for each assignment that was closed during the specified date range for which an answer was sent. Calculated as follows: [time when the assignment was reassigned or the thread was closed] minus [the time when the first answer was sent].
Average Emails
Received
The number of emails received during the specified date range.
Sent
The number of emails sent during the specified date range.
Average Time to Respond
The average time to reply for each email sent as a reply during the specified date range. Calculated as follows: [Time when sent] minus [time when received]. If multiple emails were received, only the most recent is used.

Email Activity Summary reports

The report contains details such as the number of emails sent and received, average time to respond, number of answered, closed answered and closed unanswered email threads along with average speed to answer and average time to close for answered.

Fastpath: report.boldchat.com > New Report > Email > Activity Summary

Assignment Activity Summary

This report returns activity for individual emails exchanged within a thread based on the agent assigned to the individual emails. The Sent, Received, and ATTR (Average Time to Respond) columns look at the email count grouped by the created date of individual emails in a thread. Answered and ASA (Average Speed to Answer) represent data for individual emails.

Note: To see the number of emails your agents received per hour, then group the report by Hour when running it.

Reported data:

Sent
The number of emails sent during the specified date range.
ATTR (HH:MM:SS)
The Average Time to Reply for each email sent as a reply during the specified date range. Calculated as follows: [Time when sent] minus [time when received]. If multiple emails were received, only the most recent is used.
Received
The number of emails received during the specified date range.
Answered
The number of assignments (automatic or manual) for which an answer was sent during the specified date range. Each assignment with an answer is represented, even when answering the same email or the same thread.
ASA (HH:MM:SS)
The Average Speed to Answer for assignments answered during the specified date range. Calculated as follows: [time when first answer was sent] minus [time when assignment was made].
Closed Answered
The number of answered assignments (automatic or manual) that were closed during the specified date range either because they were reassigned or the thread was closed.
Closed Unanswered
The number of assignments (automatic or manual) that were closed during the specified date range without being answered either because they were reassigned or the thread was closed.
ATTC (HH:MM:SS)
The Average Time to Close for each assignment that was closed during the specified date range for which an answer was sent. Calculated as follows: [time when the assignment was reassigned or the thread was closed] minus [the time when the first answer was sent].
Important: This report focuses on activity on given dates, as shown in rows. The only attribute shared by numbers reported in columns is their occurrence on the given date. For example, an email reported in the Sent column may not be the same as the email thread represented in the Answered column (which is showing results based on the first answered email in the thread). Similarly, Closed Answered, Closed Unanswered, and ATTC (Average Time to Close) are based on the closed time of a thread and may not represent the same emails reported in the Sent, Received, or ATTR columns.

When filtered by agent/department, or when using agent grouping, you filter out the individual emails assigned to the filtered agent/department.

Thread Activity Summary

This report returns activity for individual emails exchanged within a thread based on the agent assigned to the thread. However, Sent, Received, and Average Time to Respond look at the email count grouped by the created date of individual emails.

Reported data:

Sent
The number of emails sent during the specified date range.
Received
The number of emails received during the specified date range.
ATTR (HH:MM:SS)
The Average Time to Reply for each email sent as a reply during the specified date range. Calculated as follows: [time when sent] minus [time when received]. If multiple emails were received, only the most recent is used.
Answered
The number of threads for which an answer was sent during the specified date range. Each thread with an answer is represented.
ASA (HH:MM:SS)
The Average Speed to Answer for threads answered during the specified date range. Calculated as follows: [time when first answer was sent] minus [time when thread was created].
Closed Answered
The number of answered threads that were closed during the specified date range. Only threads with an end time within the specified date range are reported.
Closed Unanswered
The number of threads that were closed during the specified date range without being answered.
ATTC (HH:MM:SS)
The "Average Time to Close" for each thread that was closed during the specified date range for which an answer was sent. Calculated as follows: [time when the thread was closed] minus [the time when the first answer was sent].
Important: This report focuses on activity on given dates, as shown in rows. The only attribute shared by numbers reported in columns is their occurrence on the given date. For example, an email reported in the Sent column may not be the same as the email thread represented in the Answered column (which is showing results based on the first answered email in the thread). Similarly, Closed Answered, Closed Unanswered, and ATTC (Average Time to Close) are based on the closed time of a thread and may not represent the same emails reported in the Sent, Received, or ATTR columns.

When filtered by agent/department, or when using the agent grouping, you filter out the email threads assigned to the filtered agent/department. The ASA (Average Speed to Answer) is calculated using the time-to-answer of the first email answered in each counted thread (as shown in the Answered column).

Email Activity Summary reports

The report contains details such as the number of emails sent and received, average time to respond, number of answered, closed answered and closed unanswered email threads along with average speed to answer and average time to close for answered.

Fastpath: report.boldchat.com > New Report > Email > Activity Summary

Assignment Activity Summary

Report availability: Enterprise. Web only

This report returns activity for individual emails exchanged within a thread based on the agent assigned to the individual emails. The Sent, Received, and ATTR (Average Time to Respond) columns look at the email count grouped by the created date of individual emails in a thread. Answered and ASA (Average Speed to Answer) represent data for individual emails.

Note: To see the number of emails your Operators received per hour, then group the report by Hour when running it.

Reported data:

Sent
The number of emails sent during the specified date range.
ATTR (HH:MM:SS)
The Average Time to Reply for each email sent as a reply during the specified date range. Calculated as follows: [Time when sent] minus [time when received]. If multiple emails were received, only the most recent is used.
Received
The number of emails received during the specified date range.
Answered
The number of assignments (automatic or manual) for which an answer was sent during the specified date range. Each assignment with an answer is represented, even when answering the same email or the same thread.
ASA (HH:MM:SS)
The Average Speed to Answer for assignments answered during the specified date range. Calculated as follows: [time when first answer was sent] minus [time when assignment was made].
Closed Answered
The number of answered assignments (automatic or manual) that were closed during the specified date range either because they were reassigned or the thread was closed.
Closed Unanswered
The number of assignments (automatic or manual) that were closed during the specified date range without being answered either because they were reassigned or the thread was closed.
ATTC (HH:MM:SS)
The Average Time to Close for each assignment that was closed during the specified date range for which an answer was sent. Calculated as follows: [time when the assignment was reassigned or the thread was closed] minus [the time when the first answer was sent].
Important: This report focuses on activity on given dates, as shown in rows. The only attribute shared by numbers reported in columns is their occurrence on the given date. For example, an email reported in the Sent column may not be the same as the email thread represented in the Answered column (which is showing results based on the first answered email in the thread). Similarly, Closed Answered, Closed Unanswered, and ATTC (Average Time to Close) are based on the closed time of a thread and may not represent the same emails reported in the Sent, Received, or ATTR columns.

When filtered by agent/department, or when using agent grouping, you filter out the individual emails assigned to the filtered agent/department.

Thread Activity Summary

Report availability: Enterprise. Web only

This report returns activity for individual emails exchanged within a thread based on the agent assigned to the thread. However, Sent, Received, and Average Time to Respond look at the email count grouped by the created date of individual emails.

Reported data:

Sent
The number of emails sent during the specified date range.
Received
The number of emails received during the specified date range.
ATTR (HH:MM:SS)
The Average Time to Reply for each email sent as a reply during the specified date range. Calculated as follows: [time when sent] minus [time when received]. If multiple emails were received, only the most recent is used.
Answered
The number of threads for which an answer was sent during the specified date range. Each thread with an answer is represented.
ASA (HH:MM:SS)
The Average Speed to Answer for threads answered during the specified date range. Calculated as follows: [time when first answer was sent] minus [time when thread was created].
Closed Answered
The number of answered threads that were closed during the specified date range. Only threads with an end time within the specified date range are reported.
Closed Unanswered
The number of threads that were closed during the specified date range without being answered.
ATTC (HH:MM:SS)
The "Average Time to Close" for each thread that was closed during the specified date range for which an answer was sent. Calculated as follows: [time when the thread was closed] minus [the time when the first answer was sent].
Important: This report focuses on activity on given dates, as shown in rows. The only attribute shared by numbers reported in columns is their occurrence on the given date. For example, an email reported in the Sent column may not be the same as the email thread represented in the Answered column (which is showing results based on the first answered email in the thread). Similarly, Closed Answered, Closed Unanswered, and ATTC (Average Time to Close) are based on the closed time of a thread and may not represent the same emails reported in the Sent, Received, or ATTR columns.

When filtered by agent/department, or when using the agent grouping, you filter out the email threads assigned to the filtered agent/department. The ASA (Average Speed to Answer) is calculated using the time-to-answer of the first email answered in each counted thread (as shown in the Answered column).

Email Login reports

See the amount of time that your agents spent on handling emails.

Fastpath: report.boldchat.com > New Report > Login

Email Login Summary

See the amount of time that your agents spent logged in to Digital DX to handle email. For a given date range, this report shows the number of hours and minutes each agent was logged in as either available or Away. A breakdown by client application is also included.

Results are not returned for agents with no login activity.

Reported data:

Operator
Name of the agent.
Email Available - Total
The total time the agent spent in available status.
Email Available - .NET
The total time the agent spent in available status in the Desktop Client.
Email Available - Web
The total time the agent spent in available status in Agent Workspace.
Email Available - Mobile
The total time the agent spent in available status in the iPhone app or using the web client on a mobile device.
Email Away - Total
The total time the agent spent in Away status.
Email Away - .NET
The total time the agent spent in Away status in the Desktop Client.
Email Away - Web
The total time the agent spent in Away status in Agent Workspace.
Email Away - Mobile
The total time the agent spent in Away status in the iPhone app or using the web client on a mobile device.
% Forced
Percentage of total Away time that was forcibly put in Away status by ACD for not answering an item.

Email Login Details

See the time of day associated with login and logout actions for agents handling email. The report can be grouped by date or agent and shows the time of day associated with a variety of login/logout behavior. The report shows the client the agent used and what action they took, whether that was logging in as Available or Away, or logging out.

Results are not returned for dates with no login activity.

Reported data:

Operator
Name of the agent.
Time
The time of changing the agent's status.
Client
The client where the agent's status was changed.
Action
The action that was taken to change the agent's status.

Email Performance reports

Create reports on your agents' performance over your email channel.

Fastpath: report.boldchat.com > New Report > Email > Performance

Email Thread Answer Performance Summary report

Report availability: Enterprise

This report returns the time it takes for email threads to be answered, based on the selected grouping. Use it to analyze the time-to-answer distribution for each email in a thread. Time-to-answer is the time between receipt of the incoming email and the agent's response. The report returns the interval between the first email's arrival to the BoldChat server and the initial response to that email by an agent.

Important: As of 8/26/2016, emails are filtered based on the date of the event being measured rather than the date of creation of the email thread.

Email Thread Close Time Performance Summary report

Report availability: Enterprise

Returns the time it takes to close the email thread based on the selected grouping. It answers the question "How much time elapsed between the first response the time when the thread was closed?"

Important: As of 8/26/2016, emails are filtered based on the date of the event being measured rather than the date of creation of the email thread.

Email Assignment Answer Performance Summary report

Report availability: Enterprise

This report returns the time it takes for email assignments to be answered, based on the selected grouping. It answers the question "How long is it taking my agents to respond to an email?"

It analyzes the time-to-respond distribution for each email sent in direct response to an incoming email. Time-to-respond is the time between receipt of the incoming email and the agent's direct response.

Email Assignment Close Time Performance Summary report

Report availability: Enterprise

This report returns the time it takes to close the email assignment based on the selected grouping. It answers the question "How much time elapsed between the time of assignment and the time when the assignment was closed?" It is filtered based on the time the email assignment was closed.

Email Time To Respond Performance Summary report

This report returns the time it takes for an email to be responded to, based on the selected grouping. Use this report to answer the question "How long did customers have to wait for each response sent on a given date?"

To avoid a negative impact on agents' performance statistics, use Time Filter > Only when agents are Available. This excludes periods when agents should not normally be expected to respond - namely, when they are unavailable.

Note: To avoid a negative impact on operators' performance statistics, use Time Filter > Only when Operators are Available. This excludes periods when operators should not normally be expected to respond ? namely, when they are unavailable.
Important: As of 8/26/2016, emails are filtered based on the date of the event being measured rather than the date of creation of the email thread.

Email Performance reports

Create reports on your agents' performance over your email channel.

Fastpath: report.boldchat.com > New Report > Email > Performance

Email Thread Answer Performance Summary report

This report returns the time it takes for email threads to be answered, based on the selected grouping. Use it to analyze the time-to-answer distribution for each email in a thread. Time-to-answer is the time between receipt of the incoming email and the agent's response. The report returns the interval between the first email's arrival to the BoldChat server and the initial response to that email by an agent.

Email Thread Close Time Performance Summary report

Returns the time it takes to close the email thread based on the selected grouping. It answers the question "How much time elapsed between the first response the time when the thread was closed?"

Email Assignment Answer Performance Summary report

This report returns the time it takes for email assignments to be answered, based on the selected grouping. It answers the question "How long is it taking my agents to respond to an email?"

It analyzes the time-to-respond distribution for each email sent in direct response to an incoming email. Time-to-respond is the time between receipt of the incoming email and the agent's direct response.

Email Assignment Close Time Performance Summary report

This report returns the time it takes to close the email assignment based on the selected grouping. It answers the question "How much time elapsed between the time of assignment and the time when the assignment was closed?" It is filtered based on the time the email assignment was closed.

Email Time To Respond Performance Summary report

This report returns the time it takes for an email to be responded to, based on the selected grouping. Use this report to answer the question "How long did customers have to wait for each response sent on a given date?"

To avoid a negative impact on agents' performance statistics, use Time Filter > Only when agents are Available. This excludes periods when agents should not normally be expected to respond - namely, when they are unavailable.

Email Productivity reports

Create reports on your agents' productivity when answering emails.

Fastpath: report.boldchat.com > New Report > Email > Productivity

Reports' availability: Enterprise

Accepted

See the number of accepted email threads by the given grouping for a specified date range. An email is considered accepted when an agent accepts or responds to an assigned email thread.

Answered

See the number of answered email threads by the given grouping for a specified date range. An email is considered answered when an agent is the first to respond to an email thread.

Assigned

See the number of assigned email threads by the given grouping for a specified date range. An email thread is considered assigned on each new assignment or re-assignment.

Closed (Answered)

See the number of email threads closed with an answer by the given grouping for a specified date range. An email thread is considered closed (answered) when an agent closes an email thread with at least one response email.

Closed (Unanswered)

See the number of email threads closed without an answer by the given grouping for a specified date range. An email thread is considered closed (unanswered) when an agent closes an email thread with no response email.

Received

See the number of individual emails sent by the given grouping for a specified date range. Sent emails are independent of email threads.

Sent

See the number of individual emails received by the given grouping for a specified date range.

Summary

See the average of several key email metrics for a specified date range.

Time To Respond

See the response time to received emails for a specified date range. Only received emails with a corresponding reply email will be counted in this calculation.

Email Productivity reports

Create reports on your agents' productivity when answering emails.

Fastpath: report.boldchat.com > New Report > Email > Productivity

Accepted

See the number of accepted email threads by the given grouping for a specified date range. An email is considered accepted when an agent accepts or responds to an assigned email thread.

Answered

See the number of answered email threads by the given grouping for a specified date range. An email is considered answered when an agent is the first to respond to an email thread.

Assigned

See the number of assigned email threads by the given grouping for a specified date range. An email thread is considered assigned on each new assignment or re-assignment.

Closed (Answered)

See the number of email threads closed with an answer by the given grouping for a specified date range. An email thread is considered closed (answered) when an agent closes an email thread with at least one response email.

Closed (Unanswered)

See the number of email threads closed without an answer by the given grouping for a specified date range. An email thread is considered closed (unanswered) when an agent closes an email thread with no response email.

Received

See the number of individual emails sent by the given grouping for a specified date range. Sent emails are independent of email threads.

Sent

See the number of individual emails received by the given grouping for a specified date range.

Summary

See the average of several key email metrics for a specified date range.

Time To Respond

See the response time to received emails for a specified date range. Only received emails with a corresponding reply email will be counted in this calculation.

Messaging Apps Assignment Activity Summary report

This report contains details such as the number of messages sent and received, average time to respond, number of answered, ended answered and ended unanswered messages, along with average speed to answer and average time to end for answered.

Fastpath: report.boldchat.com > New Report > Messaging Apps > Messaging Apps Assignment Activity Summary
Sent
Messages sent in the specified date range.
Received
Messages received in the specified date range.
ATTR (HH:MM:SS)
Average time to respond for messages sent in reply to a received message.
Answered
Messages that were answered in the date range specified.
ASA (HH:MM:SS)
Average Speed to Answer for answered messages.
Ended Ans
Messages ended in the date range specified that were answered at some time.
Ended Unans
Messages ended that have never been answered.
ATTC (HH:MM:SS)
Average Time to End for Answered, Ended messages (from Answered to Ended).

Set up an SMS account (text messages)

To implement SMS functionality, you must configure an SMS account and provision a phone number to integrate with our SMS gateway.

Note: This feature is only available for Bold360 Plus subscribers and Bold360 AI platform accounts.

As with chat functionality, the SMS service supports department based routing, hours of availability, post-chat wrap-up, and canned messages, as well as an auto-respond feature to help you manage incoming chat requests.

Note:
  • Additional per message fees apply, check our website for block message rates.
  • The SMS service does not support sending images.
  1. Create a new SMS account:
    1. In the Web Admin Center, go to Channels > Messaging > SMS. The SMS Accounts page is displayed.
    2. Click Create New. The New SMS Account window is displayed.
  2. Set Account Settings:
    Option Description
    Name The account name. Not seen by customers.
    Department Associate incoming SMS with a department.
    Auto-End Interval End sessions automatically when a customer's response is not received within the defined period.
    Thread Ownership Choose how you want to handle the ownership of re-opened messenger threads:

    Original agent retains ownership of re-opened conversations ? When an incoming message re-opens a closed conversation, the originally assigned agent retains ownership.

    Original agent must re-accept re-opened conversations ? When an incoming message re-opens a closed conversation, the originally assigned agent must re-accept the conversation. If the owner is not available or fails to re-accept, the conversation is reassigned.

    Original agent must always re-accept conversations, even if open ? When an incoming message arrives to an open conversation, the originally assigned agent must re-accept the conversation. If the owner is not available or fails to re-accept, the conversation is reassigned.

    Business Hours Set hours of availability specific to SMS functionality.
  3. On the Auto Responder tab, configure how you want to automatically respond to incoming messages.

    Auto responder rules use regular expressions (regex) to evaluate incoming messages. When all criteria are matched, a response is triggered.

    Important: We recommend using Create Email Prompt Rules to create a set of rules that automatically asks the customer to enter their email address. The customer's email allows Digital DX to connect the customer to their history across all channels (chat, messages, email).
  4. On the Wrap Up tab, configure how you want to gather information from agents about ended sessions.
    • Set an Auto-Close Interval to determine how long an ended conversation remains in the agent workspace before closing automatically.
    • Choose the fields to show to the agent in the Wrap Up section of the agent workspace.
  5. On the Canned Message Folders tab, select the canned messages that you want to make available to agents handling this account.
  6. On the Phone Number tab, choose your Country and click Find Phone Number.

    Available countries:

    • Australia +61
    • Belgium +32
    • Canada +1
    • France +33 (Domestic SMS only)
    • Hungary +36
    • Ireland +353
    • Israel +972
    • Norway +47
    • Poland +351
    • Spain +34 (Domestic SMS only)
    • Switzerland +41
    • United Kingdom +44
    • United States +1

    Always check the Phone Number tab for the latest list of available countries.

    Tip: If you have your own Twilio account, click Show advanced setup and copy the following details from your Twilio Dashboard:
    Option Description
    Twilio Account SID The ID of the Twilio account that you use for messaging.
    Twilio Auth Token The token that authorizes calls for the defined Twilio account.
    Phone Number The phone number that has been provisioned for the Twilio account.

    Result: Once a number is provisioned for your account, the number is displayed on the Phone Numbers Dashboard in Twilio. This number is used to provide customers the ability to initiate SMS sessions from their mobile devices. If your organization supports messaging in multiple countries, then you must set up multiple Twilio accounts and define those SMS accounts one by one in Digital DX.

  7. Save your changes.

Messaging Apps Performance reports

Create reports on your agents' performance over your (additional) messaging apps channel.

Fastpath: report.boldchat.com > New Report > Messaging Apps > Performance
Note: Performance type reports do not display the agent's performance, but the overall conversation performance (including the chatbot's performance). This will be adjusted in a later release.

Messaging Apps Answer Performance Summary report

For a specified date range, analyze the distribution of the time to answer message conversations and performance within the defined time interval.

Messaging Apps Assignment Answer Performance Summary report

For a specified date range, analyze the distribution of the time to answer message assignments and performance within the defined time interval.

Messaging Apps End Time Performance Summary report

For a specified date range, analyze the distribution of the time to close message threads and performance within the defined time interval.

Messaging Apps Assignment End Time Performance Summary report

For a specified date range, analyze the distribution of the time to end message assignments and performance within the defined time interval.

Additional Configuration - Canned Messages

Canned messages are predefined strings of text that an agent can insert into a conversation. With canned messages, the agent can reuse commonly used responses without having to type them. Canned messages are managed separately by channel (Chat, Email, Messaging, Social).

Note: This article is part of a Quick Start Guide to help you implement your Bold360 environment from scratch.

To see the below steps in action, view our tutorial:

  1. In the Web Admin Center, go to Channels > Chat > Canned Messages.
  2. By default, you have two canned messages: welcome and bye. Feel free to customize either of these by clicking them and updating the body.

  3. To create a new message, click Create New.
    1. Add a Name so that agents can easily identify and reference the message.
    2. Type and format the message in the Body.

      You can include dynamic HTML variables such as agent or customer name. You can find a list of HTML variables here.

    3. In Keywords, include any words and/or phrases that help identify this message as relevant to a conversation.
    4. Agents can more easily use canned messages by adding a Shortcut. This enables agents to use a canned message without having to search for it by typing ?/[shortcutname].? (For example: ?/hello?)

  4. Save your changes.

    Result: Your new canned message is now available for responses to incoming chats.

How to use the BoldChat Web Dashboard

Enterprise subscribers can use the Web Dashboard to view a summary of account activity from anywhere ? desktop, tablet, or phone.

The Web Dashboard (https://dashboard.boldchat.com) gives you the following:

  • Real time visual data of key metrics
  • On-screen notifications for certain metrics, with customizable thresholds
  • Responsive design for easy viewing on desktop, tablet, or phone
  • A set of default charts that you can customize and expand to meet your needs

Working with the Web Dashboard

To access the Web Dashboard, log in to your enterprise account at https://dashboard.boldchat.com.

Important: To be able to edit and view the Web Dashboard, a user must have the following permission: Setup > Account Setup > General > Permission Groups > Can Access Web Dashboard.

When viewing on a desktop:

  • View charts (widgets)
  • Edit charts ? use the options menu to edit, copy, or delete a chart
  • View and acknowledge notifications
  • If you delete the last chart, you will be prompted to restore default charts upon refresh
  • Arrange charts on the screen ? drag and drop by clicking anywhere in a chart's header

When viewing on a phone or tablet:

  • View charts
  • View and acknowledge notifications

Chart types

The following charts are available to Enterprise subscribers at https://dashboard.boldchat.com.

Chart name Description User Tips Options and Filters
Chat activity A summary of chat activity in your account. By default, it shows the total number of offered chats per day for one week, including the current day. Hover above or tap a line to view additional details. Options: Total chats offered, Abandoned chats, Answered chats, Time period (Last 24 hours, 7 days, 30 days).

Filters: Department, folder, website.

Chat performance A summary of information about chats in your organization compared to target goals. Use this chart to track performance against Service Level Agreements (SLAs). Items that have missed a performance goal are shown red.

To display a notification on the Dashboard when a goal is missed, edit the report and select Notification when missed.

Columns to show: Actual, Goal, Difference.

Goal values: Average Speed to Answer (mm:ss), NPS, Overall Chat Satisfaction.

Filters: Department, folder, website.

Chat status Summary information about active and queued chats. Click the chart for details. To display a notification on the Dashboard when a chat has waited too long in the queue, edit the report , set a Notification threshold, and select Notification when exceeded.

You can choose to show details of the longest waiting chat on this chart, but this disables Department and Website filters. Click the chat to see the waiting visitor's name.

Filters: Department, folder, website (except when showing the longest waiting chat, in which case only the Folder filter is applied).
Operator rating A summary of operator ratings submitted by visitors on the post-chat survey. Items that have missed a performance goal are shown red.

To display a notification on the Dashboard when a goal is missed, edit the report and select Notification when missed.

Click the page selector at the bottom of the chart to flip through multiple pages when the number of operators exceeds five.

Filters: Department, folder
Operator status The number of operators in your organization by status: In Chat, Available, Away, Offline. Click the chart for details. Filters: Department
Visitors A summary of visitor monitoring activity on your sites, including the number of visitors on each page. The chart itself displays filtered data, while the Total Visit Count and Total Active Invitations are for the entire account. Option: Add a bar to represent each filter.

Filters: Folder.

Add a chart

  1. When viewing the Dashboard on a desktop computer (not a phone or tablet), go to the top of the Dashboard and click + (plus sign).
  2. Select the type of chart you want to add. The chart is added to the bottom of the page.
  3. Go to the bottom of the page to find the newly created chart.
  4. On the new chart, click the options menu and then Edit to customize the report.
    Tip: Don't forget to rename your chart to reflect selected filters and options.
  5. Save your changes.
Tip: To build a new report by editing an old one, click the options menu and select Copy. Go to the bottom of the page to find and edit the newly created chart.

Canned Message Summary Report

Perform Canned Message analysis and clean-up using this report that shows the most frequently used canned messages.

Fastpath: report.boldchat.com > New Report > Chat > Canned Message Summary

Report availability: Enterprise

Reported data:

Rank
Rank in terms of total usage.
Total
The number of times the canned message was used.
Note: When no custom operator filters are selected the chatbot is excluded from report.

Manage incoming messaging items according to rules (Messaging Rules Engine)

The messaging rules engine compares the properties of incoming messages against criteria and performs the rule's action when there is a match.

You must have at least one messaging folder to set up routing rules for your messages. To create a folder do the following:

  1. Create a messaging folder if you haven't done so already:
    1. In the Web Admin Center, go to Channels > Messaging > Messaging Folders.
    2. Hover your mouse over the Messaging folder and click the Create folder () icon.
    3. Name your folder.
  2. Create or edit a messaging rule, as follows:
    1. Go to Channels > Messaging > Routing Rules.
    2. On the Routing Rules for Messaging page, select an existing rule or click Create New.

    Result: The Edit/New Rule page is displayed.

  3. On the Criteria tab, name the rule.

    Each rule should have a unique name for easy identification.

  4. Select one or more criteria.
    Tip: To enter multiple values in a field, type a string and press Enter.

    Multiple selected criteria within a group are evaluated according to OR condition logic, while selected criteria across groups are evaluated according to AND condition logic.

    • Accounts
    • Phone Number Contains
    • Initial Question Contains
    • Departments
    • Message Type

    Result: The rules engine compares incoming items against the criteria and performs the rule's action when there is a match.

  5. On the Actions tab, choose how to route items when criteria are met:
    • Folder, to send the item to a specific folder
    • Department, to make the item available to members of a specific department
  6. On the Actions tab, assign attributes to an item when criteria are met:
    • Category
    • Status
    • Urgency
    • Difficulty

    Result: Agents can use this information to make decisions about how to handle or organize emails.

  7. Save the rule.
  8. Continue to create rules.
  9. Arrange rules in the order they should be evaluated (Move Up, Move Down).
    Important: Rules are evaluated in the order they appear in the rules list.

Set up automatic distribution for messaging

Automatic distribution for messaging allows you to automatically and intelligently distribute assignment of new, incoming message threads to your agents.

  1. In the Web Admin Center, go to Channels > Messaging > Automatic Distribution.

    Result: The Automatic Distribution for Messaging page is displayed.

  2. Select Enable automatic distribution.

    Result: This activates AD for all incoming messages in your account.

  3. Options:
    Option Description
    Reassign unanswered messages (seconds) When selected, SMS threads are reassigned to another agent when the originally assigned agent does not accept the thread within the specified period of time.

    An agent who fails to answer in time is set to Away status to prevent new threads from being assigned.

    Concurrent message limit When selected, the number of threads that can be assigned to each agent is limited. When an agent reaches the limit, they are no longer assigned new threads. This limit setting can be overridden at an individual agent level.
    Agents waiting for assignment When there are fewer incoming threads than agents can handle, some agents will be waiting for an assignment. Threads are assigned to highest ranked agents first, but you can choose an assignment method for agents of the same rank.

    To determine which waiting agent gets the next item, choose an assignment method:

    • Least Busy. Assign the next incoming thread to the agent who has the fewest active threads and has waited the longest. Choose this to balance the workload between agents.
    • Most Busy. Assign threads to your busiest agents. The next incoming thread is assigned to the agent who is handling the most threads until their limit is reached, and thereafter to the agent who has been idle for the shortest period of time. Choose this option if your agents must manage non-messaging tasks along with their messaging related work. Those who are managing messages will stay busy with messages, while others can stay focused on non-messaging tasks. To prevent overload on a single agent, make sure concurrent limits are set.
    • Round Robin Rotate assignment among all available agents regardless of waiting time or number of active threads (until their concurrent limit is reached). Choose this option to balance the number of threads assigned per agent. Lower ranked agents will only be assigned a thread if all higher ranked agents have reached their limit.
  4. Under Manual Reassignment, tell Bold360 how to place customers into the queue when they are reassigned by an agent rather than AD.

    You can set this option independently for customers reassigned within a department (From same department) as opposed to between departments (From other departments).

    Note: For answered items that are manually reassigned, the queue time is always reset. For automatically assigned items, customers always maintain their place in the queue.
    • To place customers at the end of the queue regardless of how long they have been waiting, select Move to end of queue (time is reset)
    • To place customers in the queue based on time already spent waiting, select Maintain place in queue (time is preserved)
  5. Save your changes.

    Result: Settings are applied to your entire account except where overridden at the department or agent level.

Canned messages for agents

Canned messages are predefined strings of text that an agent can insert into a conversation. With canned messages, the agent can reuse commonly used responses without having to type them.

  1. Choose the channel for which you want to create or edit a canned message:
    • Chat: Channels > Chat > Canned Messages
    • Email: Channels > Email > Canned Messages
    • Messaging: Channels > Messaging > Canned Messages
  2. Create, edit, or copy a canned message on the Canned Messages page, as follows:
    • To create a new message, click Create New
    • To edit, click an existing message
    • To copy, click the Copy icon next to an existing message
  3. Name and identify the message so agents can find it:
    Option Description
    Name This is never seen by customers; used to identify and reference the message.
    Subject For messages that are auto answers, the subject is shown to customers as a label in search results.
    Keywords Enter words and phrases that help identify this message as relevant to a conversation.
    Shortcut To use this message, agents can type this shortcut as a /slash command (for example, /shortcutname)
  4. Set the message's Language.

    This value acts as a filter to ensure that agents see only messages that match the customer's language or with no value specified. For example, when an Italian speaking customer starts a chat, the agent sees Italian canned messages plus those with no language value.

    Result:

    Tip: Subject, Keywords, and Body should use the same language.
  5. Type and format the message.
    Channel Options
    Chat HTML* or plain text
    Email HTML* or plain text
    Messaging Plain text
    *HTML Variables For HTML, you can insert variables in ${variable_name} format. For example, use the variable ${login.ChatName} to insert the agent's chat name into the canned message.

    Available variables:

    • ${chat.ChatUrl} - The URL of the chat from where the customer started the chat session
    • ${chat.ChatName} - The name of the customer as provided on the pre-chat form. If the First name field is available on the pre-chat form then this variable displays only the first name of the customer.
    • ${chat.CountryCode} - The two-digit code of the country where the customer started the conversation
    • ${chat.RegionCode} - The region or ZIP code of the country where the customer started the conversation
    • ${chat.City} - The city where the customer started the conversation
    • ${chat.VisitEmailAddress} - Email address of the customer as provided on the pre-chat form
    • ${chat.VisitPhone} Phone number of the customer as provided on the pre-chat form
    • ${login.UserName} - The User Name of the agent as set on the Organization > Agents > Agent Information tab
    • ${login.Name} - The Agent Name of the agent as set on the Organization > Agents > Agent Information tab
    • ${login.EmailName} - The Email Name of the agent as set on the Organization > Agents > Email Settings tab
    • ${login.BestChatName} - The Chat Name of the agent. If this is unavailable, then the Agent Name of the agent.
  6. Save your changes.

    Result: The canned message is made available for responses to incoming conversations for the chosen channel (Chat, Email, or Messaging).

Remember: Messages that will be used as Auto Answers must be organized in folders as part of Chat Window setup.

What's the difference between canned messages and the Smart Advisor?

The enhanced Smart Advisor 2.0 suggests answers to the agents in real-time based on what the visitor is asking in the chat.

Agents can use both Smart Advisor articles and canned messages in the Agent Workspace. While canned messages are defined in the Web Admin Center, the Smart Advisor panel displays articles taken from a selected AI knowledge base. This knowledge base is selected when Agent and AI are integrated. For more information, see Integrate a chatbot.

The main difference between the two sets of messages is that Smart Advisor offers results in real-time, based on the customer's questions; whereas an agent has to search manually from available canned messages while chatting with a customer. In addition, an agent can suggest an answer as a knowledge base article and this way help improve the knowledge base.

Smart Advisor: Chatbot-assisted conversations

When chatting with a customer, Smart Advisor offers agents potential answers to customer questions either based on the content of the chat conversation or by manual search.

These instant answers ultimately provide better user experience and increase agent efficiency: they allow agents to spend less time searching for answers, and improve Average Speed to Answer (ASA) in reporting.

Note: This feature is only available with a Bold360 AI platform account.

Important: You must have the Actions > Chats > Suggest response as Smart Advisor article permission enabled to use this feature.

During a conversation with the chatbot, customers have the option to connect to an available agent, if there are any. When the chat is transferred, the agent can view the full history of the conversation between the customer and the chatbot and continue that thread. The customer and the agent always use the same set of knowledge base articles.

When the customer sends a message to an agent, the chatbot analyzes that message and offers the most relevant answers to the customer's messages. These answers are listed on the Smart Advisor panel, which replaces the Canned Messages panel when the customer chats in a Bold360 ai chat window. Smart Advisor considers only those customer messages that have been sent since the agent's last interaction.

To copy the best answer to the message panel, click that response. You can edit your message before sending.

If your articles have contexts as well, you can select the relevant article variation from Smart Advisor panel.

Search Smart Advisor for help

You can manually search Smart Advisor articles when you are looking for results not listed automatically. To do so, type your question in the Search field. Automatic suggestions are provided as you type. Titles of the relevant articles are listed dynamically as you type your question. To see the content of an article, click its title. All previously displayed results are removed from the Smart Advisor panel.

To get the best search results, consider the following:

  • Grammatically accurate words return more relevant answers
  • Avoid very long phrases and generic statements

How to rate a Smart Advisor response

When Smart Advisor offers you responses, agents can always rate those responses.

  1. Click the arrow on the right of the suggested response to expand the article if not fully visible.
  2. Click Yes or No at the bottom of the article to rate whether the article was helpful.

    When you rate an article as not helpful, you can further categorize the problem with the article and suggest improvements. This rating improves the results that Smart Advisor provides.

How to suggest a response as a Smart Advisor article

When you cannot find a relevant answer to a frequent question, you can suggest your response as a Smart Advisor article. After approval, these articles are immediately available to every agent. To make a suggestion, do the following:

  1. Hover the mouse over one of your previous answers.
  2. Click Suggest as article .

Your answer must first be approved by a Bold360 ai knowledge base content manager before it becomes an article. You will not get any notification when your answer is approved.

Digital DX AI setup

The Digital DX AI platform offers customers chatbot-enabled self-service and introduces Smart Advisor, which provides agents with the best possible answers to customer questions during chat. The chatbot handles customer queries and provides a consistent front-line customer care experience. This way, Digital DX delivers the best of both chatbots and agents to solve customer issues.

Note: This feature is only available with a Digital DXAI platform account.

With your Digital DX AI platform account, you also get access to the Web Admin Console, where you can customize your AI-enabled chat window. Here you can also manage the content of the knowledge base that contains help articles that both the chatbot and the Smart Advisor panel show. The Digital DX AI platform is a service that provides a chat window with AI-enabled customer assistance after it is integrated into Digital DX. The layout of the chat window and the content of the help articles are controlled by the AI Console.

To use Digital DX AI, you must set up a link between the Web Admin Center and the AI Console by creating API keys:

  • To use the chatbot, create an API key, which connects the Digital DX AI and Agent platforms
  • To set up channeling, create a Digital DX Agent API access key. Depending on the number of channeling paths, you may have to create multiple Digital DX API access keys.

If set up correctly, customers receive self-service help from the chatbot and agents can use Smart Advisor to answer customer queries. See Smart Advisor: Chatbot-assisted conversations.

About channeling

When your customers request help from a human agent while interacting with the bot, the chat is escalated to a live agent in your organization. In the Web Admin Console (for the AI platform), chat escalation is called channeling. You may set up multiple channels to cater for your customers' needs. For example, you may use different knowledge bases to serve different audiences, in which case you must set up a channel for each knowledge base. With the Digital DX Agent API access key, channel settings are linked to a chat window and during channeling these settings are applied.

Whether customers receive help from the bot or chat with a live agent, they see the same chat window. Customers do not experience any change when a chat is seamlessly transferred from the chatbot to a live agent. They continue the conversation in the same window.


Figure 1. Customer's view when Digital DX AI is activated

Multi-Service Productivity report

Use this report to see how much time agents spend on each type of work item.

For each agent you can see the time spent assigned to different service items in Available, Away, Assigned, or Idle status and a utilization calculation in percentage. It also reports the time spent handling concurrent assignments, and the maximum number of assignments.

Fastpath: report.boldchat.com > New Report > Login > Multi-Service Productivity

Reported data:

Available

Total time logged in as Available.

Away

Total time logged in as Away.

Available (Assigned Time)

Total time in Available status with at least one item assigned.

Away (Assigned Time)

Total time in Away status with at least one item assigned.

Available (Idle Time)

Total time with no assignments (accepted or answered) while Available.

Away (Idle Time)

Total time with no assignments while Away.

Available (Utilization)

Percentage of time with at least one item assigned while Available.

Away (Utilization)

Percentage of time with at least one item assigned while Away.

Working

Percentage of time either in Available status, or with at least one item assigned in Away status.

Multi-assignment

Time spent on more than one simultaneous assignment while Available.

Total Assignment Time

Total time assigned to items counted separately while Available. For example, when an agent works on three chats simultaneously for 20 minutes each then the agent's Available (Assigned Time) is 20 minutes but the Total Assignment Time is one hour.

Assignments

Total number of assignments accepted or answered.

Max Simult

Greatest number of simultaneous assignments (any service type) for the given period.

How to automatically activate chats (Automatic Chat Distribution)

Use Automatic Chat Distribution (ACD) to automatically place agents in an active chat session without agent interaction.

For example, you can automatically invite customers to chat with an agent when they have been on a particular page for a certain time, clicked a link or revisited a URL. Automatic Chat Distribution balances the number of customers in queue and the agent's workload in order to keep the rate of invitations at a maintainable level and the agent's chat queue saturated.

  1. In the Web Admin Center, go to Channels > Chat > Automatic Distribution.

    Result: The Automatic Distribution for Chat window is displayed.

  2. Select Enable automatic distribution.

    Result: This activates ACD at the account level.

  3. Select the following options:
    Option Description
    Initial assignment delay When Automatic Chat Distribution is enabled, you can delay the automatic assignment of chat sessions by the defined time. This way, you can keep chats in queue - in unassigned status - for an extended period.
    Reassign unanswered messages (seconds) When selected, chats are reassigned to another agent when the originally assigned agent does not answer the chat session within the specified period. In practice this means that a chat is answered by another agent when the originally assigned agent fails to respond.

    An agent who fails to answer in time is set to Away status to prevent new chats from being assigned. The agent must then explicitly set their status to Available.

    Reassign messages after agent disconnected (seconds) When an agent disconnects (for example, after logging out), Automatic Distribution reassigns all active chats to other agents after the defined period of time. When the agent disconnects due to network connectivity issues, chats are reassigned after at least two minutes. Therefore, even if you set the Reassign messages after agent disconnected value to 30 seconds, chats will only be reassigned after two minutes. Keep in mind that if no agents are available to take additional workload then chats will be placed in queue and their waiting time will be counted from the time the customer started the chat.
    Concurrent chat limit When selected, the number of chats that can be assigned to each agent is limited. When an agent reaches the chat limit, they are no longer assigned new chats. This limit setting can be overridden at an individual agent level. Chat and discussion difficulty affects this limit.
  4. If you choose to limit concurrent chats, the following options are also available:
    Option Description
    Show queue position When no agents are eligible to receive new chats (all have reached their maximum concurrent chats limit), then new chats are placed in a queue. When selected, customers see their position in the queue in the chat window. Agents can manually start chatting with the next customer in queue as described in How to manually start chatting with the next customer in queue.
    Estimated wait time With this option it is possible to display the approximate waiting time to visitors who are waiting in the queue for agent chat. This option can be enabled if the Show queue position option is active. The estimated wait time is calculated based on previous wait times and the visitor's position in the queue.
    Enable exit from queue When selected, customers in the waiting queue are presented a button that cancels the chat and displays the unavailable form (if enabled).
    Queue length limits

    Maximum in queue: Do not allow new chat sessions when the total queue size reaches this number.

    Average per agent: Disable the Chat Button when the total number in the queue divided by the number of available agents reaches this number.

    Invitation throttling

    The invitation throttle controls the balance between the number of invitations sent and the risk that your target queue is exceeded. This helps you avoid long queues of unassigned chats when more customers accept invitations than agents can handle.

    Throttling options:

    • Target queue size. The target number of chats that you are willing to leave queued for assignment. The invitation throttle adjusts the number of invitations sent in order to optimize queue size.

      Note: The target queue size is independent of the Disable chat queue size setting. Chat becomes unavailable when the target queue size reaches a number equal to or less than the Disable chat queue size. You are recommended to set a higher threshold for the Disable chat queue size setting than your target queue size.
    • Expected acceptance rate. The expected likelihood that an invitation will be accepted. You can choose your own percentage or use the calculated value, which is based on a moving average of the actual acceptance rate over approximately one week for the given account or department.

    • Throttling rate. This is your willingness to risk that more invitations will be accepted than your target queue size. When you choose a lower risk option, fewer invitations are sent, thus decreasing the potential number of acceptances. The options represent a 50%, 5% and 0.1% probability that you will exceed the target queue size, assuming that the expected acceptance rate is accurate.

      Note: For optimal results, make sure that the expected and real acceptance rates correlate closely. If the rates diverge, either you will not be sending out as many invites as you are able to handle, or your target queue size will be frequently exceeded.
    Allow customers to enter queue upon Available click Decide how to handle new chat sessions when a customer clicks a button shown as Available, but meanwhile all agents become unavailable. You can override other queue limits and allow them to enter the queue according to the following limits:
    • Max. in queue upon Available click: Allow the queue to reach this limit before preventing new chat sessions.
    • Concurrent chat limit upon Available click: Allow agents to reach this limit before they are no longer assigned chats.
  5. Define the difficulty level for chats and discussions. These limits are used to calculate agent chat capacity when concurrent chat limit is enabled.
    Note: You can change chat difficulty at department level only.
    How is agent chat capacity calculated?

    Suppose concurrent chat limit is set to 3, chat difficulty has a multiplier of 1, and chat discussion difficulty has a multiplier of 0.5. When an agent has two ongoing chats (counts as 2 x 1 concurrent chats) and a chat discussion (counts as 1 x 0.5 concurrent chat) then the concurrent limit is 2.5. In this case, - since chat capacity is 0.5 - the agent can still receive an additional discussion task, but cannot receive new chats.

  6. When there are fewer incoming chats than what agents could handle, some agents will be waiting for an assignment. Chats are assigned to highest ranked agents first, but you can choose an assignment method for agents of the same rank. See How to assign chats to certain agents before others (ranking within department).
    Option Description
    Agents waiting for assignment

    To determine which waiting same-rank agent gets the next chat, choose an assignment method:

    • Least Busy. Assign the next incoming chat to the agent who has the fewest active chats and has waited the longest. This naturally means that if you have multiple agents available with no chats, ACD will assign the next incoming chat to the agent who has been in Available status for the longest period of time.

      Choose this to balance the chat workload between agents.

    • Most Busy. Assign chats to your busiest agents. The next incoming chat is assigned to the agent who is handling the most chats until their limit is reached, and thereafter to the agent who has been idle for the shortest period of time. Choose this option if your agents must manage non-chat tasks along with their chat related work. Those who are chatting will stay busy chatting, while others can stay focused on non-chat tasks. To prevent overload on a single agent, make sure concurrent chat limits are set.
    • Round Robin Rotate chat assignment among all available agents regardless of waiting time or number of active chats (until their concurrent limit is reached). Choose this option to balance the number of chats assigned per agent. Lower ranked agents will only be assigned a chat if all higher ranked agents have reached their limit.
    Note: If you are using difficulty-based distribution, chats are assigned to the agent within the same rank who is working on chats with the lowest total relative difficulty. For example, an incoming chat will be assigned to an agent handling one difficulty 3 chat before an agent who is handling four difficulty 1 chats.
  7. Under Manual reassignment, tell Bold360 how to place customers into the queue when they are reassigned by an agent rather than ACD.

    You can set this option independently for customers reassigned within a department (From same department) as opposed to between departments (From other departments).

    Note: For answered items that are manually reassigned, the queue time is always reset. For automatically assigned items, customers always maintain their place in the queue.
    • To place customers at the end of the queue regardless of how long they have been waiting, select Move to end of queue (time is reset)
    • To place customers in the queue based on time already spent waiting, select Maintain place in queue (time is preserved)
  8. Save your changes.

    Result: Settings are applied to your entire account except where overridden at the department or agent level.

Provide a chat window in multiple languages

You can set a chat window to be displayed in any of seven pre-translated languages or 35 custom languages. There is no need to create multiple chat windows for multiple languages.

This feature is part of the chat window setup. A chat window controls the look and feel and advanced behavior of the interface that is opened when a customer clicks an associated button or link. Multi-language set-up for chat windows is part of the customization procedure.
  1. Create or edit a chat window, as follows:
    1. In the Web Admin Center, go to Channels > Chat > Chat Windows.
    2. Select an existing chat window or click Create New.
  2. On the Customization tab under Languages, choose the languages in which you want the chat window to be made available.
  3. Set a Primary Language.

    The primary language is shown to customers when no translation is available in their own language.

    Example: For example, if English is your default language, a customer from Poland sees the chat window in English unless you specifically select Polish as a provided language and add a Polish translation.

  4. Customize the window and translations, as follows:
    1. Select an item under Main group > Key group > Key.
    2. Under Edit Content, choose the language you want to edit.
    3. Change the text or settings.
    4. Continue making other changes.
    5. Save your changes.
    Remember: Digital DX provides translations in the following languages: English (en-US), Dutch (nl-NL), French (fr-FR), German (de-DE), Italian (it-IT), Spanish (es-ES), Portuguese (pt-BR). For all other languages, you must provide your own translations.
  5. Save your changes.
Can I allow customers to choose a language on the pre-chat form?
Yes. Go to Channels > Chats > [New Chat Window] > Pre-chat form > Standard Fields > Language Selector.
How does Digital DX know which language to show to a customer?
Customer language is determined as follows:
  • Selection made by the customer on the pre-chat form (stronger than all other parameters)
  • Language parameter passed by the HTML snippet
  • Customer's browser language setting
  • Customer's IP

Digital DX looks for a customized (localized, translated) chat window for the chosen or detected language. If no customized window exists, the default language is shown.

Tip: The customer's language is saved as a property of the chat. This property can be used for routing chat, and can be displayed to the agent. A language property can also be set for departments, allowing automatic filtering.

Troubleshooting Bold360

A checklist of the most common communication issues when logging in to Bold360.

Connection issues due to proxy settings

You may encounter connection issues if your proxy is not configured properly. Since Bold360 uses the proxy settings of Internet Explorer, try resetting your browser to use default settings:

  • In Windows 10, go to Windows Settings > Apps. On the Apps & features tab, search for Microsoft Edge. Select it and click Advanced options, then click Reset.
  • In Windows 8.1 or prior, open Internet Explorer and go to Settings (gear icon) > Internet options. On the Reset Internet Explorer settings pane on the Advanced tab, click Reset.

ACD Summary report

This reports shows Automatic Distribution performance in your environment.

Fastpath: report.boldchat.com > New Report > Chat > ACD Summary

Includes total chats assigned automatically to agents (offered), the number of chats that ended before the agent could answer it (abandoned), and the number of chats taken away from an agent and given to another because the customer's wait time exceeded your threshold (reassigned), chats that went unanswered and answered. The report also includes useful operational data like average message count, the average duration of chats, and the maximum number of customers waiting in queue and the maximum wait time for any chat.

Offered, abandoned, and reassigned chats are counted only once. For example, if the same chat was abandoned by the same agents more than once, it nonetheless shows in the report as one chat.

Offered
Chats started from a clicks or invites.
Abandoned
Chats started and ended but never answered.
1st Answer
Chats answered the by the first agent it is assigned to.
Reassigned
Chats reassigned from the agent it had been assigned.
ASA
Average Speed to Answer for Answered Chats. Time from when the chat Started to the time it was Answered by the agent.
ACT
Average Chat Time for answered chats. Time from answering a chat until it ends, specifically, all the time between the first agent answering the chat and the final agent assigned to the chat when it ends, adds up to the ACT calculation for the final agent.
AMC
Average Message Count for answered chats.
Max #
Maximum size of chat queue.
Max Time
Maximum wait time for any abandoned or answered chats.
Note: For Digital DX Service subscribers, the calculation method of certain chat report metrics are affected by conversations with the chatbot as described in Chat reports involving a chatbot. When no custom operator filters are selected, chats assigned to the chatbot are excluded from report.

Chat Assignment report

Analyze the flow of chat-work across your organization.

Includes data for chats that were assigned by Automatic Distribution, re-assigned by the AD, and/or transferred by another agent.

Tip: Offered, abandoned, and reassigned chats are counted only once. For example, if the same chat was abandoned by the same operators more than once, it nonetheless shows in the report as one chat.
Fastpath: report.boldchat.com > New Report > Chat > Chat Assignment
Offered
All chats assigned to an agent or department.
Answered Chats
All chats answered by a live agent.
Transferred
All chats transferred by an agent or ACD.
ACT
Average Chat Time for answered chats that were transferred. Time from answering to transfer.
AMC
Average Message Count for answered chats that were transferred.
ASA
Average Speed to Answer for answered chats. Time from agent receiving assignment to the time it was answered.
Note: For Digital DX Service subscribers, the calculation method of certain chat report metrics are affected by conversations with the chatbot as described in Chat reports involving a chatbot. When no custom operator filters are selected, chats assigned to the chatbot are excluded from report.

Facebook Messenger Login reports

See the amount of time that your agents spent on handling Facebook messages.

Fastpath: report.boldchat.com > New Report > Login

Trouble logging in to your Facebook account?

FB Messenger Login Summary

See the amount of time that your agents spent logged in Digital DX with regards to handling Facebook Messenger conversations. For a given date range, this report shows the number of hours and minutes each agent was logged in as either Available or Away. A breakdown by Digital DX client application is also included.

Reported data:

Operator
Name of the agent.
FB Messenger Available - Total
The total time the agent spent in available status.
FB Messenger Available - .NET
The total time the agent spent in available status in the Desktop Client.
FB Messenger Available - Web
The total time the agent spent in available status in Agent Workspace.
FB Messenger Available - Mobile
The total time the agent spent in available status in the iPhone app or using the web client on a mobile device.
FB Messenger Away - Total
The total time the agent spent in Away status.
FB Messenger Away - .NET
The total time the agent spent in Away status in the Desktop Client.
FB Messenger Away - Web
The total time the agent spent in Away status in Agent Workspace.
FB Messenger Away - Mobile
The total time the agent spent in Away status in the iPhone app or using the web client on a mobile device.
% Forced
Percentage of total Away time that was forcibly put in Away status by ACD for not answering an item.

FB Messenger Login Details

See the time of day associated with both login and logout behavior of agents with regards to handling Facebook Messenger conversations. The report can be grouped by date or agent and shows the time of day associated with a variety of login/logout behavior. The report shows the client the agent used and what action they took, whether that was logging in as Available or Away, or logging out.

Reported data:

Operator
Name of the agent.
Time
The time of changing the agent's status.
Client
The client where the agent's status was changed.
Action
The action that was taken to change the agent's status.

Chat reports involving a chatbot

For Digital DX AI subscribers, some report data include conversations with the chatbot. To understand the impact of conversations that involve the chatbot, the following must be considered.

  • Available means that a live agent was available for chat when the conversation started. Any conversation where the customer only chats with the bot are disregarded from reports on availability.

  • Unavailable counts chat button clicks when no one is logged in as available. Since the chat bot is always available, this number will always be 0 for chats channeled from the bot. When counting unavailable agents, Digital DX checks specifically for ChatType 3, whereas bot chats are of ChatType 8 ("API initiated").
  • A chat is Created when the customer opens the chat window. Hence any report detail that calculates time from chat creation includes conversations with the bot.

  • A chat is Started when the bot answers the customer. When the customer requests help from a live agent and fills in the pre-chat form if there is one, then Start time of the chat is reset.

  • A chat is Abandoned in the following cases:

    • the customer opened the AI chat window but did not chat with the bot.
      Note: When the customer opens an AI chat window, the chat is assigned to the bot operator. Therefore, those reports that filter out the bot operator, will not include this chat.
    • the chat was transferred from the bot to a live agent and the customer was presented with a pre-chat form but the window was closed without filling in the pre-chat form. In this case, the chat is not assigned to an operator, so it appears as <None> in the Operator column of reports grouped by Operator
  • An Unanswered chat was never answered by a live agent. Unanswered chats include all conversations where the customer chatted with the bot but the conversation was never transferred to a live agent.

  • Unanswered Time also includes all conversations where the customer chatted with bot but the conversation was never transferred to a live agent.

  • Conversations with the chatbot are also included in the Average Message Count (AMC).

  • Average Speed to Answer (ASA) calculates time from chat Started to Answered by a live agent. Conversations with only the bot are disregarded.

  • Average Chat Time (ACT) for answered chats does not include time when the customer chatted with the bot. It only considers time from the live agent accepting the chat to ending the chat.

The following reports are affected by conversations with the chatbot:

Service-Level Analysis report

See a quick report on the customer support your agents provide.

Fastpath: report.boldchat.com > New Report > Chat > Service-Level Analysis

Answered

See how quickly your organization is answering incoming chats. For all answered chats, the number and percent answered within various amounts of time. The report can be filtered in numerous ways and grouped by date, day of the week, hour, or agent.

Unanswered

See how long you're keeping would-be chatters waiting until they give up on reaching an agent. For all unanswered chats the number and percent that were unanswered within various amounts of time. The report can be filtered in numerous ways and grouped by date, day of the week, hour, or agent.

Chat Duration

See how much time your chats are taking from start to finish. For all answered chats, the number and percent that lasted within various amounts of time. The report can be filtered in numerous ways and grouped by date, day of the week, hour, or agent.

Average Time in Queue

Average Time in Queue answers the following question: How many chats were in the unassigned queue for various amounts of time before being assigned? Each row represents a date, period, or agent. Each column is an amount of time. For a given date, period, or agent, each cell is the number of chats that waited the given amount of time before assignment.

  • Time in queue represents the time from when the customer initiates a chat request (or submits a chat form) until the chat is assigned to an agent, abandoned, or closed
  • The time when a chat is assigned is not the same as when it is accepted by the agent
  • Results also include closed chats (abandoned, not assigned)
  • The Immediate column includes chats that enter the queue and are assigned in less than 2 seconds
  • For chats that are reassigned, time spent in queue is cumulative (each chat is represented only once, but the value in the appropriate time column is the total time spent across all queues)
  • To view time spent in an individual agent's or department's queue for chats that are reassigned, you must filter by agent or department
  • When filtering by agent and grouping by Last Operator, time values represent time in the filtered agent's queue, not the last agent's queue
Note: For Digital DX Service subscribers, the calculation method of certain chat report metrics are affected by conversations with the chatbot as described in Chat reports involving a chatbot. When no custom operator filters are selected, chats assigned to the chatbot are excluded from report.

How can I run a saved report?

Digital DX AI allows you to reuse saved or pre-defined reports. The saved reports are either defined globally as part of Digital DX AI as a product, or at your account level.

For more information on how to create and save a new report, see How can I generate my own reports in Digital DX AI?.

To run a predefined report do the following:

  1. Go to Analytics > Reports.
  2. Select the report of interest from the-drop down list.

  3. Define the date range and refine the field definitions.
  4. Run the report.

    Result: The report will be displayed on the same page, and it can also be downloaded as a CSV or Excel file.

  5. The download can be provided in full detail or if you want the summary view as presented on the screen, select the export view to Excel option.

To save a report for future use, select Save, define the name of the report and save it.

How to use reporting in Digital DX

You can generate reports based on predefined report templates. Some reports are available only with Premier or Enterprise.

Except where noted, reports are available for all editions using both the Web Reports site and the Desktop Client. We encourage you to use Web Reports due its powerful sorting and filtering options.

Tip: The Desktop Client exports data in CSV format. To ensure CSV compatibility, set your region under Setup > General Account Settings > Region before exporting.
Note: All Email reports and most Chat reports offer up to four Department filters:
  • Department (Operator membership) ? Show chats/emails assigned to an operator who belongs to this department
  • Department (First assignment) ? Show chats/emails that were assigned to this department before any other
  • Department (Last assignment) ? Show chats/emails that have this department as their most recent assignment
  • Department (Any assignment) ? Show chats/emails that were assigned to this department at any time
    • The Department (Any assignment) filter does not recognize chats that are assigned to a department but not to a specific operator. This may happen under certain circumstances:
      • When ACD is off and a chat is assigned to a department but not to an operator.
      • When ACD is on and a chat is assigned to an offline department but not to an operator. (Assignment to an offline department can happen manually, due to a rule, or when assignment is made to a department with a queue.)

For detailed information on reports, see the complete list of Digital DX reports.

Chat Login reports

See the amount of time that your agents spent logged in to and out of Digital DX.

Fastpath: New Report > Login

Chat Login Summary report

See the amount of time that your agents spent logged in to Digital DX.

For a given date range, this report shows the number of hours and minutes each agent was logged in as either available or Away.

Reported data:

Operator
Name of the agent.
Chat Available - Total
The total time the agent spent in available status.
Chat Available - .NET
The total time the agent spent in available status in the Desktop Client.
Chat Available - Web
The total time the agent spent in available status in Agent Workspace.
Chat Available - Mobile
The total time the agent spent in available status in the iPhone app or using the web client on a mobile device.
Chat Away - Total
The total time the agent spent in Away status.
Chat Away - .NET
The total time the agent spent in Away status in the Desktop Client.
Chat Away - Web
The total time the agent spent in Away status in Agent Workspace.
Chat Away - Mobile
The total time the agent spent in Away status in the iPhone app or using the web client on a mobile device.
% Forced
Percentage of total Away time that was forcibly put in Away status by ACD for not answering an item.

Chat Login Details report

See the time of day associated with both login and logout behavior of agents. The report can be grouped by date or agent and shows the time of day associated with a variety of login/logout behavior. The report shows the client the agent used and what action they took: log in as Available or Away, log out.

Report availability: Enterprise

Reported data:

Operator
Name of the agent.
Time
The time of changing the agent's status.
Client
The client where the agent's status was changed.
Action
The action that was taken to change the agent's status.

FB Messenger Assignment Status Summary report

This report provides the status of new messenger assignments assigned in the date range specified. Facebook Messenger reports are only available for Digital DX subscribers.

Fastpath: report.boldchat.com > New Report > FB Messenger > FB Messenger Assignment Status Summary

It includes details about the number of unanswered and answered messages for open as well as ended assignments.

New
New messages created in the date range specified.
Unans/Open
New messages still unanswered and open.
Ans/Open
New messages answered and still open.
Unans/Ended
New messages currently closed and unanswered.
Ans/Ended
New messages currently closed and answered.

FB Messenger Status Summary report

This report provides the status of new conversations created in the date range specified. Facebook Messenger reports are only available for Digital DX subscribers.

Fastpath: report.boldchat.com > New Report > FB Messenger > FB Messenger Status Summary

It includes details about the number of unanswered and answered messages for open as well as ended conversations.

This report provides the status for new messages created in the date range specified. All new messages are accounted for in one of the categories to the right of the New column.

Dates with no new, answered, or closed messages are not displayed on the report. The first date in this report indicates the status of all text messages prior to the date range specified.

New
New messages created in the date range specified.
Unans/Open
New messages still unanswered and open.
Ans/Open
New messages answered and still open.
Unans/Ended
New messages currently closed and unanswered.
Ans/Ended
New messages currently closed and answered.

FB Messenger Assignment Activity Summary report

This report contains details such as the number of messages sent and received, average time to respond, number of answered, ended answered and ended unanswered messages, along with average speed to answer and average time to end for answered. Facebook Messenger reports are only available for Digital DX subscribers.

Fastpath: report.boldchat.com > New Report > FB Messenger > FB Messenger Assignment Activity Summary
Sent
Messages sent in the specified date range.
Received
Messages received in the specified date range.
ATTR (HH:MM:SS)
Average time to respond for messages sent in reply to a received message.
Answered
Messages that were answered in the date range specified.
ASA (HH:MM:SS)
Average Speed to Answer for answered messages.
Ended Ans
Messages ended in the date range specified that were answered at some time.
Ended Unanswered
Messages ended that have never been answered.
ATTC (HH:MM:SS)
Average Time to End for Answered, Ended messages (from Answered to Ended).

FB Messenger Activity Summary report

The report contains details such as the number of messages sent and received, average time to respond, number of answered, ended answered and ended unanswered messages, along with average speed to answer and average time to end for answered. Facebook Messenger reports are only available for Digital DX subscribers.

Fastpath: report.boldchat.com > New Report > FB Messenger > FB Messenger Activity Summary

See activity for a specified date range.

Sent
Messages sent within the specified date range.
Received
Messages received within the specified date range.
ATTR (HH:MM:SS)
Average time to respond for sent messages that were in reply to a received message.
Answered
Messages that were answered within the specified date range.
ASA (HH:MM:SS)
Average Speed to Answer for answered messages.
Ended Ans
Messages ended in the specified date range that were answered at some time.
Ended Unanswered
Messages ended that have never been answered
ATTC (HH:MM:SS)
Average Time to End for Answered, Ended messages (from Answered to Ended)

Email Login reports

See the amount of time that your agents spent on handling emails.

Fastpath: report.boldchat.com > New Report > Login

Reports' availability: Enterprise

Email Login Summary

See the amount of time that your agents spent logged in to BoldChat to handle email. For a given date range, this report shows the number of hours and minutes each agent was logged in as either available or Away. A breakdown by client application is also included.

Results are not returned for agents with no login activity.

Reported data:

Operator
Name of the agent.
Email Available - Total
The total time the agent spent in available status.
Email Available - .NET
The total time the agent spent in available status in the Desktop Client.
Email Available - Web
The total time the agent spent in available status in Agent Workspace.
Email Available - Mobile
The total time the agent spent in available status in the iPhone app or using the web client on a mobile device.
Email Away - Total
The total time the agent spent in Away status.
Email Away - .NET
The total time the agent spent in Away status in the Desktop Client.
Email Away - Web
The total time the agent spent in Away status in Agent Workspace.
Email Away - Mobile
The total time the agent spent in Away status in the iPhone app or using the web client on a mobile device.
% Forced
Percentage of total Away time that was forcibly put in Away status by ACD for not answering an item.

Email Login Details

See the time of day associated with login and logout actions for agents handling email. The report can be grouped by date or agent and shows the time of day associated with a variety of login/logout behavior. The report shows the client the agent used and what action they took, whether that was logging in as Available or Away, or logging out.

Results are not returned for dates with no login activity.

Reported data:

Operator
Name of the agent.
Time
The time of changing the agent's status.
Client
The client where the agent's status was changed.
Action
The action that was taken to change the agent's status.

SMS Login reports

See the amount of time that your agents spent on handling text messages.

Fastpath: report.boldchat.com > New Report > Login

SMS Login Summary

See the amount of time that your agents spent logged in BoldChat with regards to handling SMS. For a given date range, this report shows the number of hours and minutes each agent was logged in as either Available or Away. A breakdown by BoldChat client application is also included.

Reported data:

Operator
Name of the agent.
SMS Available - Total
The total time the agent spent in available status.
SMS Available - .NET
The total time the agent spent in available status in the Desktop Client.
SMS Available - Web
The total time the agent spent in available status in Agent Workspace.
SMS Available - Mobile
The total time the agent spent in available status in the iPhone app or using the web client on a mobile device.
SMS Away - Total
The total time the agent spent in Away status.
SMS Away - .NET
The total time the agent spent in Away status in the Desktop Client.
SMS Away - Web
The total time the agent spent in Away status in Agent Workspace.
SMS Away - Mobile
The total time the agent spent in Away status in the iPhone app or using the web client on a mobile device.
% Forced
Percentage of total Away time that was forcibly put in Away status by ACD for not answering an item.

SMS Login Details

See the time of day associated with both login and logout behavior of agents with regards to handling SMS. The report can be grouped by date or agent and shows the time of day associated with a variety of login/logout behavior. The report shows the client the agent used and what action they took, whether that was logging in as Available or Away, or logging out.

Reported data:

Operator
Name of the agent.
Time
The time of changing the agent's status.
Client
The client where the agent's status was changed.
Action
The action that was taken to change the agent's status.

Ticket Login Reports

Fastpath: report.boldchat.com > New Report > Login

Ticket Login Summary

See the amount of time that your operators spent logged in BoldChat with regards to handling tickets. For a given date range, this report shows the number of hours and minutes each operator was logged in as either available or away. A breakdown by BoldChat client application is also included.

Reported data:

Operator
Name of the operator.
Ticket Available - Total
The total time the operator spent in available status.
Ticket Available - .NET
The total time the operator spent in available status in the Desktop Client.
Ticket Available - Web
The total time the operator spent in available status in Agent Workspace.
Ticket Available - Mobile
The total time the operator spent in available status in the iPhone app or using the web client on a mobile device.
Ticket Away - Total
The total time the operator spent in Away status.
Ticket Away - .NET
The total time the operator spent in Away status in the Desktop Client.
Ticket Away - Web
The total time the operator spent in Away status in Agent Workspace.
Ticket Away - Mobile
The total time the operator spent in Away status in the iPhone app or using the web client on a mobile device.
% Forced
Percentage of total Away time that was forcibly put in Away status by ACD for not answering an item.

Ticket Login Details

See the time of day associated with both login and logout behavior of operators with regards to handling tickets. The report can be grouped by date or operator and shows the time of day associated with a variety of login/logout behavior. The report shows the client the operator used and what action they took, whether that was logging in as available or away, or logging out.

Reported data:

Operator
Name of the operator.
Time
The time of changing the operator's status.
Client
The client where the operator's status was changed.
Action
The action that was taken to change the operator's status.

Twitter Login Reports

Fastpath: report.boldchat.com > New Report > Login

Twitter Login Summary

See the amount of time that your operators spent logged in BoldChat with regards to handling tweets. For a given date range, this report shows the number of hours and minutes each operator was logged in as either available or away. A breakdown by BoldChat client application is also included.

Reported data:

Operator
Name of the operator.
Twitter Available - Total
The total time the operator spent in available status.
Twitter Available - .NET
The total time the operator spent in available status in the Desktop Client.
Twitter Available - Web
The total time the operator spent in available status in Agent Workspace.
Twitter Available - Mobile
The total time the operator spent in available status in the iPhone app or using the web client on a mobile device.
Twitter Away - Total
The total time the operator spent in Away status.
Twitter Away - .NET
The total time the operator spent in Away status in the Desktop Client.
Twitter Away - Web
The total time the operator spent in Away status in Agent Workspace.
Twitter Away - Mobile
The total time the operator spent in Away status in the iPhone app or using the web client on a mobile device.
% Forced
Percentage of total Away time that was forcibly put in Away status by ACD for not answering an item.

Twitter Login Details

See the time of day associated with both login and logout behavior of operators with regards to handling tweets. The report can be grouped by date or operator and shows the time of day associated with a variety of login/logout behavior. The report shows the client the operator used and what action they took, whether that was logging in as available or away, or logging out.

Reported data:

Operator
Name of the operator.
Time
The time of changing the operator's status.
Client
The client where the operator's status was changed.
Action
The action that was taken to change the operator's status.

Chat Summary report

This report includes a breakdown of all button clicks (reactive and proactive) and their associated disposition.

Fastpath: report.boldchat.com > New Report > Chat > Chat Summary
Note: You can download chat transcripts with the Digital DX API as described in the Digital DX Developer Center.

Reported data:

Total Clicks
All clicks of the chat button plus all accepted invitations.
Unavailable
All chats already in created status where chat was unavailable because of agent availability, hours of operation, or queue size limits. For information on chat statuses, see What is chat lifecycle?
Blocked
All clicks on chat buttons by those customers who have been blocked. See How to block customers during chat in the Agent Workspace.
Abandoned
All chats in created status that were not started, blocked, or unavailable (as described above). Most commonly, these are customers who were shown the pre-chat survey but failed to complete it.
Unanswered Chats
Chats that were started but were never answered. This happens either because the customer closed the chat window while waiting for an agent, or because the chat reached the Unanswered by agent timeout limit. You can set this timeout on the General tab of your chat window configuration. See How to set up timeout for unanswered chats.
Answered Chats
All chats that a live agent accepted and were moved to answered status.
AMC
Average Message Count for answered chats.
Unanswered Time
Time in queue for unanswered chats. Calculated as "chat ended" time minus "chat started" time for unanswered chats.
ASA
Average Speed to Answer for answered chats. Calculates the average time from chat started to answered by a live agent.
ACT
Average Chat Time for answered chats. Calculates the average time from the first agent answering a chat until it ends. ACT is measured for the final agent only.

If you need to look more closely at chat activity, use the Agent Activity report.

You can group and filter the report several ways in order to see the data from different perspectives.

When grouping by agent, note the following (for chats answered by multiple agents):

  • <None> in the Agent column represents chats that have not been assigned to an agent. This generally occurs if either agents were unavailable or the chat was abandoned and was never assigned to an agent.
  • All actions are reported as if executed by the final agent who answered the chat
  • The Answered value represents the number of chats for which an agent was the final assigned agent
  • The Answered Time of the first live agent handling the chat is counted toward the ASA calculation of the final agent who handled the chat

Department filters:

  • Department (operator membership) - Shows chats where the assigned agent or operator is a member of the selected department. For agents who are members of multiple departments, this also includes chats that were not assigned to the selected department, but to another department of the agent.
  • Department (initial assignment) -Shows chats where the first assignment was the selected department
  • Department (final assignment) - Shows chats where the last assignment was the selected department
  • Department (any assignment) - Show chats where the chat assignment history has assignments to the selected department
    • The Department (Any assignment) filter does not recognize chats that are assigned to a department but not to a specific agent. This may happen under certain circumstances:
      • When ACD is off and a chat is assigned to a department but not to an agent.
      • When ACD is on and a chat is assigned to an offline department but not to an agent. (Assignment to an offline department can happen manually, due to a rule, or when assignment is made to a department with a queue.) An offline department is where ACD cannot assign chats to agents because there are no agents currently available (they are away, their concurrency limit is reached, or the chat was started outside business hours).

What are the common details in reports?

Unavailable - no operator was available to take the chat

Blocked - user was blocked so could not start chat

Abandoned - user did not complete pre-chat survey

Unanswered - user left before receiving an answer

Answered - if None then it means an agent answered the customer, but then was transferred to another department, waited in a queue, and dropped before being assigned to an agent.

None in the Operator column may mean the following:

  • Chat ended with no agent assigned. Digital DX Agent reports look at the Ended state of a chat, so if it ended without assignment then it is registered under None.
  • Agent was deleted in the meantime, which is why we recommend disabling rather than deleting users.

Set agent permissions: Create or edit a permission group

Use permission groups to set the features and folders your agents can access. An agent's permissions depend on the rights and restrictions set for the group to which they are assigned.

  1. Create or edit a permission group, as follows:
    1. In the Web Admin Center, go to Organization > Permission groups. The Permission Group Management page is displayed.
    2. Select an existing permission group or click Create New.

    Result: The New/Edit Permission Group page is displayed.

  2. On the Account tab you can set the following permissions:
    Option Description
    Access agent list in monitor view Allow group members to view agents' workload in Monitor View.
    Access Audit Log Allow group members to view audit logs of the Admin Center on the General > Audit Log page. See View changes in the Admin Center.
    Access Automatic Chat Distribution Settings Allow group members to change settings on the Channel > Chat > Automatic Distribution page in the Admin Center. See How to automatically activate chats (Automatic Chat Distribution).
    Access Automatic Email Distribution Settings Allow group members to access the Channel > Email > Automatic Distribution page in the Admin Center. See Set up automatic distribution for email.
    Access Automatic Messaging Distribution Settings Allow group members to change settings on the Channel > Messaging > Automatic Distribution page in the Admin Center. See Set up automatic distribution for messaging.
    Access Data Retention Settings Allow group members to change settings on the General > Data Retention and General > Data Protection pages in the Web Admin Center. See Data Protection.
    Access Login Control Settings Allow group members to change settings on the General > Login Control page in the Web Admin Center.
    Access Mobile Dashboard Allow group members to log in to the Mobile Dashboard.
    Change Another Agent's Status Allow group members to change the availability of other agents in the Agent Workspace.
    Change Website Data Validation Settings Allow group members to change the website data validation settings when setting up a website on the Organization > Websites page in the Admin Center.
    Edit Agent Workspace Settings Allow group members to change the settings related to the functionality of the Agent Workspace.
    General Account and Restrictions Settings Allow group members to change the following account settings in the Web Admin Center:
    • Invitation settings
    • PIN invitation settings
    • Regional settings
    • General account restrictions
    • Singe Sign On settings
    • API key and trigger settings
    • Geofluent auto-translation settings
    Generate Chat Button HTML Allow group members to generate chat button HTML when setting up a static or floating chat button on the Channels > Chat > Chat Buttons page. See Generate chat button HTML.
    Generate Conversion Tracking HTML Allow group members to generate conversion tracking HTML code when setting up conversion codes on the Customers > Conversion Codes page. See Set up conversion tracking.
    Generate Customer Monitor HTML Allow group members to generate Customer Monitoring HTML code when setting up a static or floating chat button on the Channels > Chat > Chat Buttons page.
    Have Plugins Enabled Not in use.
    Modify Folders Allow group members to modify folders for chat, email, messaging, and Canned Messages.
    Replace Canned Messages Allow group members to replace Canned Messages in the desktop client.
    Setup Rules Engines Allow group members to set up rules for managing incoming chats or visits on the following pages:
    • Channels > Chat > Routing Rules
    • Channels > Messaging > Routing Rules
    • Channels > Email > Routing Rules
    See Manage incoming chats according to rules (Chat Rules Engine).
    Use Email Signatures Setup Allow group members to define email signatures when setting up an email account on the Channels > Email > Email Account page. To add a signature, select Outgoing email footer on the Format and content tab. See Set up an email account.
    Use Personal Canned Messages Allow group members to change settings on the Setup > My Canned Messages Setup page in the Digital DX Desktop Client.
    View Assignment History Allow group members to view the assignment history of work items both in their workspace and in Monitor View. See How to find customer and assignment history.
    View Dashboard Allow group members to log in to the Dashboard. See Monitoring your Organization (Dashboard).
    View Workspace Allow group members to log in to the Agent Workspace.
    View/Undelete from Recycle Bin Allow group members to manage the recycle bin by clicking View list of deleted items where available on Web Admin Center pages. See Data Retention Options.

    Enterprise and Premier subscribers may see additional permissions.

  3. On the Actions tab, set permissions controlling group members' use of specific features within the following major feature sets:
    • ActiveAssists
    • Chats
    • Contacts
    • Customers
    • Emails
    • Messaging
    • Remote Access
    • Reports
  4. On the Setup tab, set permissions controlling group members' ability to set up entities in the following categories:
    • ActiveAssist (cobrowse bookmarks)
    • APIs (API settings, integration API triggers)
    • Chats (chat buttons, Canned Messages, categories, custom fields, statuses, chat windows, floating chat buttons)
    • Contacts (categories, custom fields, statuses)
    • Customers (conversion codes)
    • Emails (categories, custom fields, statuses, accounts, email redirects)
    • General (agent statuses, agents, departments, integrations, knowledge bases, permission groups, salesforce connectors, spell checkers, websites)
    • Invitations (auto-invite rulesets, custom chat invitations)
    • Messaging (Canned Messages, categories, custom fields, SMS accounts, statuses)
    • Tickets (categories, custom fields, statuses)
    • Twitter (categories, custom fields, statuses, accounts)

    Enterprise and Premier subscribers may see additional permissions.

  5. On the Folders tab, set permissions controlling group members' ability to manage folders for the following:
    • ActiveAssists
    • Chats
    • Contacts
    • Customers
    • Emails
    • Messaging
    • Reports
    • Tickets
    • Twitter

    Enterprise and Premier subscribers may see additional permissions.

  6. On the Departments tab, control group members' ability to see operators and departments outside of their own.
    • Not Visible. Members can neither see nor transfer items to the department and its operators.
    • Department Visible. Members can see and transfer items to the department, but not its operators.
    • Operators Visible. Members can see and transfer items to the department and its operators.
  7. To make the permission group default for all subsequently created agents, click Set as default on the Account settings tab.
  8. Save your changes.
Remember: To assign an agent to permission groups, go to Organization > Agents > Agent Information.

What are best practices for using permission groups?

Digital DX offers two out-of-the-box permission groups. Our best practice recommendation is to review, and edit or add additional permission groups. Permission groups should be customized based on an organization's needs to allow different groups to setup what each user is allowed to do in Bold360 Agent. These can apply to agents or departments within an organization.

With as flexible as our permission settings are, the best approach is to think of different personas (agents, admins, supervisors, reporting analysts, content managers, and so on) and creating permissions that suit this persona. For example, you wouldn't want to give an agent access to setup and you wouldn't want reporting teams to be able to set themselves as available in the queues.

Our out-of-the-box permission groups (Administrator and Operator) are simply starting places, and we recommend reviewing and customizing them to fit your organization's needs. Create permission groups to prevent cherry picking of chats, emails, and so on by limiting visibility into the queue and specific folders, allow remote control/co-browse, create different groups with different abilities for different positions (agents, supervisors, team leads, managers, admins, developers), prevent transferring work items to individuals and only allow to do so at department level.

Operator Reports

View reports on your agents' performance.

Fastpath: report.boldchat.com > New Report > Chat > Operator Reports

Survey report

Get an overview of how satisfied chatters are with the service your agents are providing. Provides an agent by agent view of performance on a variety of key indicators. For a total number of answered chats, the report shows the average speed of answer, average length of those chats, and the number/percent of completed after chat surveys. For completed surveys, the average scores for Responsiveness, Professionalism, Knowledge, and Overall Rating are presented. Reports cannot display customer feedback and comments.

All actions are reported as if executed by the final agent who answered the chat.

Reported data:

Operator
The name of the agent.
Answered
The number chats the agent answered.
ASA
Average Speed to Answer for answered chats. Calculates time from when the chat started to the time it was answered by an agent.
ACT
Average Chat Time for answered chats. Time from answering a chat until it ends. The time between the first agent answering the chat and the final agent assigned to the chat when it ends, adds up to the ACT calculation for the final agent. It represents the average length of all chats for a given entity (Date, Agent, Country, etc.) measured from time of assignment to end of chat.
Surveys
The number of post-chat surveys that customers at least partially completed.
Survey %
The ratio of submitted post-chat surveys to all chats in percentage.
Response
Customer's evaluation of the agent's responses.
Professionalism
Customer's evaluation of the agent's professionalism.
Knowledge
Customer's evaluation of the agent's knowledge.
Overall
Customer's overall evaluation of the agent.

Survey NPS report

This report provides an agent by agent view of performance on the after-chat survey. For completed surveys, the NPS scores are presented. The Net Promoter Score or NPS? is based on the fundamental perspective that every company's customers can be divided into three categories: Promoters, Passives and Detractors. This report can be filtered allowing different views of data.

All actions are reported as if executed by the final agent who answered the chat. NPS values are for those agents who handled chats last.

Report availability: Web only.

Reported data:

Operator
The name of the agent.
Answered
The number chats the agent answered.
Surveys
The number of post-chat surveys customers submitted.
%Detractors
The percentage of detractors who gave an NPS score of 0-6.
%Passives
The percentage of passive customers who gave an NPS score of 7 or 8.
%Promoters
The percentage of promoters who gave an NPS score of 9 or 10.
NPS
The NPS score of the agent based on customer evaluation, which is the displayed in the 0 - 10 report columns.

Activity report

Get an overview of the chat volume handled by your agents. For a total number of chats offered, see the number and percent that were answered vs. missed. A missed chat occurs either because the agent did not answer the chat before exceeding a wait-time threshold or because the customer abandoned the chat. The report also shows the average speed of answer, average duration of answered chats, the average message count, and the average amount of time it took the agent to respond after the customer submitted a message (average response time). The report can be grouped and filtered in several ways.

Note: The value of Chats Offered increases each time a chat is assigned. A single chat can be assigned multiple times; the value of Chats Offered is not necessarily the same as the actual number of chats.

Report availability: Enterprise, Premier

Reported data:

Chats Offered
All chats offered to the agent.
Answered
The number of chats the agent answered.
Answered %
The percentage of chats that the agent answered.
Missed
The number of chats the agent did not answer.
Missed %
The percentage of chats that the agent did not answer.
Reassigned Chats
The number of chats that were transferred to other agents without the current agent answering them.
Reassigned %
The percentage of reassigned chats.
Abandoned Chats
The number of chats that ended without the agent answering them.
Abandoned %
Percentage of abandoned chats.
AASA
Assignment Average Speed to Answer for answered chats. Calculates time from when the agent received an assignment to the time the assignment was answered. AASA includes chats that either Automatic Distribution assigned to the agent or when the chat was transferred from another agent. AASA excludes assignments that the agent manually took from queue. See How to manually start chatting with the next customer in queue in the Agent Workspace.
ACT
Average Chat Time for answered chats. Time from answering a chat until it ends. The time between the first agent answering the chat and the final agent assigned to the chat when it ends, adds up to the ACT calculation for the final agent. It represents the average length of all chats for a given entity (Date, Agent, Country, etc.) measured from time of assignment to end of chat.
AMC
Average message count for answered chats.
ART
Average time for agent to respond to a customer's message.

Productivity report

Get an overview of how busy your chat agents are. Provides an agent by agent overview of their time spent chatting. For a given date range, the report shows how many hours and minutes the agent was available for chats, how much time they spent engaged in chats, how much time they spent idle, and a utilization calculation. The report also provides the amount of time spent handling concurrent chats, the agent's average response time, the number of chats they took per hour, and the maximum and average number of simultaneous chats.

Report availability: Enterprise, Premier

Reported data:

Operator
Name of the agent.
Available
Total time logged in as Available.
Away
Total time logged in as Away.
Available (Chat Time)
Total time in at least one chat while logged in as Available.
Away (Chat Time)
Total time in at least one chat while logged in as Away.
Available (Idle Time)
Total time not in chat while logged in as Available.
Away (Idle Time)
Total time not in chat while logged in as Away.
Available (Utilization)
Percentage of time in chat while logged in as Available.
Away (Utilization)
Percentage of time in chat while logged in as Away.
Working
Percentage of time either logged in as Available or logged in as Away but being in chat.
Multi-Chat
Time with more than one simultaneous chat while available.
ART
Average time for agent to respond to a customer's message.
Chats/hr
Average number of chats answered per hour.
Max Simult
Greatest number of concurrent chats for the given period.
Avg Simult
Greatest number of concurrent chats for the given period.

Custom Survey report

Provides an agent by agent view of performance on the default post-chat and custom pre/post-chat survey fields. For completed surveys, the raw scores for each custom field are presented and open ended comments are also included.

Custom Wrap-Up report

Report availability: Web only

Provides an overview of data collected on custom wrap-up forms. Results are grouped by agents.

How to schedule reports

After running a report, you can schedule it to run automatically on a daily, weekly, or monthly basis.

  1. Log in at https://report.boldchat.com.
  2. Click New report to select a report that you want to schedule.
  3. Click Run report.
  4. On the Report results page, click the cogwheel icon and then click Schedule.

  5. Fill in the details of the report schedule.

    You have the following options:

    • Report Title - By default, the name of the report that you have run. This will appear in your list of scheduled reports. You can rename it to find it easier later on.
    • To Email Address - The email address where the report will be sent.
    • From Email Address - Optionally, you can type an email address that will be displayed as the sender of the scheduled report. If you leave it blank, reports will be sent from reports@boldchat.com
    • Output - The format of the report: XLS, PDF, CSV, or HTLM.
    • Schedule - The frequency of receiving reports, which can be daily, weekly, or monthly.
    • On Days of Week - Only available when you schedule reports on a weekly basis.
    • On Month Days - Only available when you schedule reports on a monthly basis.
    • Period - The date range that report includes.
  6. Save your scheduled report.
You will receive reports to the defined email address in the selected output format.
Important: You can schedule 20 reports by default. Contact your Success Manager to increase this limit.

Where to find your scheduled reports?

It may take some time to experiment with the parameters of your scheduled reports that best suit your needs. If you want to update the settings of your scheduled reports, do the following:

  1. At the top of the page, go to the Scheduled tab.

    Your scheduled reports are listed in order of creation.

  2. Click the name of the report that you want to update.
  3. Save your change when you are done.

Can't find a report that someone else scheduled?

At the top of the page, click All to see all available scheduled reports, not just yours.

Where do I find scheduled reports in the BoldChat Desktop Client?

  1. Go to the Reports menu.
  2. At the top of the page, click Schedule.

    Result: Your scheduled reports are listed in a pop-up window.

You have the following options in the menu bar to manage your scheduled reports:

  • Schedule a report - Click New and select the report type that you want to schedule. You would set the report's parameters as described above.
  • Edit an existing report - Select a scheduled report and click Edit to change its settings.
  • Delete a report - Click Delete to remove a scheduled report.
  • Run a report - If you don't want to wait until a report is automatically sent, you can run it any time. To do so, select a report and click Run Now.

Chat Login reports

See the amount of time that your agents spent logged in to and out of Digital DX.

Fastpath: New Report > Login

Chat Login Summary report

See the amount of time that your agents spent logged in to Digital DX.

For a given date range, this report shows the number of hours and minutes each agent was logged in as either available or Away.

Reported data:

Operator
Name of the agent.
Chat Available - Total
The total time the agent spent in available status.
Chat Available - .NET
The total time the agent spent in available status in the Desktop Client.
Chat Available - Web
The total time the agent spent in available status in Agent Workspace.
Chat Available - Mobile
The total time the agent spent in available status in the iPhone app or using the web client on a mobile device.
Chat Away - Total
The total time the agent spent in Away status.
Chat Away - .NET
The total time the agent spent in Away status in the Desktop Client.
Chat Away - Web
The total time the agent spent in Away status in Agent Workspace.
Chat Away - Mobile
The total time the agent spent in Away status in the iPhone app or using the web client on a mobile device.
% Forced
Percentage of total Away time that was forcibly put in Away status by ACD for not answering an item.

Chat Login Details report

See the time of day associated with both login and logout behavior of agents. The report can be grouped by date or agent and shows the time of day associated with a variety of login/logout behavior. The report shows the client the agent used and what action they took: log in as Available or Away, log out.

Reported data:

Operator
Name of the agent.
Time
The time of changing the agent's status.
Client
The client where the agent's status was changed.
Action
The action that was taken to change the agent's status.

How to run Digital DX Agent reports

Use Digital DX reporting tools to analyze and interpret the underlying data associated with site engagements and facilitate the transformation of data into actionable information.

Note: For detailed information on reports, see the complete list of Digital DX reports in the navigation tree on the left.
  1. Click New Report in the top-right corner.
  2. Select a report from the list on the left.
  3. Select the date range of your report on the right.
  4. From the drop-down list next to the date picker, select how you want to group your report.
  5. Click Run Report.

What can you do after running reports?

View description of report columns

Once your report runs, you can see the category or column definitions at the bottom of the page under Result category definitions.

Export reports

You can export reports to .CSV, .XLS, or .PDF by clicking the gear icon in upper-right corner.

Create report templates

You can create report templates for later use. See How to create report templates.

Re-run reports

To change the filters and groupings of the report, click Re-Run. After updating your report settings, click Run Report.

View a quick snapshot
Click the Snapshot tab at the top of the page to view the 7 Day Snapshot. This report displays data from the last seven full days of Digital DX activity for folders the active user has permission to access.
View recent reports
The Reports tab at the top of the page displays a list of recently generated reports.
Schedule reports
Use the Schedule tab at the top of the page to set up reports that run according to a schedule and can be emailed automatically to appropriate addresses. See How to schedule reports.

What are the common details in reports?

Unavailable - no operator was available to take the chat

Blocked - user was blocked so could not start chat

Abandon - user did not complete pre-chat survey

Unanswered - user left before receiving an answer

Answered - if None then it means an agent answered the customer, but then was transferred to another department, waited in a queue, and dropped before being assigned to an agent.

None in the Operator column may mean the following:

  • Chat ended with no agent assigned. Digital DX Agent reports look at the Ended state of a chat, so if it ended without assignment then it is registered under None.
  • Agent was deleted in the meantime, which is why we recommend disabling rather than deleting users.

Messaging Apps Login reports

See the amount of time that your agents spent on handling messages over messaging apps.

Fastpath: report.boldchat.com > New Report > Login

Messaging Apps Login Summary

See the amount of time that your agents spent logged in Digital DX with regards to handling Messaging Apps. For a given date range, this report shows the number of hours and minutes each agent was logged in as either Available or Away.

Reported data:

Operator
Name of the agent.
Messaging Apps Available - Total
The total time the agent spent in available status.
Messaging Apps Available - .NET
The total time the agent spent in available status in the Digital DX Desktop Client.
Messaging Apps Available - Web
The total time the agent spent in available status in Agent Workspace.
Messaging Apps Available - Mobile
The total time the agent spent in available status in the iPhone app or using the web client on a mobile device.
Messaging Apps Away - Total
The total time the agent spent in Away status.
Messaging Apps Away - .NET
The total time the agent spent in Away status in the Digital DX Desktop Client.
Messaging Apps Away - Web
The total time the agent spent in Away status in Agent Workspace.
Messaging Apps Away - Mobile
The total time the agent spent in Away status in the iPhone app or using the web client on a mobile device.
% Forced
Percentage of total Away time that was forcibly put in Away status by ACD for not answering an item.

Messaging Apps Login Details

See the time of day associated with both login and logout behavior of agents with regards to handling Messaging Apps. The report can be grouped by date or agent and shows the time of day associated with a variety of login/logout behavior. The report shows the client the agent used and what action they took, whether that was logging in as Available or Away, or logging out.

Reported data:

Operator
Name of the agent.
Time
The time of changing the agent's status.
Client
The client where the agent's status was changed.
Action
The action that was taken to change the agent's status.

Customize a layered chat window

Adapt the look and feel of your chat windows to your design and locale.

Fastpath: In the Web Admin Center, go to Channels > Chat > Chat Windows > [New or existing window] > Customization.

You can customize the following interface elements:

  • Window texts, messages and labels
  • Colors
  • Logo and images
  • Layout and custom events

You can use key chaining to reuse values for related elements.

Layout overview


A layered window has the following variables of individual elements:

  1. General Text Color
  2. Header Font Color
  3. Header Background Color
  4. Operator Message - Message - Font Color
  5. Operator Message - Name - Font Color
  6. Operator Message - Time - Font Color
  7. Operator Message Background Color
  8. Customer Message - Message - Font Color
  9. Customer Message - Name - Font Color
  10. Customer Message - Time - Font Color
  11. Customer Message Background Color
  12. Button Font Color
  13. Link Font Color
  14. Required Font Color
  15. Message Input Font Color
  16. Message Input Background Color
  17. Button Background Color
  18. Message Input Container Background Color
  19. Content Background Color (R,G,B)

Overview of customization setting groups

The following table describes the key areas that you can customize for layered chat windows in Digital DX:

Main group - Key group Description
Layered - Basic > AutoAnswers Defines Auto Answers messages for your customer self-service. For more information, see Auto Answers: Customer self-service.
Layered - Basic > Colors Defines the color scheme of your layered chat window. For more information, see Colors (Layered - Basic).
Layered - Basic > Other Defines the default customer name, submit button caption and welcome message.

The default customer name is displayed when a pre-chat form is not available or the customer does not provide a name.

Layered - Basic > Window Defines the size and title of the chat window.
Layered - Chat page > Buttons Defines the button caption for ending the chat session.
Layered - Details > ACD Defines messages that the Automatic Distribution system displays to customers while they are waiting for an agent in queue.
Layered - Details > ActiveAssist Defines messages for the customer before and during co-browse sessions.
Layered - Details > Buttons Defines the button captions for closing the chat window, sending a message, submitting a form, as well as button captions related to video sessions.
Layered - Details > Chat Frame Defines captions, labels, and icons of the chat window.
Layered - Details > Chat Transcript Defines labels of the chat transcript dialog.
Layered - Details > Chat Window Defines system messages in the chat window.
Layered - Details > Colors Defines additional color schemes for your layered chat window. For more information, see Colors (Layered - Details).
Layered - Details > Includes Defines CSS styles for the chat window and for the page where the chat window is displayed.
Layered - Details > Miscellaneous Various labels and messages related to unavailable agents, video chats, auto-translated messages, and basic action buttons, such as Yes, No, OK, and Cancel.
Layered - Details > Post Chat Survey Defines button captions and labels on the post-chat form.
Layered - Details > Pre Chat Survey Defines button captions and labels on the pre-chat form.
Layered - Details > Remote Control Defines button captions, labels and messages when the customer is in a remote control session.
Layered - Details > Unavailable Email Defines system messages and labels for the email that customers can send when chat is not available.
Layered - Post chat > Buttons Defines the button caption for sending the post-chat form.
Layered - Pre-chat > Buttons Defines the button caption for starting the chat session from the pre-chat form.
Layered - Unavailable email > Buttons Defines the button caption for closing the chat window after the customer sends an email when chat is not available.

Window texts, messages, and labels

Window texts, messages and labels can be customized per language. See also Provide a chat window in multiple languages.

Colors (Layered - Basic)

Define the basic color scheme of layered windows.

Tip: As a general rule, variable names reflect the name of the corresponding key. For example, you can refer to the Header Font Color key with the header_font_color variable.
Key Variable and default value Description
Button Background Color button_background

Default: #01A5EE

The background color of buttons in the chat window, such as the Send and Start Chat buttons.
Content Background Color (R,G,B) content_background_color

Default: 35, 35, 35

The background color of the inner chat window, where customers see the messages.
Content Background Transparency background_transparency

Default: 0.65

The transparency of the inner chat window.
Customer Message - Message - Font Color visitor_message_font_color

Default: #000000

The color of the customer's message.
Customer Message - Name - Font Color visitor_message_sender_color

Default: #FFFFFF

The color of the customer's name.
Customer Message - Time - Font Color visitor_message_sent_color

Default: #FFFFFF

The color of the time stamp when the customer sent the message.
Customer Message Background Color visitor_background

Default: #3DC8F3

The background color of the customer message container.
General Text Color text_color

Default: white

The color of system messages and labels.
General Text Font text_font

Default: sans-serif

The font family of system messages and labels.
General Text Size text_size

Default: 1em

The font size of system messages and labels.
Header Background Color header_background_color

Default: #01A5EE

The background color of the chat window's header.
Header Font Color header_font_color

Default: #FFFFFF

The color of the label in the chat window's header. To change the label of the chat window, go to Layered - Basic > Window > Window Title.
Message Input Background Color message_input_background

Default: #FFFFFF

The background color of the input field, where customers type their messages.
Message Input Container Background Color message_input_container_background_color

Default: #232323

The border color of the message input field and the Send button at the bottom of the chat window.
Message Input Font Color message_input_font_color

Default: #000000

The color of customer messages as they type.
Operator Message - Message - Font Color operator_message_font_color

Default: #E7E7E7

The color of agent messages.
Operator Message - Name - Font Color operator_message_sender_color

Default: #B2B2B2

The color of the agent's name.
Operator Message - Time - Font Color operator_message_sent_color

Default: #3DC8F3

The color of the time stamp when the agent sent the message.
Operator Message Background Color operator_background

Default: #232323

The background color of the agent message container.

Colors (Layered - Details)

Key Variable and default value Description
ActiveAssist Activity Background Color aa_background

Default: ${form_background}

The background color of the message that describes the co-browse activity.
ActiveAssist Activity Font Color aa_color

Default: ${text_color}

The color of the message that describes the co-browse activity.
ActiveAssist Message - Message - Font Color aa_message_font_color

Default: ${operator_message_font_color}

The color of co-browse system messages.
ActiveAssist Message - Name - Font Color aa_message_sender_color

Default: ${operator_message_sender_color}

The color of the agent's name who started the co-browse session.
ActiveAssist Message - Time - Font Color aa_message_sent_color

Default: ${operator_message_sent_color}

The color of the time stamp when the agent started the co-browse activity.
ActiveAssist Message Background Color aa_message_background

Default: ${operator_background}

The background color of the co-browse message container.
Button Font Color button_font_color

Default: ${text_color}

The color of button labels.
Dialog Background Color dialog_background

Default: ${text_color}

The background color of dialogs, such as when the agent asks the customer for remote control permission.
Dialog Button Font Color dialog_button_font_color

Default: ${text_color}

The color of the button labels in chat window dialogs.
Dialog Cancel Button Background Color dialog_cancel_background

Default: ${form_background}

The background color of the Cancel button in dialogs.
Dialog Font Color dialog_font_color

Default: ${form_background}

The color of dialog texts.
Dialog OK Button Background Color

Optional: Customize Chat Windows

Note: This article is part of a Quick Start Guide to help you implement your Digital DX environment from scratch.

Every business has its own unique voice and brand identity, and Digital DX gives you the control and flexibility to customize your implementation to your unique business needs.

  1. Go to Channels > Chat > Chat Windows.
  2. Click on the name of your chat window to edit the chat window settings. Select from the following options:
    • General
    • Pre-chat form
    • Post-chat form
    • Message content
    • Agent wrap-up
    • Auto Answers
    • Customization

What is the relationship between Digital DX AI touchpoints and Digital DX chat windows?

Tip: For information about the differences between Digital DX Agent and Digital DX AI, see What is Digital DX AI?.

One Digital DX Agent account can only be integrated with one Digital DX AI account. A Digital DX AI account can escalate to more than one Digital DX Agent accounts, but it is not recommended to do so.

A Digital DX Agent account can have several chat windows, but one chat window can only be associated with one Digital DX AI Knowledge Base. A Digital DX chat window is similar to a Digital DX AI touchpoint configuration, which defines the behavior and appearance of a chat widget.

So while you can only associate one Digital DX Agent account with one Digital DX AI account, you can display the content of all your Digital DX AI Knowledge Bases by setting up multiple Digital DX chat windows.

Optional: Customize Chat Buttons

Note: This article is part of a Quick Start Guide to help you implement your Digital DX environment from scratch.

Every business has its own unique voice and brand identity, and Digital DX gives you the control and flexibility to customize your implementation to your unique business needs.

  1. Click Channels > Chat > Chat Buttons (Floating).
  2. Click on the name of your chat button.
  3. Go to the Settings > Display.
  4. You can select among predefined images in our Button Template library or provide URL links to your own custom button images.
  5. Scroll down to the Positioning section to select where your chat button is displayed on your web page and how it will animate when shown to the visitor.
  6. Save your changes.

Generate chat button HTML

The primary connection between Digital DX and your chat customers is a snippet of HTML code that you generate together with a chat button and insert to your site.

When choosing an HTML snippet for your site, you are asking yourself the following questions:

  • Which button or link are you showing to customers?
  • Are you collecting information about customers so you can analyze and react to visits even before they chat?
  • Are you tracking conversion events so you can relate specific chats to actual sales or other milestones?
  • Are you inviting customers to chat based on characteristics of their visit such as page visited, length of visit, and more.

Here's how to set up a Digital DX chat button HTML snippet to create a "gate" between customers and Digital DX. For this first test we'll create a Floating Chat button.

  1. In the Web Admin Center, choose the type of HTML code to generate:
    Option Description
    Floating Chat Button Select Channels > Chat > Chat Buttons (Floating) when you want to implement a floating chat button and/or monitor customers before chat and/or invite users to chat based on characteristics of their visit.
    Static Chat Button Select Channels > Chat > Chat Buttons (Static) when you want to implement a fixed-position chat button or link on your site.
    Conversion Tracking HTML Select Customers > Conversion Codes when you want to track conversion events so you can relate specific chats to actual sales or other milestones.

    What is the difference between static and floating chat buttons?

    A static chat button is a standard HTML button that is always displayed on your website as a static element. Whether it's a button or just a clickable string of text depends on how you configure your chat button definition.

    Floating buttons are animated by default and they slide into view when the customer moves the mouse over these buttons. When the button slides in, it covers part of your website, essentially creating an extra layer on top of your website content. You can define where the initial shrunk version of the button should appear on your website and how much it should shrunk before a customer moves the mouse over it.

  2. Apply settings to your HTML and associated entities.
    Tip: This article focuses on the "big picture" of how to implement an HTML snippet rather than the potentially long chain of settings that you can make to the various Digital DX entities that can be associated with an HTML snippet, such as Chat Button definitions, Chat Window definitions, Website definitions, Department definitions, Invitation Rulesets, Conversion Codes, and more.
  3. Click Generate HTML and then Copy to Clipboard.

    Result:

  4. Paste the code to your site.
    Important: Modifications to the generated HTML code may cause unexpected behavior and is not supported. For assistance or questions regarding the HTML snippet, contact Support.

    When pasting the HTML code to your site, consider the following in light of your actual site architecture:

    • To activate the code on all pages, paste the code into the footer include of your website before the closing <body> tag.
    • To activate the code per page (on a single page or multiple pages individually), paste the code into any page before the closing <body> tag.
    • If the chat button associated with your HTML uses a layered chat window, make sure your pages start with a <!DOCTYPE html> tag. Without this tag, some versions of Internet Explorer will use quirks mode and open the layered chat window in a pop-up.
    Tip: If you are sending the code snippet to a web developer via email, do not paste the code directly into an email message. Save the HTML code in a text file (Notepad, for example) and attach it to an email.

You must re-copy and re-insert your HTML code after making any of the following changes:

  • When you associate a new chat button (static or floating) with your HTML (rather than modifying an existing chat button)
  • When you associate a new website with your HTML (rather than modifying an existing website)
  • When you toggle Pass custom information about customer on/off
  • When you change the Conversion Code associated with your HTML
  • When you change the invitation rule set associated with your HTML

Show a different chat button image when agents are available/unavailable

To ensure that customers are properly informed about agent availability, you can choose to show a specific chat button image when at least one agent is available and another (or none) when no agents are available.

This feature is part of the chat button setup process for both floating and static buttons.

  1. Create or edit a fixed-position (static) or floating chat button, as follows:
    1. In the Web Admin Center, go to Channels > Chat > Chat Buttons (Static) / Chat Buttons (Floating).
    2. Select an existing chat button or click Create New.
  2. On the Settings tab in the Display section under When Unavailable, choose the expected behavior when no agents are available:
    • Show Unavailable Button: When no agents are available, the Unavailable chat button is displayed to customers as displayed on the Preview pane.
    • Show No Button: When no agents are available, no button is displayed to customers.
    • Show Available Button: When no agents are available, the Available chat button is displayed to customers as displayed on the Preview pane.
  3. You can also select a custom image for your available and unavailable agents that customers can see. To do so, select the Custom image source and enter the available and unavailable chat image URLs into the corresponding fields.
  4. Save your changes.

    Result: The settings are applied to the chat button.

Your chat button is ready to be set as a chat entry point by being associated with an HTML snippet and inserted to a site.

To activate a newly created chat button as a chat entry point on your website, you must paste the HTML code to your site. When editing an existing button, you do not need to paste the code since these settings are not in the HTML code itself, but rather on Digital DX servers.

Customize chat button appearance, position, animation

Change the look and behavior of your chat button.

  1. Create or edit a fixed-position (static) or floating chat button, as follows:
    1. In the Web Admin Center, go to Channels > Chat > Chat Buttons (Static) / Chat Buttons (Floating).
    2. Select an existing chat button or click Create New.
  2. To change your chat button's appearance, go to the Settings tab under Display.
  3. For floating chat buttons you have these additional options:
    • To control where your floating chat button displays on the customer's browser page, go to the Settings tab under Positioning
    • To control how your floating chat button is animated when shown to the customer, go to the Settings tab under Animation
  4. Save your changes.

    Result: The settings are applied to the chat button.

Your chat button is ready to be set as a chat entry point by being associated with an HTML snippet and inserted to a site.

To activate a newly created chat button as a chat entry point on your website, you must paste the HTML code to your site. When editing an existing button, you do not need to paste the code since these settings are not in the HTML code itself, but rather on Digital DX servers.

Set a chat button to be shown in specific countries

You can set chat buttons to be shown to customers in specific countries.

This feature is part of the chat button setup process for both floating and static buttons.

  1. Create or edit a fixed-position (static) or floating chat button, as follows:
    1. In the Web Admin Center, go to Channels > Chat > Chat Buttons (Static) / Chat Buttons (Floating).
    2. Select an existing chat button or click Create New.
  2. At the bottom of the Settings tab, under Locale, clear the checkbox for Show to all countries.
  3. Select countries to include or exclude.
  4. Save your changes.

    Result: The settings are applied to the chat button.

Your chat button is ready to be set as a chat entry point by being associated with an HTML snippet and inserted to a site.

To activate a newly created chat button as a chat entry point on your website, you must paste the HTML code to your site. When editing an existing button, you do not need to paste the code since these settings are not in the HTML code itself, but rather on Digital DX servers.

Associate chats (a chat button) with a department

Associate a chat button with a department to allow chats originating from the button to be tagged with department metadata, which can then be used to assign and organize chats.

This feature is part of the chat button setup process for both floating and static buttons.

  1. Create or edit a fixed-position (static) or floating chat button, as follows:
    1. In the Web Admin Center, go to Channels > Chat > Chat Buttons (Static) / Chat Buttons (Floating).
    2. Select an existing chat button or click Create New.
  2. On the Settings tab, choose the Department to associate with the chat button.
  3. Save your changes.

    Result: The settings are applied to the chat button.

Your chat button is ready to be set as a chat entry point by being associated with an HTML snippet and inserted to a site.

To activate a newly created chat button as a chat entry point on your website, you must paste the HTML code to your site. When editing an existing button, you do not need to paste the code since these settings are not in the HTML code itself, but rather on Digital DX servers.

Set the chat window seen by customers

To choose the actual interface seen by customers upon clicking a chat button, you must associate your chat button with a chat window.

This feature is part of the chat button setup process for both floating and static buttons.

  1. Create or edit a fixed-position (static) or floating chat button, as follows:
    1. In the Web Admin Center, go to Channels > Chat > Chat Buttons (Static) / Chat Buttons (Floating).
    2. Select an existing chat button or click Create New.
  2. On the Settings tab, choose the Chat Window to associate with the chat button.
  3. Save your changes.

    Result: The settings are applied to the chat button.

Your chat button is ready to be set as a chat entry point by being associated with an HTML snippet and inserted to a site.

To activate a newly created chat button as a chat entry point on your website, you must paste the HTML code to your site. When editing an existing button, you do not need to paste the code since these settings are not in the HTML code itself, but rather on Digital DX servers.

Where do I find a complete list of Digital DX reports

Use Digital DX's reporting tools to analyze and interpret the underlying data associated with site engagements and facilitate the transformation of data into actionable information.

Digital DX's reports are available at the reports site. Every time you run a report, the new report is displayed in the same window. Using Digital DX reports does not require any special license.

Chat Reports:

Report Documentation Description
Chat Summary here

The report includes a breakdown of all button clicks (reactive and proactive) and their associated disposition: clicks made when your agents were unavailable, clicks by blocked customers, the number of chats that ended before the agent could answer it (abandoned), chats that went unanswered, and answered chats. The report also includes useful operational data like average message count and average length of chats. You can group and filter the report several ways in order to see the data from different perspectives.

Chat Conversion Summary here

The report includes a breakdown of all conversion by the various groupings available for chats on the same visit, auto-invite chats and/or conversions done without interaction from an operator. For a given date, operator, or other grouping the report breaks down the conversions for your analysis.

ACD Summary here

You’ll see the total chats assigned automatically to agents (offered), the number of chats that ended before the agent could answer it (abandoned), and the number of chats taken away from an agent and given to another because the chatter’s wait time exceeded your threshold (reassigned.) The report also includes useful operational data like average message count, the average length of chats, and the maximum number of customers waiting in queue. The report can be grouped and filtered in several ways in order to see the data from different perspectives.

Missed Opportunities Summary here

The Missed Opportunities Summary report shows, for example, the number of customers who were not invited to chat because of unavailability and the number of chat button clicks occurring outside of established chat hours. The report can be grouped and filtered in several ways in order to see the data from different perspectives.

Canned Message Summary here

The Canned Message Summary provides - either across your entire account or on an operator by operator level - the most frequently used canned messages. Canned Message grooming is a live chat best practice and this report - especially when filtered by department or key date ranges - is an excellent starting place.

Salesforce Summary here

The Salesforce Summary shows how many Salesforce Contacts and/or Leads were pushed (manually or automatically) into Salesforce from a total number of answered chats. The report can be grouped and filtered in several ways in order to see the data from different perspectives.

Chat Assignment Report here

The Chat Assignment Report shows data for chats that were assigned by the ACD, re-assigned by the ACD, and/or transferred by another operator.

ActiveAssist Chat Summary here

The ActiveAssist Summary will show the number of chats that also included a co-browsing and/or remote control session. For a given date, operator, or other grouping, you’ll see the number of chats with sessions, the number of successfully connected sessions, and key data about the sessions and chats themselves.

Button Availability Report here

For example: When were your chat buttons available? Did they reach queue limits? When? For how long? Were there times when no operators were available? For a given period, you can view data for specific/all chat buttons in your account, or for specific/all types of status change.

Chat Keyword Summary here

For a given date range, this report contains the list of top search engine keywords used by customers to arrive on your website.

Service-Level Answered here The Chat Answered Service Level Analysis report shows, for a total number of answered chats, the number and percent that were answered within certain amounts of time. From less than 30 seconds to greater than 5 minutes, the report provides a breakdown across 11 linear time increments as well as overall averages. The report can be filtered in numerous ways and grouped by date, day of the week, hour, or operator.
Service-Level Unanswered here The Chat Unanswered Service Level Analysis report shows, for a total number of unanswered chats, the number and percent that were unanswered for certain amounts of time. From less than 30 seconds to greater than 5 minutes, the report provides a breakdown across 11 linear time increments as well as overall averages. The report can be filtered in numerous ways and grouped by date, day of the week, hour, or operator.
Service-Level Chat Duration here The Chat Duration Service Level Analysis report shows, for a total number of answered chats, the number and percent that lasted for certain amounts of time. From less than 30 seconds to greater than 5 minutes, the report provides a breakdown across 11 linear time increments as well as overall averages. The report can be filtered in numerous ways and grouped by date, day of the week, hour, or operator.
Service-Level Average Time in Queue here Average Time in Queue answers the following question: How many chats were in the unassigned queue for various amounts of time before being assigned? Each row represents a date, period, or operator. Each column is an amount of time. For a given date, period, or operator, each cell is the number of chats that waited the given amount of time before assignment.
Operator Survey Report here

The Operator Survey report provides an operator by operator view of performance on the after-chat survey. For a total number of answered chats, the report shows the average speed of answer, average length of those chats, and the number/percent of completed after chat surveys. For completed surveys, the average scores for Responsiveness, Professionalism, Knowledge, and Overall Rating are presented. The report can be filtered allowing different views of data.

Operator Survey NPS Report here

The NPS Operator Survey report provides an operator by operator view of performance on the after-chat survey. For completed surveys, the NPS scores are presented. The Net Promoter Score, or NPS®, is based on the fundamental perspective that every company’s customers can be divided into three categories: Promoters, Passives, and Detractors. The report can be filtered allowing different views of data.

Operator Activity Report here

The Operator Activity report provides, for a number of answered chats, the number and percent that were missed. A missed chat occurs either because the operator didn't answer the chat before exceeding a wait-time threshold or because the customer abandoned the chat. The report also shows the assignment's average speed of answer, average length of answered chats, the average message count, and the average amount of time it took the operator to respond after the customer submitted a message (average response time). The report can be grouped and filtered in several ways in order to see the data from different perspectives.

Operator Productivity Report here

The Operator Productivity report provides an operator by operator overview of their time spent chatting. For a given date range, the report shows how many hours and minutes the agent was available for chats, how much time they spent engaged in chats, how much time they spent idle, and a utilization calculation. The report also provides the amount of time spent handling concurrent chats, the agent's average response time, the number of chats they took per hour, and the maximum and average number of simultaneous chats.

Operator Custom Survey Report here

The Operator Custom Survey report provides an operator by operator view of performance on the default post-chat and custom pre/post-chat survey fields of the after-chat survey. For completed surveys, the raw scores for each custom field are presented and open ended comments are also included. The report can be filtered allowing different views of data.

Operator Custom Wrap-Up Report here

This report returns the data submitted by operators on the Custom Wrap-Up form. Data is shown per operator and can be filtered.

Auto Answers Chat Summary here

This report provides details about how many customers interacted with auto answers, read content, rated content and went to chat. Use the "Auto Answers Attempt" filter to break down this data for a particular attempt.

Auto Answers Canned Message Summary here

This report provides details about canned messages used by the Auto Answers feature. See which canned messages were presented to the customer, which ones were rated, and how well they were rated.

Auto Answers Customer Question Detail here

Review what types of questions website customers are entering into the Auto Answers feature. Analyze this information to update canned message content appropriately in order to maximize the effectiveness of Auto Answers.

Email Reports:

Report Documentation Description
Assignment Summary here

Analyze data such as email assignments accepted during the time period (per operator), average time to accept email assignments, average speed to answer email assignments, and more.

Assignment Status Summary here

This report provides the status of new email threads created in the date range specified. It includes details about the number of unanswered and answered emails for open as well as closed email threads.

Thread Status Summary here

This report provides the status of new email threads created in the date range specified. It includes details about the number of unanswered and answered emails for open as well as closed email threads.

Assignment Activity Summary here

This report returns activity for individual emails exchanged within a thread based on the operator assigned to the individual emails. Date reported includes average time to close, average speed to answer, average time to respond, number closed but answered, number closed but unanswered, and more.

Thread Activity Summary here

This report returns activity for individual emails exchanged within a thread based on the operator assigned to the thread. Date reported includes average time to close, average speed to answer, number closed but answered, number closed but unanswered, and more.

Email Thread Answer Performance Summary here This report returns the time it takes for email threads to be answered, based on the selected grouping. The report selects the email threads that were answered inside the date range you select. Time-to-answer is the interval between the first email's arrival to the Bold server and the initial response to that email by an operator.
Email Thread Close Time Performance Summary here This report returns the time it takes for email threads to be closed, based on the selected grouping. The report selects all the answered email threads that were closed inside the date range you select. Time-to-close is the interval between the time the thread was first answered to when it was closed.
Email Assignment Answer Performance Summary here

This report returns the time it takes for email assignments to be answered, based on the selected grouping. The report selects all the email assignments that were answered inside the date range you select. Time-to-answer is the interval between assignment to an operator and the operator's response.

Email Assignment Close Time Performance Summary here

This report returns the time it takes for email assignments to be closed, based on the selected grouping. The report selects all the answered email assignments that were closed inside the date range you select. Time-to-close is the interval between the time the email was first assigned to when it was reassigned or closed.

Email Time To Respond Performance Summary here This report returns the time it takes for an email to be responded to, based on the selected grouping.
Email Productivity - Accepted here

See the number of accepted email threads by the given grouping for a specified date range. An email is considered accepted when an operator accepts or responds to an assigned email thread.

Email Productivity - Answered here

See the number of answered email threads by the given grouping for a specified date range. An email is considered answered when an operator is the first to respond to an email thread.

Email Productivity - Assigned here

See the number of assigned email threads by the given grouping for a specified date range. An email thread is considered assigned on each new assignment or re-assignment.

Email Productivity - Closed (Answered) here

See the number of email threads closed with an answer by the given grouping for a specified date range. An email thread is considered closed (answered) when an operator closes an email thread with at least one response email.

Email Productivity - Closed (Unanswered) here

See the number of email threads closed without an answer by the given grouping for a specified date range. An email thread is considered closed (unanswered) when an operator closes an email thread with no response email.

Email Productivity - Received here

See the number of individual emails received by the given grouping for a specified date range.

Email Productivity - Sent here

See the number of individual emails sent by the given grouping for a specified date range. Sent emails are independent of email threads.

Email Productivity Summary here

See the average of several key email metrics for a specified date range.

Email Productivity - Time To Respond here

See the response time to received emails for a specified date range. Only received emails with a corresponding reply email will be counted in this calculation.

Login Reports:

Report Documentation Description
Multi-Service Productivity here

The Multi-Service Productivity report provides an operator by operator overview of their time while assigned different service items. For a given date range, the report shows how many hours and minutes the agent was available, how much time they were assigned work items, how much time they spent idle, and a utilization calculation. The report also provides the amount of time spent handling concurrent assignments, the number of assignments they took per hour, and the maximum and average number of assignments. All this is broken out as well for each department assigned items for an operator. This is then rolled up into aggregate utilizations for each department an operator is a member of, as well as across all departments on the account.

Peak Concurrent Login Summary here

In a given time range, grouped by day, the Peak Concurrent Login report returns the number of logged in operators and time of day when the highest number of operators were logged in at once.

Chat Login Summary here

The Chat Login Summary can be grouped only by operator and shows how much time (in hours and minutes) for a given date range, the operator was logged in as available and away. A breakdown by client application type is also included.

Chat Login Details here

The Chat Login Detail can be grouped by date or operator and shows the time of day associated with a variety of login/logout behavior. The report shows the client the operator used and what action they took, whether that be logging in as available or away, or logging out.

Email Login Summary here

The Email Login Summary can be grouped only by operator and shows how much time (in hours and minutes) for a given date range, the operator was logged in as available and away. A breakdown by client application type is also included.

Email Login Details here

The Email Login Detail can be grouped by date or operator and shows the time of day associated with a variety of login/logout behavior. The report shows the client the operator used and what action they took, whether that be logging in as available or away, or logging out.

Ticket Login Summary here

The Ticket Login Summary can be grouped only by operator and shows how much time (in hours and minutes) for a given date range, the operator was logged in as available and away. A breakdown by client application type is also included.

Ticket Login Details here

The Ticket Login Detail can be grouped by date or operator and shows the time of day associated with a variety of login/logout behavior. The report shows the client the operator used and what action they took, whether that be logging in as available or away, or logging out.

Twitter Login Summary here

The Twitter Login Summary can be grouped only by operator and shows how much time (in hours and minutes) for a given date range, the operator was logged in as available and away. A breakdown by client application type is also included.

Twitter Login Details here

The Twitter Login Detail can be grouped by date or operator and shows the time of day associated with a variety of login/logout behavior. The report shows the client the operator used and what action they took, whether that be logging in as available or away, or logging out.

SMS Login Summary here

The SMS Login Summary can be grouped only by operator and shows how much time (in hours and minutes) for a given date range, the operator was logged in as available and away. A breakdown by client application type is also included.

SMS Login Details here

The SMS Login Detail can be grouped by date or operator and shows the time of day associated with a variety of login/logout behavior. The report shows the client the operator used and what action they took, whether that be logging in as available or away, or logging out.

FB Messenger Login Summary here

The Facebook Login Summary can be grouped only by operator and shows how much time (in hours and minutes) for a given date range, the operator was logged in as available and away. A breakdown by client application type is also included.

FB Messenger Login Details here

The Facebook Login Detail can be grouped by date or operator and shows the time of day associated with a variety of login/logout behavior. The report shows the client the operator used and what action they took, whether that be logging in as available or away, or logging out.

Messaging Apps Login Summary here

The Messaging Apps Login Summary can be grouped only by operator and shows how much time (in hours and minutes) for a given date range, the operator was logged in as available and away. A breakdown by client application type is also included.

Messaging Apps Login Details here

The Messaging Apps Login Detail can be grouped by date or operator and shows the time of day associated with a variety of login/logout behavior. The report shows the client the operator used and what action they took, whether that be logging in as available or away, or logging out.

SMS Reports:

Report Documentation Description
SMS Status Summary here

This report provides the status of new SMS conversations created in the date range specified. It includes details about the number of unanswered and answered texts for open as well as ended conversations.

SMS Assignment Status Summary here

This report provides the status of new SMS assignments assigned in the date range specified. It includes details about the number of unanswered and answered texts for open as well as ended assignments.

SMS Activity Summary here This report contains details such as the number of texts sent and received, average time to respond, number of answered, ended answered and ended unanswered texts along with average speed to answer and average time to end for answered.
SMS Assignment Activity Summary here

This report contains details such as the number of texts sent and received, average time to respond, number of answered, ended answered and ended unanswered texts along with average speed to answer and average time to end for answered.

SMS Answer Performance Summary here

For a specified date range, analyze the distribution of the time to answer SMS conversations and the performance within user defined time intervals.

SMS Assignment Answer Performance Summary here

For a specified date range, analyze the distribution of the time to answer SMS assignments and the performance within user defined time intervals.

SMS End Time Performance Summary here

For a specified date range, analyze the distribution of the time to close SMS conversations and the performance within user defined time intervals.

SMS Assignment End Time Performance Summary here

For a specified date range, analyze the distribution of the time to close SMS assignments and the performance within user defined time intervals.

Facebook Messenger Reports:

Report Documentation Description
FB Messenger Status Summary here

This report provides the status of new FB Messenger conversations created in the date range specified. It includes details about the number of unanswered and answered texts for open as well as ended conversations.

FB Messenger Assignment Status Summary here

This report provides the status of new FB Messenger assignments assigned in the date range specified. It includes details about the number of unanswered and answered texts for open as well as ended assignments.

FB Messenger Activity Summary here

This report contains details such as the number of texts sent and received, average time to respond, number of answered, ended answered and ended unanswered texts along with average speed to answer and average time to end for answered.

FB Messenger Assignment Activity Summary here

This report contains details such as the number of texts sent and received, average time to respond, number of answered, ended answered and ended unanswered texts along with average speed to answer and average time to end for answered.

FB Messenger Answer Performance Summary here

For a specified date range, analyze the distribution of the time to answer FB Messenger conversations and the performance within user defined time intervals.

FB Messenger Assignment Answer Performance Summary here

For a specified date range, analyze the distribution of the time to answer FB Messenger assignments and the performance within user defined time intervals.

FB Messenger End Time Performance Summary here

For a specified date range, analyze the distribution of the time to close FB Messenger conversations and the performance within user defined time intervals.

FB Messenger Assignment End Time Performance Summary here

For a specified date range, analyze the distribution of the time to end FB Messenger assignments and the performance within user defined time intervals.

Messaging Apps Reports:

Report Documentation Description
Messaging Apps Status Summary here

This report provides the status of new Messaging Apps conversations created in the date range specified. It includes details about the number of unanswered and answered texts for open as well as ended conversations.

Messaging Apps Assignment Status Summary here

This report provides the status of new Messaging Apps assignments assigned in the date range specified. It includes details about the number of unanswered and answered texts for open as well as ended assignments.

Messaging Apps Activity Summary here

This report contains details such as the number of texts sent and received, average time to respond, number of answered, ended answered and ended unanswered texts along with average speed to answer and average time to end for answered.

Messaging Apps Assignment Activity Summary here

This report contains details such as the number of texts sent and received, average time to respond, number of answered, ended answered and ended unanswered texts along with average speed to answer and average time to end for answered.

Messaging Apps Answer Performance Summary here

For a specified date range, analyze the distribution of the time to answer Messaging Apps conversations and the performance within user defined time intervals.

Messaging Apps Assignment Answer Performance Summary here

For a specified date range, analyze the distribution of the time to answer Messaging Apps assignments and the performance within user defined time intervals.

Messaging Apps End Time Performance Summary here

For a specified date range, analyze the distribution of the time to close SMS conversations and the performance within user defined time intervals.

Messaging Apps Assignment End Time Performance Summary here

For a specified date range, analyze the distribution of the time to close Messaging Apps assignments and the performance within user defined time intervals.

Visit Reports:

Report Documentation Description
Visit Summary here

The report shows the total number of customers, the number of new and repeat customers, the average time customers spent on site, the total and average number of customer page views, and the average time per page. The report also includes information about the performance of proactive invites including the total number of invitations sent, number declined and ignore, and the average acceptance rate including a 95% confidence interval. The report can be grouped and filtered in numerous ways to provide different perspectives on the data. A very useful grouping is by "custom invite" which will allow an analysis (again within a 95% confidence interval) on the best performing proactive invitations.

Invite Summary here

The Invite Summary report, grouped only by proactive invitation rule, shows the number of times the invitation was offered, accepted, declined and ignored. Percentages are included as well.

Visit Chat Interactions here

The Visit Chat Interactions report shows the visit data associated with visits which also had a chat interaction. The report provides the total number of chats (grouped in one of a variety of ways) and then the number of those chats associated with either a new or return visit. Also included are the average time the chat customers spent on site, the average and total number of page views they had, the number of the chats occurring from invitations, and the average chat message count and duration.

Visit Keyword Summary here

For a given date range, this report contains the list of top search engine keywords used by customers to arrive on your website.

Experiment Reports:

Report Documentation Description
Experiment Summary here

For chat buttons, see the number of customers to whom each button was presented and the number who accepted (clicked to chat). For invitations, see the number of customers invited and the number who accepted (clicked to chat). You can also compare conversion data for the items in your experiment in comparison to the control.

Experiment Detail here

For chat buttons, see the number of customers to whom each button was presented and the number who accepted (clicked to chat). For invitations, see the number of customers invited per test invitation and the number who accepted, declined, or ignored. You can also compare advanced conversion data for the items in your experiment.

Twitter Reports:

Report Documentation Description
Twitter Status Summary here

This report provides the status of new twitter threads created in the date range specified. It includes details about the number of unanswered and answered tweets for open as well as ended threads.

Twitter Activity Summary here

This report contains details such as the number of tweets sent and received, average time to respond, number of answered tweet threads, ended answered and ended unanswered tweet threads along with average speed to answer and average time to end for answered tweet threads.

Twitter Answer Performance Summary here

For a specified date range, analyze the distribution of the time to answer tweets and the performance within user defined time intervals.

Twitter End Time Performance Summary here

For a specified date range, analyze the distribution of the time to close tweet threads and the performance within user defined time intervals.

Ticket Report:

Report Documentation Description
Ticket Summary  

Includes details about the number of new and closed tickets along with the average time for which tickets were open (from created to closed).

Contact Report:

Report Documentation Description
Contact Summary here

The data can be grouped in a number of different ways including date, day of the week, hour, operator, country etc.

Basic Reports:

Report Documentation Description
Basic Summary here

For a given date range this report contains graphs for total chats, a summary containing the number of new customers vs return customers, number of invited vs customer initiated chats, most clicked chat button location, customer chat acceptance rate, location where invitations had the highest acceptance rate, chat engagement rate and a number of other useful metrics. Based on the data included in the report, automated logic suggests one or more tips so that you can improve the quantity and quality of chat interactions.

One of the easiest ways to help manage the deployment is to leverage scheduled reports. Reports can be scheduled one time and then emailed out automatically on a set frequency, even to individuals who are not set up with Digital DX.

When a customer wants to chat with a live agent, their interaction goes through a complex lifecycle. Here's the oversimplified version of this complexity.

1. Created > 2. Started > 3. Answered > 4. Ended > 5. Closed

Let's look at what happens in a simple scenario:

  1. The customer clicks a chat button on a website This is when a chat is in Created status.
  2. The customer fills in the pre-chat form and clicks "Start". This is when chat status changes to Started.
  3. Depending on whether you have Automatic Distribution enabled, the chat is assigned to an agent either automatically or manually. This is when chat status changes to Assigned.
  4. The agent answers the chat, and chat status changes to Answered.
  5. The customer or the agent ends the chat, and chat status changes to Ended.
  6. The agent fills in the wrap-up form and chat status changes to Closed.
  7. If there is no wrap-up form, the chat closes after the Auto-close interval set on the Agent Wrap-up page of the chat window setup.

What if you have a chatbot?

A chatbot does not significantly influence a chat's lifecycle.

  1. A chat begins with the customer clicking a chat button on a website. This is when the chat is in Created status.
  2. Chat status changes to Started after the first interaction with the chat window (customer starts typing), or if there is an auto-question when the widget opens.
    Important: Since the bot does not count as an agent who answers the customer, chat status never changes to Answered while chatting with the bot. Therefore, Answered time in the Agent Workspace will always display N/A.
  3. The customer at some point may decide to escalate the chat to a live agent. At this point, the customer may have to fill in a pre-chat form and the chat's Started time is updated. In other words, the chat is started again; this time with a live agent.
  4. From here on, the chat's lifecycle is the same: the chat is first Answered, then Ended, and finally Closed.

Optional: Set Up an Invitation

Note: This article is part of a Quick Start Guide to help you implement your Digital DX environment from scratch.

There are a few ways to invite visitors to chat. The following steps outline how to set up a rules-based invitation to a chat conversation.

  1. Create an Invitation, which is the actual interface the visitor sees when invited.
    1. Go to Customers > Custom Invitations and click Create New.
    2. Name the invitation (for example, Acme invite).
    3. Save your changes.

    Need more info? There's an article about customizing chat invitations in our Support Center.

  2. Create an Invitation Rule Set.
    1. Go to Customers > Invitation Rule Set and click Create New.
    2. Enter a Name that will help you identify the rule set.
    3. Select Enable to activate the rule set.
    4. Under the Rules section, click New Rule.
    5. Name the rule.

    6. Click Add Criteria and select an option from the drop-down list.
    7. Click Add Action and select Activate Custom Invite from the drop-down list.
    8. Search for and select the rule you just created.
    9. Save your changes to add your rule to the rule set.
  3. Associate the Rule Set with chat button and HTML snippet.
    1. Go to Channels > Chat > Chat Buttons (Floating) and click on the name of the chat button you created.
    2. On the HTML page, select the rule set you created from the Auto Invite Ruleset drop-down menu.

    3. Save your changes and click Generate HTML.
    4. Follow the instructions on how to test your chat button.

Need more info? There's a section about invitations and rules in our Support Center.

Create your first department

In Bold360, departments control how agents are grouped and how chats and other work items are distributed. Departments may also differ from the actual 'departments' within your business due to language or skill groups.

Note: This article is part of a Quick Start Guide to help you implement your Bold360 environment from scratch.

To see the below steps in action, view our tutorial:

Note: In simple deployments, you may only have one department and that?s okay. Setting up that department will help keep your deployment organized and set you up for success as your organization?s digital engagement strategy matures.
  1. In the Web Admin Center, go to Organization > Departments.
  2. On the Department Management tab, click Create New.

  3. Enter a Name for your Department.

    Customers can see this name when you have multiple departments and want customers to choose which department they want to be routed to. This requires a pre-chat form.

  4. Under Language, select the language that agents in this department speak.

  5. On the Agents tab, click on individual agent names to add agents to their appropriate department. To remove agents from the department, click on the agent name again to move them to the lower section.

  6. You can also set department-level business hours.

    See How to set department-level business hours.

  7. Save your changes.

Need more info? There?s a section about department management in our Support Center.

Define your website

Set up a Website label to track the origin of visits and manage other aspects of the deployment. This website corresponds to the site where you want to deploy the code for the chat button and window.

Website labels also allow you to deploy the platform across multiple domains, but still distinguish which site the visitor is on or is engaging from. Additionally, websites may be used for routing, assignment, and custom defined hours of operation; all of which are specific to the website label that you define and to the domain/website where you deploy the code snippet.
Note: This article is part of a Quick Start Guide to help you implement your Bold360 environment from scratch.

To see the below steps in action, view our tutorial:

  1. In the Web Admin Center, go to Organization > Websites.
  2. From the website management page, click on the existing website called My Website.

  3. Unless your organization offers 24/7 coverage, you should enable business hours to control the times, days, dates, and circumstances under which your chat buttons are shown to customers. To do so, select Enable business hours for chat.

  4. Select your Timezone.
  5. Set your Business Hours, which are periods of time (day/time combinations) that reflect your regular hours of operation.
    1. Select the start and end of business hours, expressed as From/To, when chat is available for customers.

      Outside of this time period, your chat buttons display as unavailable even when agents are available. For example, if business hours are set for 9:00 AM to 5:00 PM, the chat button associated with this website will become available at 9:00 AM (if agents are available) and will be disabled at 5:00 PM.

    2. Select the days to which the From/To setting is applied.
    3. To set unique hours for the weekend (or any day of the week), click Add business hours and set the days and time as described above.
    4. Under Exceptions by date, you can alter your Business Hours (opening hours) on specific dates. See How to set website-level business hours.
  6. Save your changes.

Additional Configuration - Automatic Distribution

Automatic Distribution automatically assigns chats to agents to maximize agent efficiency. Within Automatic Distribution settings, you can set concurrent chat limits, enable queues and more.

Note: This article is part of a Quick Start Guide to help you implement your Bold360 environment from scratch.

To see the below steps in action, view our tutorial:

  1. In the Web Admin Center, go to Channels > Chat > Automatic Distribution. Set up automatic distribution for chat by selecting Enable automatic distribution.
  2. Optional: You can enable a concurrent chat limit which will limit how many chats are assigned to an agent at a time. To do so, enable Concurrent Chat Limit and set this number in the corresponding box.
  3. If you have set a concurrent chat limit, you can route customers to a queue when all agents have hit their concurrent chat limit. Under Queue Length Limits, you can set a hard limit under Maximum in queue or you can set a dynamic limit depending on how many agents are online under Average per agent. If you do not want to enable a queue, you can set Maximum in queue to 0.
  4. You can change the assignment method under Agents Waiting for Assignment. By default, this is set to Least Busy. This is the approach most commonly taken by customers. However, you can choose from the following options:
    • Least Busy. Assign the next incoming chat to the agent who has the fewest active chats and has waited the longest. This naturally means that if you have multiple agents available with no chats, ACD will assign the next incoming chat to the agent who has been in Available status for the longest period of time. Choose this to balance the chat workload between agents.
    • Most Busy. Assign chats to your busiest agents. The next incoming chat is assigned to the agent who is handling the most chats until their limit is reached, and thereafter to the agent who has been idle for the shortest period of time. Choose this option if your agents must manage non-chat tasks along with their chat related work. Those who are chatting will stay busy chatting, while others can stay focused on non-chat tasks. To prevent overload on a single agent, make sure concurrent chat limits are set.
    • Round Robin. Rotate chat assignment among all available agents regardless of waiting time or number of active chats (until their concurrent limit is reached). Choose this option to balance the number of chats assigned per agent. Lower ranked agents will only be assigned a chat if all higher ranked agents have reached their limit.
  5. Save your changes.

Additional Configuration - Wrap-up Fields

When a chat ends, an agent can be prompted to provide ?wrap-up? information about the chat. This will label the chat session for reporting purposes.

You can create labels (wrap-up fields) that are used to categorize and organize chats. These can be particularly helpful to leverage if you decide to integrate with a CRM tool in the future.

Note: This article is part of a Quick Start Guide to help you implement your Bold360 environment from scratch.

To see the below steps in action, view our tutorial:

  1. In the Web Admin Center, go to Channels > Chat > Wrap-up Fields.
  2. On the left side of the page, choose the type of label to edit or create: categories and/or statuses.
  3. To edit an existing out-of-the-box item, click the item?s name. From here you can rename the item or delete it by clicking the bin icon.

  4. Click Create New to add additional categories or statuses. When doing so, name the category or status in the new field.
  5. Save your changes.

Route chats to your agents

If you have multiple departments, you should have some logic in place to route customer chats to the appropriate department. You can do so by using a pre-chat form or by setting up routing rules.

Note: This article is part of a Quick Start Guide to help you implement your Bold360 environment from scratch.

Via Pre-Chat Form

When you want the customer to choose with which department they want to be connected.

  1. Make sure your departments are named in a customer-facing manner.
  2. In the Web Admin Center, go to Channels > Chat > Chat Window.
  3. Click on My Chat Window and go to the Pre-Chat form tab.
  4. Check box for Department. This will add Department as a field in the pre-chat form. Customers can choose the department they want to speak with and will be routed accordingly.

Via Routing Rules

When you want to route customers to a particular department based on their initial question, language or other criteria.

  1. In the Web Admin Center, go to Channels > Chat > Routing Rules.
  2. Click Create New.
  3. On the Criteria tab, do the following:
    1. Create a Rule Name. This name should include the department name.
    2. Fill out the criteria that will determine when a chat should be routed to this department. For example, if Initial Question Contains help or support.
  4. Within Actions tab, select appropriate department from Department drop-down.

The audit log allows you to view who changed the settings of the Web Admin Center and when those changes were made. Changes made in the AI Console or Desktop Client are not included.

You must have Account settings > Access Audit Log permission to see the audit logs.
  1. In the Web Admin Center, go to General > Audit Log.
  2. At the top of the page click the date picker to select the period of time when you want to see the changes.

    Every event in the audit log shows the page where changes occurred. The most recent event is listed on top.

  3. Click an event to see its details on the information panel on the right.

    The information panel displays the status of settings before and after they were changed.

  4. To go to the page or setup item where changes occurred, click the name of the page at the top of the information panel.

Glossary of terms

ACD Summary report

The ACD Summary includes total chats assigned automatically to agents (offered), the number of chats that ended before the agent could answer it (abandoned), and the number of chats taken away from an agent and given to another because the customer's wait time exceeded your threshold (reassigned), chats that went unanswered and answered. The report also includes useful operational data like average message count, the average duration of chats, and the maximum number of customers waiting in queue and the maximum wait time for any chat. We recommend grouping this report by operator to see if agents are answering or missing chats when they are assigned. For more information, see ACD Summary report.

Digital DX

Refers to the entire Digital DX Suite. This term is also sometimes used to refer to the live agent functionality within the Digital DX Suite that supports live chat and messaging - that is, the Digital DX Agent functionality.

Web Admin Center

The portal at https://admin.bold360.com that administrators use to manage the live agent environment.

Agent Workspace

The portal at https://agent.bold360.com/ that live agents use to provide customer support and messaging.

AI Console

The portal that administrators and content editors use to work with the knowledge base and configure a chatbot. You must have a Digital DX AI subscription to access this portal. The location of this portal varies depending on your account name and is in the following format: <acount_name>.nanorep.co

Digital DX Suite

The umbrella term for the Digital DX line of products. For an overview of features provided by the individual offerings in the product line, see https://www.bold360.com/pricing.

Digital DX AI

Functionality in the Digital DX Suite that supports chatbots, knowledge base use, and AI-powered self-service. These features were previously provided by a product called "Nanorep"; that name may occur in some places, such as URLs and API names.

Digital DX Agent

This product option provides omni-channel engagement and support without the advantages of AI.

Service

This product option extends the functionality of Digital DX Agent by providing AI-powered chatbot and self-service. The knowledge base stores and serves content to provide a better experience for customers and agents.

  • Agents support customers using the Agent Workspace.
  • Admins manage the live agent environment using the Web Admin Center and manage the knowledge base and chatbots using the AI Console.

Advise

This product option provides AI-based internal support for customer-facing employees, who need quick access to content to help them solve customers' issues. Internal support is available through a Google Chrome widget and a Salesforce app. This product does not include chatbot support.

  • Agents and employees receive internal support directly using Google Chrome or Salesforce.
  • Admins set up the knowledge base using the AI Console.

Acquire

This product option proactively guides your website visitors through personalized shopping experiences. It provides extended integration with sales tools and focuses on helping customers with product discovery and conversion.

Desktop Client

An older version of Digital DX. Desktop Client users download a .NET-based Desktop Client to provide support for customers.

chat widget / chat window

An HTML window, where customers can chat with agents. The Digital DX Agent platform refers to it as "chat window", whereas the Digital DX AI platform refers to it as "chat widget".

escalation

The process of transferring control from a chatbot to a live agent or other support solution when the chatbot is unable to meet customer needs. Ideally, customers will receive the information they need through conversation or search in the Digital DX AI widget. If they do not, you can offer them one or more options using channeling policies to escalate their query. One escalation path is to a live chat.

knowledge base

A repository of answers for the AI to draw upon when responding to customers. This repository may contain information about your products, services, and more. "KB" is often used as an abbreviation for "knowledge base".

Monitor View

A view in the Agent Workspace where you can supervise agents' workload. See How to monitor the chats of your organization.

swimlane

Another name for a panel in the Agent Workspace. A panel may contain a work item (chat, email, message), customer information, canned messages, Smart Advisor, discussion, the transfer panel, or any other custom integration panel.

Advanced reporting features

You can fine-tune the result of your reports that best suit your needs.

How to group your reporting data

When you run a report, you get information on the performance of your whole organization. However, you may want to know how a specific agent or even a chat button performs. To do so, you can change the default grouping of your reports to visually align the generated data to your needs.

  1. Sign in at https://report.boldchat.com.
  2. Click New Report at the top of the page and select a report type on the left.

    To change the default grouping of your report data, click the grouping option on the right and change it to your needs.

  3. Click Advanced on the right.
  4. Click Add New Report Grouping and select a grouping option.

    Result:

    Note: You can add multiple grouping options.
  5. Click Run Report at the bottom of the page.

How to filter reports

When you run a report, you get information on the performance of your whole organization. However, you may want to know how a specific agent or even a chat button performs. To do so, you can filter your reports to see only the data that really matters.

Note: Currently, Messaging App reports do not support filtering based on Account.
  1. Sign in at https://report.boldchat.com.
  2. Click New Report at the top of the page and select a report type on the left.
  3. Click Advanced on the right.
  4. Click Add New Report Filter and select a filter.

    Result:

    Note: You can add multiple filters.
  5. Click All to select specific members of the filter group.

  6. Select the individual members of the filter.
  7. Click Run Report at the bottom of the page.

How to change the timezone of reports

  1. Click New Report at the top of the page and select a report type on the left.
  2. Click Advanced on the right.
  3. In the top-right, click the timezone selector and change it to your timezone.

  4. Click Run Report at the bottom of the page.

Yes. Bold360 is a one-stop-shop for omni-channel engagement including chat, email, message management, remote access, and co-browse. The Bold360 API provides an interface for communicating with an application and allows you to customize how Bold360 and BoldChat integrate with your applications.

The Bold360 API is a tool for retrieving information related to your Bold360 account and based on that information, recreate most of the functionality that Bold360 offers. Bold360 API calls are launched by triggers that contain the conditions of making an API call. When a user on your website clicks an element, such as a chat button, an API can be called to extend or modify that interaction.

For more information, see the Bold360 and BoldChat Developer Center.

How to integrate Bold360 Agent with Bold360 AI

Integrate Bold360 AI and Bold360 Agent to enable your customers to escalate to a live agent when necessary.

Before you start: You must have valid Bold360 AI and Bold360 Agent subscriptions. The integration must be set up in both the Bold360 Admin Center and Bold360 AI.

Set up the integration in Bold360 Agent

  1. Log in to admin.bold360.com and go to Integrations > Bold360 ai.
  2. Enter your Bold360 ai account name.

    If you don?t know your account name, go to your Bold360 AI account and check the website name. The account name is whatever comes before .nanorep.co in the full URL.

    Result: Upon filling out the Bold360 ai account name field, you?ll notice that the Bold360 ai host url field is populated automatically.

  3. Enter the Bold360 AI API key.

    See How to create an API key in Bold360 AI for more information.

  4. Choose Integrate.

Set up the integration in Bold360 AI

  1. Log in to Bold360 AI, and go to Channeling > Channeling Policy.
  2. Choose (Create channel).
  3. Name your channel.

    Example: For example, Bold360 chat.

  4. Define criteria for selecting your target audience.

    For a search widget, we recommend doing this for queries without an answer (Search Results = No results) or by label (Article Label = Chat).

    Note: You need to create and assign this label to the articles where chat should be available. You can find more detailed information about channeling criteria here.
  5. Select Chat for Channel type.
  6. Under Button action, choose Show chat form.
  7. Select Bold360 from the Select chat provider drop-down.
  8. Paste your Bold360 Agent API key into the API key field. If you don't know your Bold360 Agent API key, create a new one as follows:
    1. Log in to admin.bold360.com and go to Integrations > API Access Keys.
    2. Choose Create New.
    3. Name the API Key.

      Example: For example, Bold360 ai.

    4. For Website, select My Website.
    5. Select the Department where you want to direct your chats.

      You can leave this blank unless you want to create different policies for different chat departments. If that's the case, you will want to create your departments as outlined in the Quick start guide to set up Bold360. From there, you can follow these instructions to create multiple API keys and channeling policies (one for each department).

    6. For Chat Window, select My Chat Window.
    7. Choose Save.
    8. When the Access Key window pops up, select Copy to Clipboard to copy your API key.

      Result: Now you can go back to Bold360 AI and paste this key.

  9. Choose Save Settings to save your channeling policy.

What's next?

If you are new to Bold360 Agent, follow the instructions in the Quick start guide to set up Bold360 to set up your Bold360 Agent account.

Google Analytics Integration with Bold360 Layered Windows

Integrate Google Analytics with Layered Chat Windows, track visitor interactions as Analytics events and gain accurate insight into visitor behavior.

As dynamic elements on a website, Layered Chat Windows require a mechanism to cache tracking information and provide accurate results. This step-by-step guide describes a Local Storage implementation that allows data to persist when a chat session is interrupted.

Note: Interruptions usually happen in the following circumstances:
  • Visitor navigates to a new page under the same domain.
  • Connection dropout occurs.
  • Visitor browses multiple pages on the website simultaneously.
  • Visitor closes and re-opens or reloads a page.

The Local Storage technology is compatible with the following browsers:

  • Google Chrome recommended (Last 20 versions)
  • Mozilla Firefox on Windows (Last 10 versions)
  • Microsoft Edge
  • Microsoft Internet Explorer 9 and newer
  • Safari on macOS (Last two versions)
  • Opera (Last 10 versions)

See the WebStorage article on Wikipedia for details.

Note: For information about data residency, see the BoldChat Help Center. Bold360 and BoldChat data residency options are identical.

Prerequisites

All pages on your site must either include or reference the following code snippets:

Tip: Streamline code snippet delivery via Google Tag Manager.

Task One: Configure the Chat Frame Javascript Include

Add a Chat Frame Javascript Include to the Chat Window Definition deployed to your site. This code intercepts chat events and passes them to the chat window via the postMessage method.

  1. Go to Channels > Chat > Chat Windows > Customization tab.
  2. Under Appearance, select Layered - Details > Includes > Chat Frame Javascript Include.
  3. Add the following method to the Content field at the bottom:
    Note: This is the method how Layered Chat internal events are already communicated between the Chat Frame (hosted on livechat[-eu].boldchat.com) and the Chat Window (the container, hosted on the same website that the visitor is browsing). Using this method we are basically extending the existing Chat communications methods by adding a new key (gacomm) for these custom messages.
    try {
      function sendtxt(txt) {
        var message = JSON.stringify({
          gacomm: txt
        });
        parent.parent.postMessage(message, "*");
      }
      sendtxt(bcConfig.chatOptions.page);
      window.console && console.log("Sent Chat Window Page: " + bcConfig.chatOptions.page);
      if (bcConfig.chatOptions.page == "chat") {
        var _tEvents = {
            "new-message": "bc_newHistoryMessageCallback"
          },
          _tFunction = function(i, type, fName) {
            if ((i == "new-message") && (bc.$("#bc-status-prompt").prev().hasClass("bc-operator-message"))) {
              sendtxt("answered");
            }
          }
      }
      for (var i in _tEvents) {
        window[_tEvents[i]] = _tFunction.bind(window, i, "function", _tEvents[i]);
      }
    } catch (err) {
      window.console && console.error(err);
    }
  4. Save your changes.

Task Two: Configure the Chat Window Javascript Include

Add a Chat Window Javascript Include to the Chat Window Definition deployed to your site.

Note: It is recommended to encapsulate the code snippets in this section in a try/catch phrase to detect potential issues later on.
  1. Go to Channels > Chat > Chat Windows > Customization tab.
  2. Under Appearance, select Layered - Details > Includes > Chat Window Javascript Include.
  3. Open a try/catch and import inline the LS CACHE minified script.
    Note: The Chat Window Javascript Include code depends on the LS CACHE library to manage the expiration time of Local Storage entities. We strongly recommend that you include the following minified code on your website, instead of referencing the library:
    try {
    
    /**
    * lscache library
    * Copyright (c) 2011, Pamela Fox
    *
    * Licensed under the Apache License, Version 2.0 (the "License");
    * you may not use this file except in compliance with the License.
    * You may obtain a copy of the License at
    *
    * http://www.apache.org/licenses/LICENSE-2.0
    *
    * Unless required by applicable law or agreed to in writing, software
    * distributed under the License is distributed on an "AS IS" BASIS,
    * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    * See the License for the specific language governing permissions and
    * limitations under the License.
    **/
    
    !function(a,b){"function"==typeof define&&define.amd?define([],b):"undefined"!=typeof module&&module.exports?module.exports=b():a.lscache=b()}(this,function(){function a(){var a="__lscachetest__",c=a;if(void 0!==m)return m;try{g(a,c),h(a),m=!0}catch(d){m=b(d)?!0:!1}return m}function b(a){return a&&"QUOTA_EXCEEDED_ERR"===a.name||"NS_ERROR_DOM_QUOTA_REACHED"===a.name||"QuotaExceededError"===a.name?!0:!1}function c(){return void 0===n&&(n=null!=window.JSON),n}function d(a){return a+p}function e(){return Math.floor((new Date).getTime()/r)}function f(a){return localStorage.getItem(o+t+a)}function g(a,b){localStorage.removeItem(o+t+a),localStorage.setItem(o+t+a,b)}function h(a){localStorage.removeItem(o+t+a)}function i(a){for(var b=new RegExp("^"+o+t+"(.*)"),c=localStorage.length-1;c>=0;--c){var e=localStorage.key(c);e=e&&e.match(b),e=e&&e[1],e&&e.indexOf(p)<0&&a(e,d(e))}}function j(a){var b=d(a);h(a),h(b)}function k(a){var b=d(a),c=f(b);if(c){var g=parseInt(c,q);if(e()>=g)return h(a),h(b),!0}}function l(a,b){u&&"console"in window&&"function"==typeof window.console.warn&&(window.console.warn("lscache - "+a),b&&window.console.warn("lscache - The error was: "+b.message))}var m,n,o="lscache-",p="-cacheexpiration",q=10,r=6e4,s=Math.floor(864e13/r),t="",u=!1,v={set:function(k,m,n){if(a()){if("string"!=typeof m){if(!c())return;try{m=JSON.stringify(m)}catch(o){return}}try{g(k,m)}catch(o){if(!b(o))return void l("Could not add item with key '"+k+"'",o);var p,r=[];i(function(a,b){var c=f(b);c=c?parseInt(c,q):s,r.push({key:a,size:(f(a)||"").length,expiration:c})}),r.sort(function(a,b){return b.expiration-a.expiration});for(var t=(m||"").length;r.length&&t>0;)p=r.pop(),l("Cache is full, removing item with key '"+k+"'"),j(p.key),t-=p.size;try{g(k,m)}catch(o){return void l("Could not add item with key '"+k+"', perhaps it's too big?",o)}}n?g(d(k),(e()+n).toString(q)):h(d(k))}},get:function(b){if(!a())return null;if(k(b))return null;var d=f(b);if(!d||!c())return d;try{return JSON.parse(d)}catch(e){return d}},remove:function(b){a()&&j(b)},supported:function(){return a()},flush:function(){a()&&i(function(a){j(a)})},flushExpired:function(){a()&&i(function(a){k(a)})},setBucket:function(a){t=a},resetBucket:function(){t=""},enableWarnings:function(a){u=a}};return v});
  4. Define the events to be reported in Google Analytics.
    var ga_events = {
      	"prechat": 'PreChat Form Displayed',
      	"chat": "Chat Opened",
      	"answered": "Chat Answered",
      	"postchat": "Survey Displayed",
      	"email": "Email Form (Unavailable)",
      	"no-operators": "Unavailable Chat",
      	"chat-sent": "Survey Completed or Transcript",
      	"message-sent": "Unavailable Email Sent",
      	"final": "Chat Ended without Survey or Transcript"
    	}
  5. Validate messages for security reasons.

    The following code achieves the following:

    • Ensures messages come from the livechat[-eu].boldchat.com server
    • Parses messages
    • Checks localStorage for existing events to be de-duplicated and discarded, if necessary
    • Sends relevant events to Google Analytics

    Note how individual events are stored in the browser localStorage with a CID, a unique identifier for Chat windows that survives page re-loads, browser closing/reopening as well as navigation on different tabs under the same domain.

    The code also ensures that the user is able to start multiple simultaneous chats on different domains while events are accounted for separately and accurately.

    function listener(event) {
      if (event.origin !== "https://" + bcConfig.host) return;
      var pmessage = JSON.parse(event.data);
      if (pmessage.hasOwnProperty('gacomm')) {
        window.console && console.log("Received: " + event.data);
        var received = pmessage.gacomm + "---" + bcConfig.cid;
        var found = false;
        lscache.flushExpired();
        CIDs = lscache.get('CIDs');
        if (CIDs !== null) {
          var arrayLength = CIDs.length;
          for (var i = 0; i < arrayLength; i++) {
            if (CIDs[i] == received) {
              found = true;
              break;
            };
          };
        } else {
          CIDs = [];
        }
        if (!found) {
          CIDs.push(received);
          lscache.set('CIDs', CIDs, 60);
          window.console && console.log("Sending new event to GA: " + received);
          try {
            ga('send', 'event', {
              eventCategory: 'Live Chat',
              eventAction: ga_events[pmessage.gacomm],
              eventLabel: 'Chat Window'
            });
          } catch (err) {
            window.console && console.error("Google Analytics UA code not found on page");
          }
        }
      }
    }
    if (window.addEventListener) {
      addEventListener("message", listener, false)
    } else {
      attachEvent("onmessage", listener)
    }
  6. Close the try/catch:
    } catch (err) {
      window.console && console.error(err);
    }

Task Three: Video Chat Events (Optional)

Track video chat events by updating your Chat Frame and Chat Window Javascript Includes.

Note: The video chat feature works over the HTTPS exclusively. If your site does not support secure connections, Bold360 opens the chat in a popup window and switches to HTTPS. In this case, you must include the Google Analytics snippet at the top of the Chat Window Javascript Include code to be able to send tracking data to Google Analytics.

Tracking messages contain specific video chat events that are assigned to individual Event Categories. This data is appended to _tEvents objects.

  1. Use the following Chat Frame Javascript Include code on your site:
    /* Chat Frame Javascript Include */
    
    try {
      var VIDEOCHAT_CATEGORY = 'Video Chat';
    
      var trackEventByVideoSessionStatus = {
        3: { event: "videochat-started", initiatedBy: "By Visitor"},
        4: { event: "videochat-started", initiatedBy: "By Operator"},
        7: { event: "videochat-ended", initiatedBy: "By Operator"},
        8: { event: "videochat-ended",  initiatedBy: "By Visitor"}
      };
    
      function sendtxt(txt, category, parameter) {
        var message = JSON.stringify({
          gacomm: txt,
          eventCategory: category || 'Live Chat',
          eventParameter: parameter || 'Chat Window'
        });
    
        parent.parent.postMessage(message, "*");
      }
    
      sendtxt(bcConfig.chatOptions.page);
      window.console && console.log("Sent Chat Window Page: " + bcConfig.chatOptions.page);
      if (bcConfig.chatOptions.page == "chat") {
        var _tEvents = {
            "new-message": "bc_newHistoryMessageCallback",
            "video-support": "bc_chatWindowLoadedEventCallback",
            "video-statechange": "bc_videochatStatusChangedCallback"
          },
          _tFunction = function(i, type, fName, value) {
            if ((i == "new-message") && (bc.$("#bc-status-prompt").prev().hasClass("bc-operator-message"))) {
              sendtxt("answered");
            }
    
            if ((i == "video-support")) {
                if (bcConfig.videoSupport) {
                    sendtxt("videochat-available", VIDEOCHAT_CATEGORY);
                }
                else {
                    sendtxt("videochat-unavailable", VIDEOCHAT_CATEGORY);
                }
            }
    
            if ((i == "video-statechange")) {
                var trackEvent = trackEventByVideoSessionStatus[value];
                if (trackEvent) {
                  sendtxt(trackEvent.event, VIDEOCHAT_CATEGORY, trackEvent.initiatedBy);
                }
    
                if (bcConfig.videoSupport.isAudioOnly && trackEvent && trackEvent.event === "videochat-started") {
                  sendtxt("videochat-audio-only", VIDEOCHAT_CATEGORY);
                }
              }
          }
      }
      for (var i in _tEvents) {
        window[_tEvents[i]] = _tFunction.bind(window, i, "function", _tEvents[i]);
      }
    } catch (err) {
      window.console && console.error(err);
    }
    Tip: Looking for a quick solution? Download the full code by clicking the attachment of this article.
  2. In Google Analytics, ga_events objects must contain the new event definitions in the Chat Window Javascript Include.
    var ga_events = {
      "prechat": 'PreChat Form Displayed',
      "chat": "Chat Opened",
      "answered": "Chat Answered",
      "postchat": "Survey Displayed",
      "email": "Email Form (Unavailable)",
      "no-operators": "Unavailable Chat",
      "chat-sent": "Survey Completed or Transcript",
      "message-sent": "Unavailable Email Sent",
      "final": "Chat Ended without Survey or Transcript",
      "videochat-available": "Video Chat Available",
      "videochat-unavailable": "Video Chat Unavailable",
      "videochat-started": "Video Chat Started",
      "videochat-ended": "Video Chat Ended",
      "videochat-audio-only": "Chat is Audio Only"
    }
    Update the ga message to send new tracking parameters.
    function listener(event) {
      if (event.origin !== "https://livechat.boldchat.com") return;
      var pmessage = JSON.parse(event.data);
      if (pmessage.hasOwnProperty('gacomm') 
          && pmessage.hasOwnProperty('eventCategory') 
          && pmessage.hasOwnProperty('eventParameter')) {
        window.console && console.log("Received: " + event.data);
        var received = pmessage.gacomm + "-" + bcConfig.cid;
        var found = false;
        lscache.flushExpired();
        CIDs = lscache.get('CIDs');
        if (CIDs !== null) {
          var arrayLength = CIDs.length;
          for (var i = 0; i < arrayLength; i++) {
            if (CIDs[i] == received) {
              found = true;
              break;
            };
          };
        } else {
          CIDs = [];
        }
        if (!found) {
          CIDs.push(received);
          lscache.set('CIDs', CIDs, 60);
          window.console && console.log("Sending new event to GA: " + received);
          try {
            ga('send', 'event', {
              eventCategory: pmessage.eventCategory,
              eventAction: ga_events[pmessage.gacomm],
              eventLabel: pmessage.eventParameter
            });
          } catch (err) {
            window.console && console.error("Google Analytics UA code not found on page");
          }
        }
      }
    }
    if (window.addEventListener) {
      addEventListener("message", listener, false)
    } else {
      attachEvent("onmessage", listener)
    }
    } catch (err) {
      window.console && console.error(err);
    }
    Tip: Looking for a quick solution? Download the full code by clicking the attachment of this article.

Reporting

Events are reported with a few seconds' delay under the Real-Time Events section and they are processed and made available within 24 hours under the Behavior section as well as Dimensions in Custom Reports, allowing maximum flexibility to be tied to any other Google Analytics dimension and metric.


Troubleshooting

For troubleshooting purposes and to ensure that events are transmitted correctly, the code above outputs three log lines for each chat event in the browser console, if available.


Similarly, in case the Google Analytics code is not found by Bold360 on the hosting website page, the following error is thrown in the browser console, if available:


Create a Floating Chat Button

Chat buttons are entry points that visitors use to engage with you. They can be customized to meet the needs of each area of your site.

Now you?ll create your first chat button and generate a very important snippet of HTML code. You?ll use the HTML code on your site to deploy chat; don?t worry if you aren?t ready for that step yet ? you can also preview test chats from within the Bold360 Admin Center.

Note: This article is part of a Quick Start Guide to help you implement your Bold360 environment from scratch.

To see the below steps in action, view our tutorial:

  1. In the Web Admin Center, go to Channels > Chat > Chat Buttons (Floating).
  2. Click My Chat Button to edit.
  3. From the Chat Window drop-down, select My Chat Window that you have previously set up.

  4. If you have one department, select it under Department. This will route any chats that come in through this button to agents within that department.
    Note: If you have multiple departments, you can find more information on your routing options in Route chats to your agents.
  5. We recommend using your own custom image for the button itself. To do so, select Custom for Image Source. This custom image should be hosted on a URL, so that you can point to the button in Available Chat URL.
  6. We also recommend using another custom image for an unavailable button. To move forward with this recommended approach, select Show Unavailable button under When Unavailable. This custom image should also be hosted on a URL, so that you can point to the Unavailable button within Unavailable Chat URL.
  7. Once you have completed all the steps outlined, you are ready to generate the HTML to place on your website. To do so, on the left side of the page, go to the HTML tab.
    1. Under Website, select My Website.
    2. Under Auto-Invite Ruleset, select My Invite Ruleset .
    3. Click Generate HTML.

      You may be prompted to save your changes.

    4. Once HTML is generated, click Copy to clipboard.
    5. Paste this code into your favorite text editor such as Notepad. We do not recommend pasting code into Microsoft Word as it can break the code with styling or line breaks. Our best practice recommendation is to deploy this code to a staging site first. From there, review the widget and make any changes you want. Upon doing so, regenerate the code and then send it to your web developer to be added to all pages on your live website! Note that any test data will appear in reporting.
      Note: If you don?t have a custom button image, you can use our default image by keeping Image Source set to Predefined options.

Need more info? There?s a section about chat buttons in our Support Center.

Create a Chat Window

The chat window is where you configure the customer?s chat experience. It controls the look and feel and advanced behavior of the interface that is opened when a customer clicks an associated button. Chat windows can be customized in a number of ways.

Note: This article is part of a Quick Start Guide to help you implement your Bold360 environment from scratch.

To see the below steps in action, view our tutorial:

  1. In the Web Admin Center, go to Channels > Chat > Chat Windows.
  2. Click My Chat Window.
  3. On the General tab, do the following:
    1. Ensure Layered is selected for both Desktop and Mobile. We recommend using a layered window as opposed to a pop-up window to provide a modern, optimal user experience.
    2. For Messaging when agent not reached, select Condition-specific. This provides customers with more specific messaging (such as out of business hours or full queue) when agents are unavailable.
    3. If you want agents or customers to be able to send files, check Enable under File transfer. You can choose whether this is enabled from agent to customer, customer to agent, or both.

  4. If wanted, you can enable a pre-chat form, which will prompt customer for information before they are connected with an agent. To do so, navigate to the Pre-chat form tab.
    1. Enable pre-chat form. You can select For customer-initiated chats only.
    2. Choose the fields you want to include under Standard fields. We recommend using Name, Email, and Initial Question. To start, we recommend not making them Required as they may deter customers from chatting.

  5. On the Post-chat tab, do the following:
    1. You can choose to allow customers to send themselves a transcript. If so, enter the email address you want it to send from and choose whether it should be sent in Plain Text or HTML format.
    2. You can enable a Post-Chat form, which prompts a customer for feedback after their chat conversation ends. To do so, under Customer survey, choose option to Show when chat ends.
    • We recommend choosing If customer sends more than 2-3 messages
    • We recommend choosing Overall and Comments to start to keep it simple and encourage customers to fill out the survey. (Adding too many fields may deter customer from providing feedback). Using these two fields allows customers to provide a numeric score and open-ended feedback.
  6. You can customize the user interface of the chat window on the Customization tab. You can find a full list of customizable attributes here. Below, you?ll find the most important configuration items to change and where to do so:
    1. Layered - Basic > Colors > Header Background Color
    2. Layered - Basic > Window > Window Title
    3. Layered - Basic > Colors > Content Background Color (R, G, B)
    4. Layered - Basic > Colors > Button Background Color

  7. Save your changes.

Enable file transfer in the chat window

You can enable file transfer in the chat window for both agents and customers.

  1. Create or edit a chat window, as follows:
    1. In the Web Admin Center, go to Channels > Chat > Chat Windows.
    2. Select an existing chat window or click Create New.
  2. On the General tab, enable File transfer.
  3. Select who can send files during a chat:
    • Agent to customer
    • Customer to agent
  4. Save your changes.
Remember: To implement a chat window, you must associate it with a chat button.

What are best practices for file transfer?

It is possible to enable agents and customers to send files to each other. In the chat window settings, you can set this in one or both directions depending on your use case. We typically recommend turning this option on in both directions.

More efficient resolution through file transfer leads to increased customer satisfaction.

How to use Geofluent for auto-translation

Important: Please contact your Customer Success Manager to enable this feature if you want to use it.
Tip: Check out this video to learn how auto-translation work.

Digital DX AI offers automatic language translation in conversational and search modes. It enables your bot to answer your international visitors in any language while end user requests are served from one knowledge base in one language. This feature helps the multilingual support of knowledge bases that frequently change without the need of having to provide the translations as well. The translation engine supports more than 46 languages. The quality of Digital DX's automatic translation is almost as high as if you used a dedicated knowledge base per language.

Customers can switch between viewing the original bot or agent message, and the translated version of the message provided by GeoFluent. By using the toggle displayed above the input filed at the bottom of the widget, customers can check the original message in case of unclear translations. Currently, this toggle is always switched on.

Important: This feature requires a GeoFluent subscription that you can acquire by contacting Lionbridge. Lionbridge will provide you with the account key and secret you need to start using auto-translation.

Features and Benefits

  • Language selector in the beginning of the conversation.
  • Answer content, FAQs, and widget interface are automatically translated.
  • Language selection is saved if the bot conversation is transferred to a live agent.
  • Customers can easily switch between original and translated message.

What languages does GeoFluent support?

GeoFluent supports the following languages in the chat window:

Afrikaans* Arabic* Bengali* Bulgarian* Chinese (Simplified)* Chinese (Traditional)*
Croatian* Czech* Danish* Dutch English (UK)* Finnish*
French French (Canadian)* German Greek* Hebrew* Hindi*
Hungarian* Icelandic* Indonesian* Irish* Italian Japanese
Kazakh Korean Lithuanian Malay* Norwegian (Bokmal)* Norwegian (Nyorsk)*
Polish* Portuguese* Portuguese (Brazilian)* Punjabi* Romanian* Russian*
Serbian Slovak* Spanish Swedish* Tagalog Thai*
Turkish* Ukrainian* Vietnamese*      

* You need to translate the branding of the chat windows.

How to set up auto-translation with GeoFluent?

To set up auto-translation, contact your Customer Success Manager with the following information at hand:

  • GeoFluent Host
  • GeoFluent Account Key
  • GeoFluent Account Secret

How to enable auto-translation?

Once your GeoFluent account is set up for your Digital DX AI account, all your conversational widgets can provide live translations. To enable it, you must set up a language selector as follows:

  1. In the AI Console, go to Knowledge > Add Article.
  2. Create a welcome message as an article, which includes the language selector.
  3. Add a < language_selector / > tag to the article. This tag will be replaced by the languages drop-down list.
  4. Optionally, add a "languages" attribute to the < language_selector > to define the supported customer languages: By default, all languages are listed in the language drop-down list that are supported by your GeoFluent account. The list of languages must be a comma separated list of two-character language codes.
  5. Once you create this message, go to Touchpoints > Widgets and select the widget where you want to use the language selector.
  6. In the Auto Question field, select the newly created message.
  7. Save your changes and you are good to go.

How to use auto-translation with a Digital DX Agent integration?

At the beginning of a chat session, customers can select their language in the widget. When the chat is channeled to a human agent, Digital DX Agent receives the selected language value from Digital DX AI and automatically offers the relevant GeoFluent translations.

Auto-translation in Digital DX Agent takes the following parameters into account:

  • Customer language: Determined by the customer's chat window's language setting or the language the customer selected on the pre-chat form. You can define chat window language defaults in the chat window configuration.
  • Agent languages: The languages the agent speaks, prioritized by fluency level. Configured in the agent settings.
  • Language pairs: The translation pair is supported by your GeoFluent subscription.

If the agent and the customer share a common language, then there is no need for translation and it is switched off by default. Otherwise, if none of the agent languages match the customer language and the language pair is available, messages are translated automatically.

Reports for auto-translations provided by GeoFluent

When auto translations for conversational mode is enabled for an account, you can run reports on three new fields in the Automatic translation section of the Admin Center > Reports page:

  • Auto-translated - true if the query sent to the bot was auto-translated by GeoFluen
  • Query language - the language code of the original end-user query before auto translation. It is "empty" if live translation did not happen for the query
  • Original message - The original end user query before auto translation. The number of unread agent messages can be displayed on the conversational widget in Normal with minimized option mode.

You can group reports by the Auto-translated and Query language options.

Translation Analytics

You can generate reports on GeoFluent-based auto-translation on the Analytics > Reports page of the AI Console. You can select the following report fields from the Automatic translation category:

  • Auto-translated: Displays whether the customer voice was auto-translated
  • Query Language: Language of the original customer voice
  • Original Message: Content of the original customer voice

Notification of auto-translation failure

If GeoFluent translation service is used and it fails to translate the response, a message is displayed that the translation service is not available. The user can then resend the request.

You can display additional record details on the Salesforce panel both in compact and expanded modes.

Remember: When you search for a record in the Bold360 Salesforce panel, the results are listed in compact mode. To switch to expanded mode, click the arrow to the right of the Salesforce record.
  1. To display additional details of Salesforce records, go to Salesforce Setup > Object Manager tab and select a Salesforce object.
  2. On the Page Layouts tab, select the