Here is the list of all the steps available in the Bot Editor to send messages of different formats to your customers on the Messenger 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 option sets the "Get Started" screen text that customers see when they first access private messages in your Messenger account.

It also allows you to set the “Stick Menu” for the Messenger channel, which is the “burger” menu that customers can open to access links to your website for example.

It is triggered when the customer clicks the “Start” button.

First Conversation

This step is necessary and should be added to the scenario. It deals with a specific case, but it is important, especially at the beginning of your contract with Alcmeon.

It is triggered when a user with a conversation history on this channel BEFORE the account was logged into Alcmeon sends a new message.

Technical explanation: This message does not trigger "Get Started", nor a "Next Conversations" since in Alcmeon there is no conversation in the past, nor an "Unexpected Text" since the message is not in a conversation already started.

Following conversations

This step determines the bot's behavior during a new conversation, as opposed to its very first conversation in the channel. It is triggered when there are messages in Alcmeon that formed a previous conversation (in the Alcmeon sense) for this client, and this client sends back a new message that is the start of a new conversation.

Note: When all previous messages from the customer have been “anonymized” (special action for GDPR compliance), if the customer sends a message, then this step is triggered.

Unexpected text

This step is used to intercept messages typed by a customer in the middle of the decision tree, when they would be expected to click a button presented to them instead. It is triggered when ALL of the following conditions are met:

• the customer sent a message
• this message is not a click on a button or on another element of the scenario), it is therefore a message typed by the client himself
• in the same conversation as this message from the customer, there is a message immediately preceding it which is a message sent by the bot as part of THIS scenario
• This previous message from the bot does not have a "free message entry" or "default response" output, because in this case the script should follow that output, which takes precedence over "unexpected text".

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 text message sent can often, depending on the channel, contain emojis or an image, video, audio file or attachment.

Message only

This step sends a simple text message to the customer.

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

Carousel

This step 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 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.
 

Media

This step could also be named “media with buttons”: it allows to send an image or a video, without accompanying text, and up to 3 buttons can be optionally displayed below the media. The buttons behave as described above in the Carousel section.

Button

This step could also be named “text with buttons”: it allows to send a simple text, without accompanying image, and up to 3 buttons can be optionally displayed below the media. The buttons behave as described above in the Carousel section.