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

AI Bot ✨

This step enables an Artificial Intelligence API (either Natural Language Processing (NLP) or generative AI) to respond to the client's last message.

For more details, see our dedicated article: Create your AI Bot scenario

AI satisfaction ✨

This step is designed to be used after an AI has provided a response, allowing you to collect customer feedback on the AI's performance.

For more details, see our dedicated article: Create your AI Bot scenario 

First conversation

This is the main entry point to your WhatsApp account, kicking off the moment a customer sends their very first message. It's your bot's chance to shine with a warm welcome message and present a clear menu of options for the rest of the scenario.

For each subsequent conversation after the first one that triggered the "First Conversation" step, the "Subsequent Conversations" step will be triggered: so it's just as important to write a good welcome message in this case!

After that initial interaction, every chat the customer starts will trigger the Subsequent Conversations step. Just like the first, it's crucial to craft an inviting welcome message here.

Following conversations

This step dictates your bot's behavior for all interactions after a customer's very first chat on the channel. It's triggered when a customer, who has a history of previous conversations within Alcmeon, initiates a new message that marks the start of another conversation.

Note: Even if all of a customer's prior messages have been "anonymized" (for GDPR compliance), this step will still be triggered if they send a new message.

Unexpected text

The Unexpected text step is designed to catch messages a customer types when your bot expects them to click a button or interact with a specific scenario element instead. It is triggered when ALL of the following conditions are met:

• The customer sends a message.
• This message isn't a click on a button or any other pre-defined scenario element; it's text the customer typed themselves.
• Immediately preceding the customer's message, the bot sent a message as part of the current scenario.
• That previous bot message doesn't have a "free message entry" or "default response" option. If it did, the bot would follow that path, as it takes precedence over “Unexpected text.”

In short, this step ensures your bot can intelligently handle situations where a customer deviates from the expected interaction flow, allowing you to guide them back or offer relevant assistance.

Welcome Message

The Welcome Message is a special step that defines the very first messages your bot sends when a customer opens a conversation with your WhatsApp account.

This message is delivered only when two specific conditions are met: The customer accesses your WhatsApp conversation for the first time AND their message input bar (at the bottom of the WhatsApp app) is completely empty – meaning they haven't typed anything yet.

In your Alcmeon bot's workflow, you can connect the Welcome Message step to any series of other steps For example, you could link it to a Single Message step followed by a List Message step. In this scenario, your new visitor would immediately receive both of these messages as soon as they open the chat with your bot.

WhatsApp cart sent

💡Advanced feature, please contact Alcmeon support for activation.

This step isn't about sending a message; instead, it's triggered automatically when a customer, using WhatsApp's multi-product message feature, compiles a cart and then validates and sends it to you

Typically, you'll link this step to a confirmation message, such as: "Thank you for validating your basket! Please click here: [payment_url] to finalize your order."

The actual payment process must occur on your own website or mobile application, as WhatsApp does not provide an integrated payment solution.

Message only

This step sends a simple text message to the customer.

This step must be connected to another step. Failing to do so will result in the conversation abruptly stopping for the customer.

Message with buttons

This step sends a message accompanied by buttons that guide the customer through your scenario.

You can include one, two, or three buttons (neither 0 nor 4) with each message.

When a customer clicks a button, its label is sent back to your bot as a text message, allowing your scenario to advance. 

Once a button is clicked, it becomes unclickable to prevent re-submission, while any other buttons in the message remain active.

If you need to ask a question that requires a free-text response from the customer (rather than a button click), you'll need to use the "Message with Choices" step described below.

Message with choice

This step sends a message to the customer and then waits for a specific numbered response, such as "1", "2", "3", and so on. 

The list of available choices is automatically added to the message body, so you don't need to include them in your text.

This step has been replaced by Meta's provision of "Messages with Buttons" and therefore remains particularly useful when you need to ask a customer a question that requires a free-text answer. For instance, you can use it to collect their name, email address, postal code, or any other open-ended input. In such cases, the bot will proceed through the "other answer" output, which functions like a "free entry" message.

List Message

This step allows you to send a message that includes text and a button which presents a categorized list of choices.

This is particularly useful when you need to offer more options than the three-button limit of the "Message with buttons" step. 

Within this dialog, you can provide between 1 and 10 options, which can be organized into up to 10 "sections" (but they are optional).

Each section can have a title (up to 24 characters).

Each clickable option includes a title (up to 24 characters) and a description (up to 72 characters)

Customers can select a single option and click "Send." The title of their chosen option is then sent as a text message, allowing your bot's scenario to continue to the next step.

WhatsApp template

This step sends a WhatsApp Template to the customer. WhatsApp Templates are predefined messages that must undergo an approval process by Meta.

Their use is billed by Meta (not Alcmeon) according to the rules detailed in the following official article: https://developers.facebook.com/docs/whatsapp/pricing/updates-to-pricing

These message templates come in various types and are highly customizable. For instance, your text can include placeholders that are populated with specific information when the template is used. This customization extends not only to the text itself but also to media elements and even URLs embedded in buttons.

Each template offers design options, including the ability to define a header and footer, along with buttons.

Furthermore, templates support multi-language translations for all their text components.

Models supported for your in Alcmeon scenarios:

• Text Message Templates
• Media-based Message Templates, including images, videos, or files
• Interactive message templates, featuring quick reply, URL, and phone buttons
• Carousel Templates
• Coupon Code Templates
• Limited Time Offer Templates
• Multi-Product Message Templates, linked to your Meta product catalog
• And more to come, as Meta releases them!

1. Creating Templates

First, create your templates directly from Alcmeon , even if you don't have an administrator role in your Meta Business Portfolio (formerly Business Manager): Navigate to Alcmeon's settings, select the "Message Templates" section, and follow the guided WhatsApp template creation process. 

Once created, your templates are submitted to Meta for validation. This usually takes only a few minutes.

Should your template be rejected, Alcmeon will display the reason for rejection. Rejected templates cannot be used.

2. Choosing and Configuring a Template for your Scenario

Select the "WhatsApp Template" step and drag it onto your scenario timeline. Click the "pencil" icon to open its editing panel. Click "Select a Template" to view all your Meta-approved templates. 

A template list will appear, allowing you to choose the desired template with a single click.

You can review the template's characteristics, including its title, content, buttons, and variables. You can also filter templates by country using the flag icon in the top right corner.

If necessary, you will then need to populate the various variables in your template with text and/or custom fields. This allows you to send personalized templates with your customers' data.

Ice breakers

Previously, these special buttons were designed to appear for your customers when they first opened a conversation with your bot.  However, Meta announced in October 2024 that this feature has been discontinued until further notice.

Buttons from Variable

The “Message with buttons from variables” step is used to send a Message with buttons or a List Message. The difference is that the buttons labels can be a list of variables instead of static ones.

This step automatically generates the appropriate message type (with buttons or list message) depending on the number of variables. If you have up to three variables, it will send a “Message with Buttons”. For more variables, it will send a “List Message”.

The variables are typically retrieved using our “API Connector” step allowing you to build the message.

Typical Use Case: Imagine your bot has the customer's phone number. It can then use the "API Connector" step to retrieve a list of offers that the customer is eligible for, then present those specific offers to the customer.