Messaging Articles

How to configure Digital DX AI after setting up a messaging channel

Once you have set up a WhatsApp or Microsoft Teams messaging channel, complete additional configuration in Digital DX AI to customize the bot's behavior.

  1. Define the answer the bot returns when it can't answer the customer's question.

    You can set up multiple messages or create articles that the bot returns when the customer's search yields no results. See How to configure conversational touchpoints to learn more about how to set these up.

    Note: You can't use an article for the final message as that prevents the bot from triggering the escalation.
  2. Define channeling policies to cover different scenarios.

    Depending on whether you have a bot-only, agent-only or bot and agent messaging channel, you may define different channeling policies. See How do I define a channeling policy? to learn more about how to create a channeling policy.

    Agent only

    If you want your customers to talk to agents only on the messaging channel, set up a channeling policy with a condition where the number of words is greater than 0. Add a message as an error answer that introduces the escalation option and explains customers that they will be connected to a live agent if it's business hours and agents are available.

    Note: To prevent the bot from providing an answer, you must have an empty knowledge base.
    Bot only If you want your customers to talk to the bot only on the messaging channel, make sure you have defined error answers for when the bot can't find an answer to the customer's query.
    Agent and bot experience

    If you want customers to talk to the bot first and outside business hours but have the option to talk to an agent, you might want to:

    • Define a Day and time condition for the channeling policy that is used to escalate chats to agents
    • Use labels on articles for which you want to provide agent support and define an Article label condition for the channeling policy
What's Next?

See What are the best practices for managing a knowledge base? to learn about how you can optimize the bot's content.

How to configure the Agent Workspace after setting up a messaging channel

Once you have set up a WhatsApp or Microsoft Teams messaging channel, complete additional configuration in Bold360 Agent to customize the agent experience.

  1. Set up a department for your new channel.

    If you didn't select a department during the integration steps, now's the time to do so.

  2. Enable messaging channels for agents.
    1. Log in the Web Admin Center.
    2. On the Organization > Agents page, select the agent.
    3. On the Agent information tab, under Channels select Agent is available for Additional Channels.
    4. Save your changes.
  3. Optional: Set up Smart Advisor.

    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.

    To use Smart Advisor as an agent, see Smart Advisor: Chatbot-assisted conversations.

    To set up Smart Advisor, see Integrate a chatbot.

  4. Optional: Set up canned messages.

    Canned messages are predefined strings of text that an agent can insert into a conversation. With canned messages, agents can send common responses without typing.

    To use Canned messages as an agent, see Canned messages for chat: Using predefined replies.

    To set up Canned messages, see Canned messages for agents.

  5. Optional: Set up wrap-up fields.

    You can create labels (wrap-up fields) to organize items in a channel automatically according to rules or manually by an agent during wrap-up.

    To use wrap-up fields as an agent, see How to prepare a wrap-up.

    To set up wrap-up fields, see Wrap-up Fields: Organize items by Category, Custom Field, Status.

  6. Optional: Set up automatic distribution.

    Automatic distribution is available for messaging channels under Messaging > Automatic Distribution. See Set up automatic distribution for messaging.

  7. Optional: Set up routing rules.

    You can route your incoming messages to specific departments based on rules that you set up in the Web Admin Center. See Manage incoming messaging items according to rules (Messaging Rules Engine).

  8. Optional: Set up inactive conversations.

    You can use this option to avoid the problem of filling up the agents' active queue. See How to configure messaging channels for more information.

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.

What are messaging applications in Digital DX AI?

Messaging applications in Digital DX AI enable you to communicate with your customers over popular messaging apps, such as WhatsApp and Microsoft Teams.

Note: Messaging applications are in beta. Contact your Customer Success Manager to learn more.

When you set up a messaging channel, you have the following options depending on your support needs:

  • Provide bot-only support if you do not have human agents
  • Provide agent-only support if you want your customers to always talk to a human agent
  • Use the combination of bot and agent support, if you want the bot to cover out of hours support and help your agents during business hours
