Here is the list of all the steps available in the Bot Editor to send messages of different formats to your customers on the AlcmeonChat channel.

AI Bot ✨

This step allows an artificial intelligence API (NLP or generative) to respond to the client's last message.

See our dedicated article: Create your AI Bot scenario 

AI satisfaction ✨

This step is intended to appear after an AI has given a response, so you can collect customer satisfaction with the AI's response.

See our dedicated article: Create your AI Bot scenario 

Get Started

This step is triggered when the customer clicks the button that opens the chat window, which can be linked to a welcome message and a menu of options for the continuation of the conversation.

On the other hand, it allows you to define the "persistent menu" of the AlcmeonChat channel which opens by clicking on the menu button to the right of the message entry area.

Message with menu

This step sends a text message along with a series of "quick replies," which are buttons the customer can click. These buttons disappear when one is clicked. Once a button is clicked, the label on that button is the message sent by the customer.

In the Alcmeon bot editor, you can connect each button to another step, so that the scenario continues when the customer clicks on it.

The sent text message can contain emojis, an image, a video, an audio file, or an attachment.

Message only

This step sends a text message to the customer, like the "Message with Menu" described above, but without a button.

This step must be connected to another step, otherwise the bot scenario will abruptly stop at this step for the client.
 

Carousel

This feature allows you to send a set of up to 10 slides, which can scroll horizontally. Each slide can contain an image, then a title (maximum 80 characters), an optional subtitle (maximum 80 characters), and up to 3 buttons.

Each button can either be connected to another step in the scenario (continuing the bot experience for the customer), or open a URL that you can define.

Unlike the "quick replies" described in the "Message with menu" step, clicking a carousel button does not make it disappear: the customer can go back in their conversation history to click the same button again or another carousel button.

Request email/SMS notification

SMS notification no longer available until further notice

Allows you to ask for the customer's email and/or phone number during the scenario, so that they are notified when an advisor sends a response in the conversation.

Note: This notification will not be sent if the client still has the AlcmeonChat interface open in the active tab, as it is assumed that they are still reading the conversation.

Several parameters are available at this stage. In particular, in the "SMS/Email Content" field, you must insert the variable(s) corresponding to what you want the customer to receive as notification content by SMS or email.

Here is the list of available variables:

• {{last_user_message}}
• {{answer}}
• {{landing_page_url}}

Classic example:

Hello, an advisor has replied to you. Here's his reply: 

{{answer}}

Click on this link to continue the discussion: {{landing_page_url}}

Retrieving and using an external variable

Example use case: You want to use AlcmeonChat on pages where your customers are logged in, and you want to retrieve some of their personal data to pass it to inMessage and make it visible to your agents and/or use this data as part of the conditional logic of your bot scenario.

Information about the logged-in user is passed to inMessage via attributes consisting of a list of key/value pairs (example: {"user_firstname":“Jean”,"user_lastname":“Dupont”} ).

To learn more: https://developers.alcmeon.com/docs/inmessage-authentication

These values can be called as variables in your bot's scenario, with attributs.user_firstname and attributs.user_lastname in our example.

The search for information is done in two stages:

1. Creating an action in Alcmeon: storing each attribute in a new variable.
2. Creating a custom field: Store each variable from the previous step in a custom field that you have previously created.

1. Action in Alcmeon

Variable attributes cannot be used directly (e.g. to populate a custom field).

So in a scenario we need to create a first step "Action in Alcmeon", which will feed new variables with the attribute variables.

In our example (we create the variables user_firstname and user_lastname):

• user_firstname = attributes.user_firstname
• username = attributes.username

These two variables can then be used in our scenario.

2. Custom field

To use this information (for example, to display first and last names in the inMessage Inbox ), we need to define Custom Fields that will be populated by the variables previously created in our “Action in Alcmeon” step.

In our example: we need to create two custom fields that could be named:

• Name
• First name

Then create a “Custom Fields” step in the scenario:

• Type: variable
• Use the name of the variable defined in the Action step in Alcmeon (here: user_firstname)
• Specify the Custom Field to fill in (here: Name)