A scenario is a chain of messages triggered by a condition (e.g. "Bot start" or a visit through a specific landing-page link). Every scenario has three tabs: Settings, Messages, Analytics.
Scenario "Settings" tab
- Scenario name
- Toggles: "Allow the scenario to restart" and "Start the scenario automatically"
- "Start conditions" block — you can add several conditions (e.g. "Bot start" + a visit via a specific landing page), and for each one enable "Jump to a specific message"
"Messages" tab and the scenario map
A list of the scenario's messages plus a "Scenario map" button — a visual, drag-and-drop canvas showing the connections between blocks: entry points ("Bot start", a specific landing page) are connected by lines to message cards, and each card can be dragged and rewired right on the canvas.
Clicking the gear icon next to a message opens a context menu: Analytics (open rate, replies), Edit, Duplicate, Direct link (to the message), and Delete.
| Type | Description |
|---|---|
| Regular message | Text/media, sent along the "next step" chain |
| Scenario start + AI agent | The first message drives the conversation through an AI agent instead of fixed text |
| Booking reminder | Sent automatically a set amount of time before a booked appointment |
Full anatomy of a single message's settings
Opening a message via "Edit" expands a long form — it's identical for scenario messages and for broadcasts.
Name, agent, and text
The message name (for your own navigation — the subscriber never sees it), the choice of AI agent if the message drives a conversation, and the text itself in a mini text editor with formatting (bold, italic, strikethrough, underline, code, quote, plain text, link), plus emoji insertion and a @field mention.
Additional instruction for the agent
A text field the agent sees but the subscriber doesn't. The platform explains its purpose like this: "You can pass the agent extra information about the subscriber, such as their profile fields. The subscriber won't see this text." It's used to inject context on the fly (a name, a purchase history) into the system prompt of a specific conversation.
Attachments and data to save
Attachments — files/photos attached to the message. Data to save — which profile fields the agent should fill in based on the conversation (e.g. saving a phone number the subscriber mentioned into the phone_number field).
Conditions for ending the AI agent's conversation
The platform explains it like this: "Specify the conditions under which the agent should end the conversation. For example: 'The user agreed to pay' or 'The user is off-topic'. Once the condition fires, you can specify further actions — for example, move to another scenario or send another message." There's a ready-made condition type "Number of replies" (a numeric value — how many subscriber replies the agent will handle before ending) — it comes with its own set of actions from the same catalogue described below.
Delivery toggles (available on any message, including broadcasts)
- Track link clicks — click statistics for links in the text
- Enable link preview — show a preview card for a link in the message
- Send text line by line with a delay — the text arrives in chunks, with a pause, mimicking "is typing…"
- Wait for the subscriber's reply — the message is "paused" until the recipient reacts, before it's counted as delivered/processed
Conditions for sending the message
Filters and modifiers applied before sending:
- Send only if the subscriber is in a segment — show it only to the chosen audience
- Send to a group or channel — instead of a private chat
- Send to the subscriber's email — duplicate it by email
- Replace another message — the new message overwrites a previously sent one instead of being sent as a separate item
- Disable forwarding — the subscriber won't be able to forward the message to others
- Add to lists
- Scheduled sending — a specific date/time
Actions after receiving the message — the platform's universal automation builder
This is the platform's most powerful piece: a set of actions that run once the subscriber has received (or replied to) the message. Sets can be tied to different segments — the platform explains: "If the subscriber falls into a segment, that set of actions runs; otherwise the bot checks the next segment." The same action builder is used in triggers, in AI-dialogue completion conditions, and in post-booking / booking-cancellation actions. The full catalogue of action types:
| Group | Actions |
|---|---|
| Subscriber | Change subscriber field · Save subscriber count · Add tag · Remove tag · Add manager · Remove manager · Block in bot · Unblock in bot |
| Message | Add to scenario · Remove from scenario · Send message · Delete message · Pin message · Unpin message |
| API | API request (starts with a "Request type" field — an HTTP method like GET/POST — followed by the URL and parameters) · Activate trigger |
| Button | Remove active button · Remove active keyboard |
| Group | Block in group/channel · Unblock in group/channel · Refresh status from group/channel |
| Google Sheets | Get value · Add row · Edit row · Delete row · Add sheet · Delete sheet |
| AmoCRM | Add deal · Edit deal |
| Yandex Metrica | Send conversion |
| Yclients | Add client by phone number · Remove client by phone number · Send client SMS |
The combination of "Add tag" + "Send only if the subscriber is in a segment" (a segment based on that tag) is exactly how most sales funnels are built here — without a single line of code.
At the bottom of the form there are three buttons: Save, Send now, Send to tester (check it on yourself before publishing).
Buttons in messages
A button is a separate settings block, added via "Add button" on any message. The full list of 12 types:
| Button type | What happens on click |
|---|---|
| Link button | Opens an external link |
| Action button | Runs an action set on the subscriber (the same catalogue as above) |
| Article button | Opens a specified article from the "Content" section |
| Booking button | Opens the booking calendar |
| Buy product | Opens the product payment page |
| Buy subscription | Opens the subscription payment page |
| Subscriber's account | The subscriber sees information about their active subscription and can cancel it |
| Comments | Opens the comments page |
| Keyboard button | Replaces the subscriber's keyboard (a set of quick replies) |
| Share phone number | The subscriber sends their phone number to the bot |
| List button | Opens a list with dialogue messages via send conditions; requires Inline Mode enabled through @BotFather |
| Copy text | The specified text is copied to the clipboard |
| Forward text | The subscriber picks a chat and forwards the specified text there |
Ready to automate your business?
More than 15,000 bots have already been created on the platform
Create chatbotFree trial — no card required