Note: You need access to the AI Console if you want to use a bot only on your messaging application. For an agent-only and a bot and agent experience you need to have access to both the Agent Workspace and the AI Console.

Customers can interact with agents on their favorite messaging application in their own pace. The connection between the customer and the agent is permanent from the customer's perspective. Customers can start and stop the conversation in the messaging application anytime without losing connection to the agent.

To learn more about what the experience is like for customers and agents, see these articles:

How to configure messaging channels

Once you created a messaging channel for WhatsApp or Microsoft Teams, you can change the default status messages, define a context, or set up to auto-end conversations.

Make sure you have created a messaging channel.

  1. In the AI Console, go to Touchpoints > Widgets.
  2. Under Conversation configuration, select Messaging applications.
  3. Choose (Configure) next to the channel that you want to configure.
  4. Adjust the options as necessary.
    Status messages

    You can change the default messages for the following cases:

    • The conversation is escalated or closed
    • There is a network issue and the customer's message cannot be delivered
    • There are multiple answers for a customer question
    Contexts If you use context to have article variations for the WhatsApp or Microsoft Teams channel, you can specify the context here to let the bot know which variations it can display to customers. See How do I define an article's context? to learn more.
    Auto-end configurations

    Bold360 can automatically end conversations after the specified time measured from the last customer-sent message. You can define an interval between 30 minutes and 24 hours.

    You can also define a message for customers when their conversation automatically ends.

    Nanorep Entities

    When users ask questions on Microsoft Teams, now they can receive personalized answers . For example, if Bold360 is integrated with a third-party ticketing system and the agent asks How many open tickets do I have?, Bold360 can deliver a response that is specific to the user.

    To enable personalized answers, select the Enable Nanorep Entities option for the Microsoft Teams channel you configured under Touchpoints > Widgets > Messaging applications. Then create articles with personalized answers using entities.

  5. Save your changes.

How to renew connection to your Facebook account

Unless you log in to Facebook, the connection to your Facebook account expires in 60 days and your Digital DX integration stops working.

To continue using Facebook Messenger as a channel, do the following:

  1. On the Facebook Messenger Accounts page, select an account.
  2. On the Account Settings page, select Renew connection to your Facebook account.
  3. To reconnect Facebook to Digital DX, click the Log In button showing the Facebook logo.

    You are prompted to enter your Facebook account details.

    Tip: If you are using a custom app approved by Facebook to manage Facebook Messenger, click Show Advanced Setup and enter details as required (App ID, App Secret, Access Token, Webhook URL, Token).
  4. Save your account settings.

What's the customer experience like in WhatsApp?

Learn how articles created in Bold360 AI are displayed in WhatsApp.

The way articles are displayed in WhatsApp differs from how they are displayed in widgets because WhatsApp is a text-based messaging app. When creating articles that are to be presented in WhatsApp, keep the following in mind:

  • WhatsAppcandisplay text, but it doesn?t present inline bulleted and numbered lists, tables, or carousels.
  • It supports simple URL links but can?t handle links to email addresses or to other articles in the knowledge base.
  • It automatically removes embedded videos and advanced text formatting from articles.
  • Conversational flows and entities are supported except for persistent and quick buttons. Persistent and quick buttons are presented as texts and the user can enter the number of the option or the name of the option to continue the flow.
  • When the bot finds multiple answers to the user's query, the bot lists options as a numbered list and suggests the user to enter the number of an option. Should customers change their mind, they can still select a different option:
  • Agent escalation works by setting up channeling policies in Bold360 AI. Once the conversation is channeled, the bot stops responding and lets the agent continue the conversation. Customers see a message when the conversation is escalated to an agent and when it ends. Customers however don't have an option to end the conversation with the agent.

How to set up a WhatsApp messaging channel

