Frequently Asked Questions

Allowlists and the Digital DX AI platform

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

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

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

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

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

LogMeIn IP ranges

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

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

IP addresses for the sign in service

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

  • 34.199.209.240
  • 35.173.84.18
  • 78.108.120.24
  • 173.199.2.47
  • 173.199.4.47

Email addresses for the sign in service

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

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

Third-party IP Ranges

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

Email Domains

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

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

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

 

Update as of September 14, 2021

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

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

  • bold360.com
  • boldchat.com

Alternatively, you can allowlist the following DNS servers:

Ireland

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

Frankfurt

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

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

Ireland

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

Frankfurt

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

Bold360 version 21.11 contains the following new enhancements:

New KB Launchpad Intent Library for COVID-19/Vaccinations

In order to help businesses with providing just-in-time information related to updates to COVID-19 and vaccination protocols, a new entry in the KB Launchpad is now available with intents that can be used to deploy knowledge to keep your workforce informed of new policies and information that you may need to enforce.

Not familiar with the KB Launchpad? The KB Launchpad contains pre-defined intent libraries to help you add industry and use-case specific questions/intents to your KBs with your own specific responses to help with adding commonly asked questions for newly created KBs.

We will be enabling the KB Launchpad as a default setup option on all accounts shortly but contact your Account or Success Manager to get it enabled early if necessary.

ICO Cookie Compliance

In order to support ICO cookie compliance in regions that require end-user consent for allowing cookies to be set, Genesys DX now complies with this standard by making the tracking and analytics related cookies that are set through the touchpoint and visitor monitoring HTML snippets to be optional.

By default, all cookies will continue to be set upon page load. To restrict these cookies from loading automatically and only upon end-user consent, additional steps will be required on the website that the Genesys DX code is being deployed to.

You can learn more about what this compliance is and how to update your Genesys DX deployment to be compliant by reviewing the details in this article: ICO Cookie Compliance.

How to work with Salesforce in Bold360

The Salesforce integration in Bold360 delivers highly customizable Customer Relationship Management (CRM) experience to Bold360 agents while they chat with customers. The integration increases agent efficiency by making Salesforce customer data directly available from Bold360.

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

Agents can access their company's Salesforce account during chat from the custom integration panel.

Agents can do the following during chat:

  • Search for customer data in the company's Salesforce account

  • Create and update accounts, leads and any other default or custom Salesforce objects directly from Bold360

Automatic lookup of Salesforce records during chat

When you open the Salesforce integration panel, Bold360 automatically searches for records in Salesforce that are associated with the relevant Salesforce objects as follows:

  • Bold360 searches for Salesforce records based on the customer's email address, first name, or last name, which is gathered from the pre-chat form of the chat window.
  • Bold360 then searches for those Salesforce records, which are related to the retrieved contact record and were defined during the Salesforce integration process.
  • If no contact record is found then, using the customer's email address, first name, or last name, Bold360 looks up any Salesforce record that were mapped to Bold360 during the Salesforce integration process. See Integrate Salesforce into Bold360.

How to search manually for Salesforce records during chat

If automatic lookup does not show any result, you can still manually search for information that is relevant to the customer in your company's Salesforce database. To do so, type a term in the search field and press Enter. The results are displayed on tabs, where each tab represents a Salesforce category. Click on a search result to see detailed information.

After searching for customer data, you can either link the current chat to an existing record or create a new record in Salesforce.

How to link a chat conversation to Salesforce during chat

When you find customer data in Salesforce about the person who you currently chat with, you can link the current or a past chat session to the customer's record in Salesforce. This way, you can append the chat transcript in Salesforce to the customer's chat history that helps your sales team to follow up with customers. To link a chat session, click the Link button next to the item in the results.

The chat transcript is sent to Salesforce when the chat is closed in Bold360.

Note: You can link the chat conversation only to one Salesforce record on each tab.

How to create Salesforce records during chat

If your search does not retrieve any result, you can create Salesforce records while you chat with a customer.

  1. On the Salesforce panel, click Create a New Contact at the bottom of the results list.

    Depending on what type of customer data you want to create, the button is named differently.

  2. Fill in all available information. Details that the customer provide on the pre-chat form are filled in automatically.
  3. Click Save & Link.

The new contact is now available in Salesforce and the chat transcript is automatically linked to it.

How to enable the Salesforce integration in Bold360

After setting up Bold360 Conversation Integration, the connection between Salesforce and Bold360 must be enabled.

  1. In the Web Admin Center, go to Integrations > Salesforce.
  2. Select the domain that you want to use to connect to your Salesforce account:
    • If your organization registered a custom domain with Salesforce, such as yourdomain.my.salesforce.com, then select Use a custom domain and define that domain in the field below.
      Tip: If your organization enforces Single sign-on ("SSO"), see How to set up a custom Salesforce domain in a single sign-on environment.
    • Otherwise, select Connect via salesforce.com
  3. Click Set up integration.

    Result: You are redirected to Salesforce.

  4. On the Allow Access page in Salesforce click Allow.

    Result:

    Note: You cannot change the list of required permissions. You are redirected to Bold360.
  5. Optional: Select the Trigger Filters that you want to apply to block certain agents from using the Salesforce integration.

