1. Configure the scenario of your bot

1.1 Select your type of message

• Rich Message* card creation: Send a message without waiting for an answer in return. It can be text or more visual content.
  • This card also allows you to add a hypertext link by clicking on the icon
    • You must enter a message before validating the card, otherwise, the scenario will not be saved.
      
      

• • Next step : 3 actions are proposed after each Message :
    • Continue to step
    • Transfert to a routing rule (with an alternative to transfer option )
    • End conversation
      

Option: For each transfer that your bot will do, you will be able to configure an alternative to transfer in case there is no availability. The alternative action can be: a transfer, forwarding to another card or closing the conversation. 

1.2 Open-ended question card

Ask a question where the user will be able to write the answer

• Ask your question in the "what do you want to ask" section.
• The bot will wait for the visitor's response before proceeding to the next stage of the scenario and will record the data collected temporarily, depending on the name or the email you have defined here.
• It will be possible to re-use this data in the successive stages of the scenario by calling it via the tag {data_name}.

1.3 Multiple choices question

Ask a question where the user can choose between several different options.

You can choose the type of multiple choice question you want to set up: static or dynamic.

• Static MCQ: the visitor's choice must be sent to an API.
• Dynamic MCQ: the question and choices are generated dynamically by the API.

• Create a MCQ and choose the "static" type:

• • Fill in the question, the choices and the technical values that the API expects for each choice.

• • Activate the "save to variable" option and give the card a variable name corresponding to what your API expects to receive.

• • Create an API connection card to send the visitor's choice to the API. For this read point 1.5 of this article.

• Create a MCQ and choose the "dynamic" type:

• • Fill in the appropriate variables for the question, choices and technical values.

• • If necessary create static choices to be displayed before or after the dynamic choices. If you need to send the visitor's choice to an API, activate the "save to variable" option and give the card a variable name corresponding to what your API expects to receive.

• • Create an API connection card to send the visitor's choice to the API. See 1.5 below.

1.4 NLU Question

Ask a question and detect the user intent.

• Add an open question
• Chose an intent
• Define an alternative in case of detection failure. This is triggered if the visitor’s answer is not understood by the bot. Want to know more about how intents work? Please read this article: Intents Manager

1.5 Connection card

Send or request information from your API.

• Choose an API connection and its version
• Possible alternative: the alternative in case of API request failure action is triggered if the API request fails
  Do you want to know more about how the API connection works?
  Click on this article: Connect your bots to your apps

You can edit a card by clicking on , on the top right side of the card.

You will be able to 1) rename the card, 2) move up or 3) move down, 4) duplicate it or 5) delete it.

• 1) Rename card: you can rename the scenario card in order to have a simpler reading of your bot scenario. This also will help you in the Automation report when you will analyse in detail the bot scenario.
• 2) Move up: move the card up in the scenario creation. This will not affect the execution order of your bot scenario
• 3) Move down: move the card down in the scenario creation. This will not affect the execution order of your bot scenario
• 4) Duplicate: Duplicate a card with all the parameters, including the list of intent if you are duplicating an “Intent detection question” card
• 5) Delete: delete the selected card from your scenario

1.6 Condition card

You can set up a condition map and use it to choose future actions to be executed based on variables.

Exemple :

1.7 Geo-routing card

If your brand owns a network of brick and mortar stores, the "geo-routing" map allows you to send conversations from your bot to your in-store teams. To learn more, read the dedicated article.

2. Creation and use of variables

The MCQ card and the Open Question card allow you to create and name qualified variables. These can then be used in cards to appear in other steps of the scenario.

There are 4 types of variables that can be automatically added to the visitor’s profile using bots :

To do so, you have to name the variables exactly like that :

• Firstname => “visitor_firstname”
• Lastname => “visitor_lastname”
• Email => “visitor_email”
• Phone number => “visitor_phone”

3. Verify that you don’t have configuration errors 

Check the error panel on the top right side.

If you have errors displayed, you can solve them by clicking on each error

Then, save your bot by using the Save button.