To use WhatsApp for communicating with your customers, you need to create a messaging channel in Bold360 AI.

Make sure the following steps have been completed:

  • You purchased a WhatsApp Business Account and your Customer Success Manager has completed the necessary configuration settings to enable WhatsApp integration.
  • You have created an API key in Bold360 AI that meets the following criteria:
    • It is set up to have access to the knowledge base you selected in the previous step
    • It has all permissions set to write
    • Its allowed IP ranges are set to 0.0.0.0-255-255.255.255

      Go to Admin Center > API Keys in Bold360 AI to see a list of already existing API keys or to create one. See How to create an API key in Bold360 AI to learn more.

  • If you want to use live agents too, make sure you have integrated Bold360 AI with Bold360 Agent.
  1. In the AI Console, go to Touchpoints > Widgets.
  2. Under Conversation configuration, select Messaging applications.
  3. On the Channels tab, choose the plus icon to create a new channel.

    Result: You are taken to the Create Channel page.

  4. On the Create Channel page, enter a name and a description for the channel.
  5. Select the knowledge base that the bot should use to serve your customers.
  6. Enter the knowledge base API key.

    You need to provide an API key here that meets the following criteria:

    • It is set up to have access to the knowledge base you selected in the previous step
    • It has all permissions set to write
    • Its Allowed IP ranges are set to 0.0.0.0-255-255.255.255

      Go to Admin Center > API Keys in Bold360 AI to see a list of already existing API keys or to create one. See How to create an API key in Bold360 AI to learn more.

  7. Select Bold360ai for Escalation Provider Type.
    • Make sure you have the correct Bold360 integration URL.

      Your integration is either in the US or EU region. For an EU-based integration, add -eu into the integrations field. Otherwise, leave it empty.

    • In the API Key filed, enter your Bold360 Agent API key.

      To get this API key, log in to the Bold360 Admin Center and go to Integrations > API Access Keys and create a new key. Make sure you select the correct chat window.

    • Select the Smart Advisor Knowledge Base that will offer potential responses to your human agents during chat.
  8. Select WhatsApp for Provider.
  9. In the DeploymentID field, enter your WhatsApp deployment ID.

    To get the DeploymentID, go to the WhatsApp Deployments tab of messaging applications.

    Note: The WhatsApp deployment was created beforehand with the help of your Customer Success Manager and should be active.
  10. Save your channel settings.
What's Next?
  • Read this article to learn how to configure your messaging channel further.
  • See this article to complete additional configuration in Bold360 AI.
  • Read this article for additional configuration steps in Bold360 Agent.

How to add and customize the Bold360 search widget in Microsoft Teams

As an administrator of your company, you must install the Bold360 app in Teams just as any other app.

What's the customer experience like in Microsoft Teams?

Learn how articles created in Bold360 AI are displayed in Microsoft Teams.

The way articles are displayed in Microsoft Teams differs from how they are displayed in widgets. When creating articles that are to be presented in Microsoft Teams, keep the following in mind:

  • Microsoft Teams can display text, lists, tables, but it can't present carousels.
  • It supports URL links, links to email addresses and to other articles in the knowledge base.
  • It can display embedded videos and advanced text formatting in articles.
  • Conversational flows and entities are supported except for persistent buttons. Persistent buttons work the same way as quick buttons: once the user selects an option, the buttons disappear.
  • When the bot finds multiple answers to the user's query, the bot presents the options as buttons.
  • Agent escalation works by setting up channeling policies in Bold360 AI. Once the conversation is channeled, the bot stops responding and lets the agent continue the conversation. Customers see a message when the conversation is escalated to an agent and when it ends. Customers however don't have an option to end the conversation with the agent.

How to set up a Microsoft Teams messaging channel

To use Microsoft Teams for communicating with your customers, you need to create a messaging channel in Bold360 AI.

