Feature

Draw the conversation. It runs itself.

A visual builder with twenty-six blocks — messages, buttons, conditions, delays, AI answers, CRM actions and calls to your own systems. Drag them together and the conversation runs without anyone watching it.

Start free See the whole platform

Most customer conversations are not open-ended. They are a path: identify what the person wants, collect three facts, do something, hand over. Drawn out, that path is a flow — and once drawn, it runs consistently at three in the morning.

The builder is visual because conversations are branching things, and a diagram is how people actually think about them. What it produces is not a script but a working automation, connected to your contacts, your CRM and your other systems.

What it does

The parts that matter

Twenty-six building blocks

Text, images, documents, location, buttons, lists, forms, templates, conditions, switches, delays, AI, CRM actions and HTTP calls.

Buttons instead of typing

Every question you turn into a tap is one the flow cannot misread.

Branches and conditions

Split on a tag, an answer or a contact field, and send people down genuinely different paths.

It can act, not just reply

Tag a contact, add them to a list, create a lead, move a stage, assign an agent.

It can call your systems

An HTTP request node fetches an order, checks stock or writes to your database mid-conversation.

Reusable sub-flows

Build "collect address" once and call it from everywhere instead of copying it.

Triggers: what starts a conversation

A flow can start from an exact keyword, a phrase, a message that merely contains a word, a new contact's first message, a reply to a campaign, or any message at all. When several could match, the most specific wins, so a precise keyword is never swallowed by a catch-all.

Keyword matching — exact, phrase, starts-with, contains, multi-word
Campaign follow-ups — a reply within your chosen window starts the right flow
Ad referrals — someone arriving from a click-to-WhatsApp ad can be greeted differently

Handing over is a feature, not a failure

The best automated conversations end at the right moment. An Assign to Agent node is the proper exit from any path where a person adds value — and because automation stands down when an agent replies, the handover is clean rather than a bot talking over a colleague.

Route by topic — billing to one team, bookings to another
Context arrives with it — everything collected sits on the conversation
Opt-outs stop everything — including steps already waiting behind a delay

Questions

Straight answers

Do I need to write code?

No. The only node that involves technical setup is the HTTP request, and that is optional — most flows never use it.

Can I test before going live?

Yes, and you should. Run the flow against your own number first; the builder can tell you a branch is connected but not that it reads badly.

Does the same flow work on Instagram?

Instagram supports a subset — text and quick replies work, while WhatsApp-specific elements like templates and forms do not. Build channel-appropriate flows rather than expecting one to cover both.

What if someone says something unexpected?

Add a Knowledge Base Answer node as the catch-all, so an off-script question is still answered from your documents rather than dead-ending.

See it working on your own numbers

We will connect your WhatsApp number, load your documents and show you real answers to your real questions — before you commit to anything.

Start free Talk to us

No card required for the walkthrough.