Trigger

Starting point of the chatbot flow.

The trigger block is what determines which chatbot is to be executed when a user requests a chat

The trigger block is what determines which chatbot is to be executed when a user requests a chat.

Conditions for trigger

As you can have more than one chatbot on your account, the conditions on the trigger help the system qualify the right chatbot for the conversation.

You can also combine multiple conditions using an AND / OR operation.

The conditions on the trigger can be:

URL	The webpage URL the user is on. For example, "URL contains pricing" or "URL equals https://sopro.io"
Browser language	The default language set by the user on their browser. For example, "Language is French"
Date range	The date when the user is initiating the chat. For example, you can build a separate chatbot flow that activates during Christmas.

Conditions are not mandatory. If you have not defined any conditions for your chatbots, the first active chatbot on the list will be activated.

Inject data into the chatbot

If you want to send external data to the chatbot, you can use this option. Once enabled, you can map the fields that contain the value with the Sopro variable.

Two ways you can inject the data:

Using Query params

With this method, when the Sopro snippet is loaded on the website for the first time, the defined query params and their values will be stored in the variable list.

For example, if your URL is the followingwww.sopro.io/?cust_id=1234&plan=9896

You can choose to store the values of the cust_id and plan on the trigger action block.

Using JSON

With this method, you can inject a JSON payload inside the Sopro’s code snippet and map the objects to be stored in the trigger action block.

To do this you need to add the following object with your desired fields in the Sopro code snippet

data-session-payload='{"field1": "value", "field2: "value"}

Now, let's take an example to understand this.

Assume you are using the chatbot in your web app and you already know who is the user initiating the chat. For your agents to be aware of the user details, you can add their name, email, company, etc. to the Sopro's code snippet.

Copy

<script src="" data-session-payload='{"name": "Charles", "phone": "8164848686"}' defer></script>

We have stored the “name” and “phone" fields to Sopro variables on the trigger action block.

Note:

By default we're already mapping the identified prospect and company data and populating the default set of prospect and company variables. These are then used to personalize the webchat messaging but also are displayed to you in the visitors details info in Live chat.

Note:

• You can include regex expressions on the URL input box.

• You can validate query parameters too by enabling the feature