Make sure the following steps have been completed:

  • You have created an API key in Bold360 AI that meets the following criteria:
    • It is set up to have access to the knowledge base you selected in the previous step
    • It has all permissions set to write
    • Its allowed IP ranges are set to 0.0.0.0-255-255.255.255

      Go to Admin Center > API Keys in Bold360 AI to see a list of already existing API keys or to create one. See How to create an API key in Bold360 AI to learn more.

  • If you want to use live agents too, make sure you have integrated Bold360 AI with Bold360 Agent.
  1. In the AI Console, go to Touchpoints > Widgets.
  2. Under Conversation configuration, select Messaging applications.
  3. On the Channels tab, choose the plus icon to create a new channel.

    Result: You are taken to the Create Channel page.

  4. On the Create Channel page, enter a name and a description for the channel.
  5. Select the knowledge base that the bot should use to serve your customers.
  6. Enter the knowledge base API key.

    You need to provide an API key here that meets the following criteria:

    • It is set up to have access to the knowledge base you selected in the previous step
    • It has all permissions set to write
    • Its Allowed IP ranges are set to 0.0.0.0-255-255.255.255

      Go to Admin Center > API Keys in Bold360 AI to see a list of already existing API keys or to create one. See How to create an API key in Bold360 AI to learn more.

  7. Select Bold360ai for Escalation Provider Type.
    • Make sure you have the correct Bold360 integration URL.

      Your integration is either in the US or EU region. For an EU-based integration, add -eu into the integrations field. Otherwise, leave it empty.

    • In the API Key filed, enter your Bold360 Agent API key.

      To get this API key, log in to the Bold360 Admin Center and go to Integrations > API Access Keys and create a new key. Make sure you select the correct chat window.

    • Select the Smart Advisor Knowledge Base that will offer potential responses to your human agents during chat.
  8. Select Microsoft Teams for Provider.
  9. In the Channelid field, enter your Microsoft Office tenant ID.

    To get your tenant ID, in Microsoft Teams, right-click a team and select Get link to team. Ask your administrator if you need help.

  10. Save your channel settings.
What's next?
  • Make sure Allow sideloading of external apps and Allow external apps in Microsoft Teams are enabled and use the .zip file attached to this article to add the Bold360 app to Microsoft Teams. For more information refer to Microsoft?s documentation.
  • Read this article to learn how to configure your messaging channel further.
  • See this article to complete additional configuration in Bold360 AI.
  • Read this article for additional configuration steps in Bold360 Agent.

Receive internal support in Microsoft Teams

To get internal support from the bot, search for Bold360 in the search field of Teams. When the app opens, you have the following options:

Get instant self-service support
Type your question at the bottom of the app to get an immediate answer for the bot. If the bot does not provide any answer, try to rephrase your question.
Escalate chat to a live agent
When the answer that the bot provides is insufficient, you can escalate the chat to a human agent. Send a message to the bot with the word escalate and wait for an agent to join the chat.
Add Bold360 to your Teams apps

During a conversation, you can add Bold360 to your Teams apps so that you can find it easier later on. To do so, click Add at the top of the app. You can open Bold360 from your Teams apps.

Announcements

Join the DX Community!

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

Join the DX Community

Featured

Allowlists and the Bold360 platform

Allowlists and the Digital DX AI platform

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

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

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

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

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

LogMeIn IP ranges

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

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

IP addresses for the sign in service

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

  • 34.199.209.240
  • 35.173.84.18
  • 78.108.120.24
  • 173.199.2.47
  • 173.199.4.47

Email addresses for the sign in service

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

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

Third-party IP Ranges

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

Email Domains

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

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

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

 

Update as of January 18, 2022

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

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

  • bold360.com
  • boldchat.com

Alternatively, you can allowlist the following DNS servers:

Ireland

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

Frankfurt

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

US East (N. Virginia)

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

US West (Oregon)

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

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

Ireland

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

Frankfurt

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

US East (N. Virginia)

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

US West (Oregon)

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