ChatBridge24

CHATBOT SCENARIOS

A WhatsApp chatbot you draw, test and publish

A scenario is drawn, not scripted. Place the blocks, connect their paths, try it in the Test chat and publish it — and every run stays inside limits that keep a loop from becoming a bill.

The WhatsApp chatbot in ChatBridge24 is an advanced WABA bot you draw yourself. It greets a new chat, offers buttons or a list, asks for the details you need and checks them, and hands the conversation to your team when a person should take over.

Most of what a business is asked on WhatsApp is asked again and again: where are you, what does it cost, is it still available, can somebody call me. A scenario answers those the moment they are asked, at any hour, and steps aside when the question needs a person.

Scenarios run on numbers connected to the WhatsApp Business API. In Bitrix24 the same builder comes with the ChatBridge24 app on the Bitrix24 Marketplace, as the Bitrix24 WhatsApp bot.

Last verified 2026-10-24 — against the scenario builder released on that day.

Scenario Live on +971 4 ●●● ●●●● START Any first message ASK A QUESTION Are you looking to rent or to buy? CONDITION The answer contains “rent” or “buy” SEND Rental list SEND Sales list NO MATCH, OR WAIT 10m Hand to a person and stop the scenario LAST RUN · EVERY STEP RECORDED 09:02:11 Start · matched the first message 09:02:11 Asked: Are you looking to rent or to buy? 09:04:48 Answer “buy” — path 2 matched 09:04:49 Sent: Sales list · billed once, window open
The scenario builder: a drawn flow that asks a question, branches on the answer, and either replies or hands the conversation to a person — with every step of the last run recorded. A drawing of the product.

The blocks you draw with

Four groups in the library — Messages, Ask, Logic and Flow — plus a Start block in every scenario.

Messages

Send message — text with up to three reply buttons, a list of up to ten options, a link button or a request for the customer’s location, with a picture, a video, a document or a title above it where WhatsApp allows one. A Send message block can also name an approved template to send instead once the 24-hour window has closed. Send template — an approved message template, which can be sent after the window has closed. Send file or media — an image, a video, an audio file or a document from the number’s own library.

Ask

Ask a question, a Buttons menu or a List menu. An answer can be checked as a number, an email address, a phone number, a date, a location, a file, a yes or no, or text of a set length or pattern. A wrong answer is asked again in your words, up to five tries.

Logic

Condition takes the first path whose rules match — an answer, the message, a button, the contact’s country, the conversation’s labels, whether the contact is new or came from an ad, the day or the hour. Business hours splits Open and Closed on your working hours and holidays. Set variable, Wait and Go to block complete the group.

Flow

Start another scenario continues the conversation in another live scenario on the same number. End finishes it, and can hold the scenarios back from that conversation for up to a week. Hand to a person stops the bot and leaves the conversation to your team.

Questions that wait well

A question can send a reminder after a silence, then take its own No reply path. A customer who writes a word such as agent or human instead of answering can take an Asked for a person path, which you connect to a hand-off.

Answers you can reuse

Every answer is saved under a name you choose. A later message can use it, together with built-in values such as the contact’s name, your business name, today’s date and the campaign a lead came from — so the next message can greet somebody by the name they just gave you.

When a scenario starts

Several scenarios on one number, each with its own start.

A Start block begins its scenario when a customer writes a keyword, on the first message from a new contact, when a chat came from a click-to-WhatsApp ad or a landing-page campaign, when a customer taps a button on one of your templates, on any message while your team is closed — or on any other message, for the scenario that greets everybody. A keyword can match as a whole word anywhere in the message, as the whole message or at its start, in any letter case, and Arabic matches with or without harakat.

A number can hold up to twenty scenarios, and several can be live at once, in the order you set. A specific trigger always wins over “any other message”, and among equals the scenario higher in the order starts. A scenario can be limited to once per contact in a number of hours, and kept away from conversations that carry a label you choose.

Two rules are always on. A scenario never starts while a colleague is talking to the customer — anyone on your team who has written to them in the last 24 hours from the ChatBridge24 inbox or, in Bitrix24, from Open Channels or a CRM record’s WhatsApp tab — and customers who opted out, or whom your team blocked, never get a scenario at all.

Draft, test, publish

Nothing reaches a customer until you publish it and switch it on.

01

Build it as a draft

Add blocks from the library, connect their paths and fill each block in its own panel, with a preview of the WhatsApp message for the blocks that send one. Saving keeps a draft beside the published version, so what your customers meet does not change while you work.

02

Try it in the Test chat

Write to the scenario as a customer would and tap its buttons. The Test chat runs the same rules as the live bot, highlights the block that is running and shows every saved answer. Nothing is sent and nothing is charged.

03

Publish when the checks pass

Publishing checks the whole scenario and names each block to fix — a path left unconnected, a template that is not approved on this number, a loop that would keep sending without waiting for the customer, a message longer than WhatsApp allows. Every published version is kept and can be brought back as the draft.

04

Switch it on

A conversation already inside a scenario finishes on the version it started on. Building and testing are open on every plan; putting a scenario live needs the Professional or Enterprise plan. Switching a scenario off is always allowed.

The limits

Each one is a real limit in the engine, so a drawn loop cannot become a bill.

01

Four messages per customer message

One message from the customer can produce at most four from the bot. Anything after that waits for the customer’s next message.

02

Twenty-four steps per customer message

Conditions, values and jumps send nothing, so this is the limit on a loop that never sends. A turn that reaches it ends the scenario.

03

Forty messages and 400 steps each time a scenario runs

A menu that returns to itself is a loop on purpose. This is how far one run of a scenario can take it; a run stopped here does not start again in that conversation for at least a day.

04

Ten jumps each time a scenario runs

Go to block and Start another scenario each count as a jump, so two scenarios handing a conversation back and forth stop after ten.

05

Waits of at most 20 hours

A Wait, a reminder or a No reply timer is capped at 20 hours, so the next message still lands inside WhatsApp’s 24-hour customer service window when the customer wrote recently.

06

Up to 150 blocks per scenario

And up to 400 connections between them — room for a full menu, every question and each path back.

Safe on a live number

WhatsApp’s rules, applied block by block.

  • Never the same message twice. Before a block sends, the scenario moves past it. If a server stops at that exact moment the customer may miss that one message, but they never receive it twice.
  • One message at a time. When two customer messages arrive together, only one of them moves the conversation on.
  • The 24-hour customer service window. A free-form message is sent only while the window is open. Once it has closed only an approved template is sent, and a scenario with nothing approved to send ends there.
  • A hand-off is final. After Hand to a person, the bot does not re-enter that conversation; it belongs to your team.
  • Only your words. Every message a scenario sends is one you wrote in a block. The bot does not generate replies with AI.
  • Replies, not cold messages. A scenario starts only when a customer writes or taps a button. To reach somebody who has not written to you, send a template or run a marketing campaign.

Where it sits

Bitrix24 WhatsApp bot

The same scenario builder in the ChatBridge24 app for Bitrix24.

WhatsApp shared inbox

Where a handed-off conversation lands, and who answers it.

ChatBridge24 pricing

Scenarios are in the Professional and Enterprise plans, per connected number.

From the blog

Further reading on this subject.

Building an advanced WABA bot

How a WhatsApp chatbot should answer the repeated question and hand over cleanly.

Building a bot in Bitrix24, step by step

Plan, draw, test and publish a bot that hands over to your Open Channels team.

Running a WhatsApp shared inbox

Ownership, internal notes and response times, without double replies.