LINE - scenario steps
Table of Contents
Here's a list of all the available steps in the Bot Editor for sending various message formats to your customers via the LINE channel.
Preamble
LINE's messaging platform operates under a specific rule: you are allowed only one free reply to a customer's message, and this reply must be sent within 30 seconds. This rapid response is exclusively achievable with bots; human agents cannot reply within this tight timeframe. Consequently, the initial message sent by a bot - whether in direct response to a customer's message or a button click - is free of charge.
LINE does offer a method to reply to customers beyond this 30-second window, known as a “push”. However, "push" messages are not free. Companies must subscribe to a specific plan, and LINE directly bills them for these messages. You can find the detailed price list for LINE push messages here: https://www.lycbiz.com/jp/service/line-official-account/plan/ For context, 5,000 JPY is approximately 30 EUR, and 3 JPY is about 0.019 EUR
⚠️ If your company attempts to use Alcmeon's bot and inbox functionalities with a LINE account that is not a business account or has not subscribed to a paid plan, you will encounter various errors within Alcmeon. Consequently, your bots will not function as expected.
AI Bot ✨
This step allows an Artificial Intelligence API (NLP or generative) to formulate a response to the customer's most recent message.
See our dedicated article: Create your AI Bot scenario
AI satisfaction ✨
This step should follow an AI's response, allowing you to collect customer satisfaction with the AI's interaction.
See our dedicated article: Create your AI Bot scenario
Become Friends
This step serves as the primary entry point for new customers engaging with you on the LINE channel. It is triggered in two scenarios:
- When a customer officially becomes a "Friend" of your brand on LINE. This is a mandatory online action required to access the conversation space.
- If a customer was previously a "Friend" but then blocked your brand, this step is triggered again when they unblock you.
First Conversation
This is a necessary step that must be included in your scenario.
It triggers when a user, who has an existing conversation history on this channel prior to your account being connected to Alcmeon, sends a new message.
This message will not trigger a “Become Friends” nor a "Next Conversation" (since Alcmeon has no record of past interactions), nor an "Unexpected Text" (as it's not part of an ongoing conversation within Alcmeon).
Following conversations
This step dictates your bot's behavior for subsequent conversations with a customer, distinguishing them from their very first interaction on the channel. It triggers when a customer, who has a prior conversation history recorded within Alcmeon, sends a new message (in the Alcmeon sense) that initiates a new conversation thread.
Note: If all of a customer's previous messages have been "anonymized" (for GDPR compliance, for example), this "Following Conversations" step will also trigger if that customer sends a new message.
Unexpected text
This step is designed to intercept messages typed by a customer in the middle of the decision tree, when a bot was expecting them to click a button instead. It triggers when ALL of the following conditions are met:
- The customer has sent a message.
- This message is not a click on a button or on another scenario element; it is a text typed by the customer.
- In the same conversation as this message from the customer, there is a message immediately preceding this customer message which is a message sent by the bot as part of this specific scenario.
- That preceding bot message does not have a "free message entry" or "default response" output. If it did, the scenario would follow that designated path, which takes precedence over "Unexpected Text."
Message with menu
This step allows you to send a text message accompanied by a series of "quick replies." These are interactive buttons that customers can click. Once a customer clicks a button, the entire set of quick replies disappears. The label of the clicked button becomes the message effectively "sent" by the customer.
Within the Alcmeon bot editor, you can connect each button to a different step, allowing the scenario to branch dynamically based on the customer's choice.
The text message sent can also support various media elements, including emojis, images, videos, audio files, or other attachments, depending on the specific channel.
Message only
This step simply sends a text message to the customer.
This step must always be connected to a subsequent step. Otherwise, the bot conversation will abruptly end for the customer at this point.
Carousel
This step enables you to send a set of up to 10 horizontally scrollable slides. Each slide can include an image, a title (maximum 40 characters), a text (maximum 160 characters), and up to 4 buttons.

Each button can be configured to either connect to another step within your scenario (allowing the bot conversation to continue) or open a specified URL you can define.
Unlike the "quick replies" described in the "Message with menu" step, clicking a button with a carousel does not make the carousel disappear. Customers can scroll back through their conversation history to click the same button again or another carousel button.
Image Carousel
This carousel presents a series of up to 10 horizontally scrollable slides. Each slide is designed to feature one clickable image and an optional title, which will serve as the label for the button overlaid on the image.

Each slide can be configured to either connect to another step within your scenario (allowing the bot conversation to continue) or open a specified URL you can define.
Unlike the "quick replies" described in the "Message with menu" step, clicking a carousel button does not make it disappear. Customers can scroll back through their conversation history to click the same button again or another carousel button.
ImageMap
This step enables you to send a message featuring a single image with multiple touch zones.

Each area can be configured to either connect to another step within your scenario (allowing the bot conversation to continue) or open a specified URL you can define.
Confirm
This step sends a text message accompanied by exactly two buttons, typically labeled "Yes" and "No."

Each of these two buttons can be configured to either connect to another step within your scenario (allowing the bot conversation to continue) or open a specified URL you can define.
Rich Menu
Advanced feature, please contact Alcmeon support to use it.
This step is triggered by an event containing a payload, which originates from a customer clicking on a tab menu located at the bottom of the chat window in the LINE client application.
This menu is known as the "Rich Menu." It is not managed by Alcmeon. Alcmeon only manages the conversational effect within the chat window when a Rich Menu item is clicked.
A Rich Menu ca contain:
- Buttons designed to open a URL
- Buttons that send a payload into the chat window to initiate a specific scenario.
- Buttons that send a keyword into the chat. This keyword can then be detected by Alcmeon using a"Condition on entered text " step placed after "First conversation", "Following conversations" and "Unexpected text" steps (to cover all possible entry points).