Third party bot providers can be used and managed through LivePerson's Conversational Cloud just like a normal human agent or a LivePerson bot Using our connectors, you can provision IBM Watson, Google Dialogflow, Amazon Lex, or Microsoft bots. You can also leverage LivePerson Functions to build custom integrations with other third party bot providers.

If you need to connect an external bot that does not have a pre-built connector, see this document for instructions.

Some connectors may provide more or less functionality depending on the specifics of the provider.

We will be automatically error escalate any new conversation if the bot has reached the limit of 999 open conversations. To mitigate this issue, please consider setting a lower value for closing inactive conversations for your bot skills and also add more bots.

Please be advised that we recommend to have one bot for 250 open and active conversations, if you want your to handle more load, please add more bots to ensure a smooth and convenient consumer experience. Furthermore we recommend adding at least 2 bots for one bot skill to support a failover and a higher availability in case of any service interruptions and issues.

Please be advised that you should create fresh bot agents for your bots. Using the same bot agents for ConversationBuilder and ThirdPartyBots will break both bot instances. Conversational Cloud only allows one active user session per agent. Thus, bots created in Conversation Builder and Third-Party Bots with the same bot agent will eventually kick each other out.

Bot Lifecycle

During run-time, your bot may have different operational states. These states are based on the health status of the services it utilizes, such as LivePerson APIs, AI vendors, etc.

Bot State Description
Offline The bot is offline and won't accept any conversations.
Online The bot is online and will accept and process new conversations.
Vendor Interruption The bot is online and will accept new conversations, but will directly escalate them to the default transfer skill, because the configured AI Vendor is not reachable/working.
Service Interruption The bot is in the delayed state and will not accept new conversation or process existing conversations. This state is a result of an interruption within LivePerson APIs/servers.In this state the bot will try to restart automatically once every minute until the interruption is resolved.


Supported customer content events

Currently, the bot connectors only support following events from the customer:

We do not support passing of any other UMS events. If the customer sends an rich content or a file to the bot, the bot will replace it with a special identifier so the bot can handle this special use-case with custom code. Those identifies are as follows:

  • Rich Content Identifier:
  • File Content Identifier:

Support for different messaging channels and corresponding rich content

The bot Connector system is designed to support all relevant rich content since it only forwards the received structured content and metadata to LivePerson's messaging and chat services, where it is handled. We have verified and tested the support for Web Messaging, Facebook and Apple Messages for Business. All other channels are not verified, but should work if you send the right structured content for the channel. If you experience any issues, please contact LivePerson Support (use the chat on this page, or message Support) or your account team.

Creating and starting bots

Due to limitations within the Conversational Cloud's permission system, it is not possible for an operator with the Agent or the Agent Manager profiles to create new bots or start bots. However, they are still able to stop, edit and delete existing bots.

If you want to enable creating and starting bots for the Agent and Agent Manager profiles, you need to create a new custom Profile, which will derive its base permissions from the Campaign Manager or Admin profiles. Then, make sure to enable the needed permissions for creating and starting bots only while disabling any other permissions. Afterwards, you will need to assign this new Profile to the Agent/Agent Manager who should be able to start/create bots.

Minimal set of permissions for creating and starting bots for Campaign Manager Profile

Minimal set of permissions for creating and starting bots for Administrator Profile

Intent and actions evaluation

Please note that your bot setup should always return an intent or an action as a response. If you return an intent without actions or messages, or return no intent at all, the bot will consider this an error and escalate to the default escalation skill.

Getting Started

Create a Bot User in the Conversational Cloud

  1. Add a new user in the Conversational Cloud. Choose "Bot" for “User type”. If bot is not available as a user type, contact your LivePerson account manager to enable the feature.

  1. Under login method, choose "API key" and generate a new API key for the user

  1. Make sure the user has chat and/or messaging slots (more than 0 for either), based on the channel you'd like the bot to take conversations from.
  1. Find the API key name you created above the in bot user profile

Provision a connector

To enable Third-Party bots, contact your Account Manager to enable the feature in the Conversational Cloud for your account.

Upon logging in to Conversational Cloud, you will see the Conversation AI Tab:

Follow the steps below to add a new bot.

  1. Click on the "Third-Party Bots" App.

  2. Click “+ Add Bot” in the bot table

  3. Choose Bot Type: Decide which type of bot you want to add.

  4. Assign agent: Create a new bot agent or select the agent you created in the step above

  5. Conversation Type & Error Handling: Choose bot type specific configurations follow Bot Type for a detailed description on the configuration of these steps.

  6. Connect to A.I.: Choose an AI engine from the list of available configuration. See Next Steps.

Next Steps

Move on to the product guides to learn how to connect and configure your specific bot framework/builder.