Flows — visual builder

Flows are automated scenarios in direct messages. You draw a scenario on a visual board: blocks are connected with arrows, and when a client types a keyword, comments on a post or subscribes, the flow leads them through the steps on its own — it replies, asks questions, checks subscription and hands off to a manager. The section is located in “Automation” → “Flows”.

Triggers — what starts a flow

Trigger	When it fires
Keyword in DM	The client sent a DM containing the needed word
Instagram comment	The client left a comment under a post or Reels
Story reply	The client replied to your Instagram story
Subscription	A new follower on Instagram

For keywords you can set the matching mode — exact word, “contains” or any message. You can specify several words, tie the trigger to a specific post and enable firing once per person. The trigger settings open in the right panel when the start block is selected.

Blocks — what a scenario is built from

Block	What it does
Message	Sends text to the client
Question with awaited reply	Asks a question and pauses the flow until the client replies. The reply is saved into a variable
Condition	Branches the scenario “yes/no” — for example, by a tag or a contact field
Subscription check	Checks whether the client is subscribed to a Telegram channel or Instagram account. Three outcomes — subscribed / not subscribed / error
Delay	Waits for the set time and continues the scenario
Action	Sets a tag, writes a contact field or notifies a manager
Start a sequence	Enrolls the contact into a message sequence
A/B split	Splits traffic between two branches in a set proportion (50/50 by default)
Note	A sticker for the team on the board — the client doesn’t see it

In message texts, variables like {{variable_name}} work — for example, you can insert the client’s reply from a “Question” block.

Note

Subscription check for a Telegram channel works only if your bot is added as an administrator of that channel. On Instagram the check is possible only once the client has already messaged your direct — so put it on the “Keyword” or “Story reply” triggers, or after a “Question with awaited reply” block, rather than right on the “Comment” trigger.

Tip

In an A/B split the same contact always lands in the same branch of a particular test — results don’t “jump”, and the client won’t receive both variants.

How to build a flow

1. Open “Automation” → “Flows” → “New flow” (or start from a template).
2. Drag blocks from the palette at the top onto the board — or click a block to add it to the center.
3. Connect the blocks: drag a line from one block’s point to another. Branching blocks (condition, subscription check, A/B) have their outputs labeled and highlighted in different colors.
4. Select a block — its settings open in the right panel.
5. Set up the trigger on the start block: type, channel, keywords.

Handy things on the board:

• Right-click a block — duplicate, temporarily disable or delete it. A disabled block is simply skipped by the flow.
• Hotkeys — Cmd/Ctrl+Z undo, Cmd/Ctrl+D duplicate, Delete to delete, Esc to exit fullscreen mode.
• Multi-select — hold Shift and select several blocks to move or duplicate them as a group.
• In notes you can @mention a colleague — they’ll get a “You were mentioned in a flow” notification.
• Changes are saved automatically; the validation panel under the board highlights blocks with empty settings and “dangling” connections.

Ready-made flow templates

You don’t have to build from scratch — the catalog has more than a dozen ready-made flows: a welcome series, a “guide” lead magnet, an FAQ bot, lead qualification (quiz), “comment → DM” for Instagram, email collection, a promo code with reminders, booking a consultation, abandoned cart recovery, a review request, “story reply → price list”, a welcome for new followers, a bonus for subscribing to a Telegram channel, a promo code for following on Instagram.

The templates are grouped by category (Leads, FAQ, Sales, E-commerce, IG funnel, Re-engagement), and there’s search. When installing, you choose the channel the flow will run on — or skip this step and link a channel later.

Note

In templates with a subscription check, replace @your_channel with your own channel and enter your own promo code — and don’t forget to make the bot an admin of the channel in Telegram.

You can save your own flow as a team template — colleagues will see it in a separate block of the catalog and deploy it in one click.

Draft, activation and test

• A flow is created as a draft — triggers don’t fire until you switch it on with the toggle in the editor header.
• Test run — the “Test” button runs the flow on a chosen contact to check the scenario before launching it on a live audience.
• The status at the bottom of the board shows the flow’s validity, the number of blocks and the time of the last save.

Versions and change history

Every save of the board goes into the version history (the last 20 are kept). In the versions window you can:

• view the diff — which blocks were added, removed or changed relative to the current version;
• roll back the flow to any snapshot. The current state is also saved to history in the process, so a rollback is safe.

Analytics — where clients drop off

The “Analytics” button in the editor switches the board to a stats-funnel view:

• a summary — total runs, active, completed, errors and conversion;
• per step — how many people reached it and how many dropped off between steps (as a percentage);
• if you enable analytics mode on the board, blocks with active passes are highlighted.

Empty stats right after creation are normal: run “Test” or wait for the first trigger firings.

Scenario examples

Lead magnet for a comment. “Instagram comment” trigger under a Reels with the word “WANT” → DM message → question with awaited reply → subscription check → subscribed: send the guide, not subscribed: ask to subscribe → “tag Warm lead” action → notify the manager.

Bonus for subscribing to a Telegram channel. “Keyword in DM” trigger → channel subscription check → subscribed: give the bonus; not subscribed: ask to subscribe → wait for a reply for up to 24 hours → re-check.

Lead qualification. Keyword → a series of questions with awaited replies (answers are written to contact fields) → condition by the answers → hot leads to the manager, the rest into a warming sequence.

What’s next

• A one-off mass mailing to your base is Broadcasts.
• A scheduled series of messages without branching is Sequences.
• The dialogs that flows and agents run live in the Inbox section.