How to install Bold360 Conversation Integration in Salesforce

How to install Bold360 Conversation Integration in Salesforce

The Bold360 Conversation Integration app acts as a mediator between Bold360 and Salesforce and is responsible for the communication between the two systems.

  1. Make sure that all customer information that identifies a Salesforce object is also configured on the Bold360 pre-chat form. You can do so in Channels > Chat Windows > Edit Chat Window > Pre-chat form.

    Result:

    Tip: The integration retrieves better results if the customer provides more information on the pre-chat form.
  2. Log into your Salesforce account and follow this link to install the package.
  3. On the Install Bold360 Conversation Integration page, check the option, select who can use the app, and click Install.
    Note: At the moment the Bold360 Conversation Integration app is not a part of Salesforce's AppExchange Partner Program.
  4. On the Approve Third-Party Access page, select Yes, grant access to these third-party web sites and click Continue.
  5. Click Done.
    Note: The installation may take a while. You will receive an e-mail once it's done.

The Bold360 Conversation Integration app appears on the Installed Packages page of Salesforce.

How to create data source entities

Use data source entities in Bold360 AI to turn your data into smart conversations.

Make sure your widget is set to conversational. Learn more here.
In this example, we have a list of mobile phones and we want to create a bot that recommends users the best mobile devices based on their needs. We are going to set up a data source entity based on this list of mobile phones and then create an article that uses this entity.
  1. Create the list of mobile phones in a CSV file.

    A sample CSV file is attached at the end of this article. Learn more about the different data source options and requirements in this article.

  2. In the AI Console, go to Knowledge > Entities.
  3. Choose (Create Entity).
  4. Select data source entity for entity type.
  5. Provide a name and optionally a description for the entity.

    The entity name can contain letters, numbers and underscores. Spaces are not allowed.

    You can use the description to give the entity a more meaningful name or description that helps you identify it later.

    Example: Name your entity MOBILE_PHONES.

  6. Fill out the Data Source URL field.

    You can select the CSV file from your local computer and upload it to Bold360 AI' secure server or you can upload the file to a file hosting service like OneDrive and enter its URL here.

    Note: If you provide a link to the file's location, make sure it's publicly accessible.
    See What are the data source URL options? for more options.
  7. Set the response type to CSV.
  8. Choose LOAD.

    Result: The properties table is now loaded. Properties are the columns that are available in the data source file.

  9. Fill out the Properties table.

    See What are the property options for data source entities? and How do life cycle options work? to learn more about the options.

    Example:

    You should decide what questions the bot should ask the end users to offer the best possible recommendation about phones. In this example, the bot asks questions about brand, price range, and camera quality.

  10. Optional: Define fallback messages.

    See What are fallback messages? to learn more.

    Example: For this example, we enter Unfortunately, there's no mobile device that matches your preferences. for no results and set up a carousel to be displayed with the image, the brand and model, and the price if there are multiple results based on the customer's responses.

  11. Save your changes.
  12. Now go to Knowledge > Articles.
  13. Create a new article or open an existing one and add the entity in the article's body.

    In the article's body, create the final response of the bot: this is what the bot responds when there is a single mobile device to recommend. The response should use the entity to present the details of the selected mobile device. To insert an entity, you can either choose or enter [[ in the text editor and have a drop-down of all entities displayed. Once you add an entity to the response, the entity is automatically added to the article. You can expand the entity to see the questions that the bot may ask the user and adjust them to fit the article if needed.

    Note: You can drag-and-drop entities in the Article Editor to control the order of the questions in the conversation.

    Example: Intent: I want to buy a mobile phone

    Body: ?

  14. Publish the article.

You can now see the conversation in action in your widget ? just enter I want to buy a mobile phone.

Important: The bot doesn't always ask all the questions we set in the entity. It can automatically identify when there is no need to ask a question, for example, when there is only one possible result left. In addition, the order of the questions might differ as the bot automatically chooses the order based on what it estimates as the fastest way to get to a possible answer.

Featured

Bold360 21.11 Release Notes

Bold360 version 21.11 contains the following new enhancements:

New KB Launchpad Intent Library for COVID-19/Vaccinations

In order to help businesses with providing just-in-time information related to updates to COVID-19 and vaccination protocols, a new entry in the KB Launchpad is now available with intents that can be used to deploy knowledge to keep your workforce informed of new policies and information that you may need to enforce.

Not familiar with the KB Launchpad? The KB Launchpad contains pre-defined intent libraries to help you add industry and use-case specific questions/intents to your KBs with your own specific responses to help with adding commonly asked questions for newly created KBs.

We will be enabling the KB Launchpad as a default setup option on all accounts shortly but contact your Account or Success Manager to get it enabled early if necessary.

ICO Cookie Compliance

In order to support ICO cookie compliance in regions that require end-user consent for allowing cookies to be set, Genesys DX now complies with this standard by making the tracking and analytics related cookies that are set through the touchpoint and visitor monitoring HTML snippets to be optional.

By default, all cookies will continue to be set upon page load. To restrict these cookies from loading automatically and only upon end-user consent, additional steps will be required on the website that the Genesys DX code is being deployed to.

You can learn more about what this compliance is and how to update your Genesys DX deployment to be compliant by reviewing the details in this article: ICO Cookie Compliance.