Skip to main content
Bot Builder · Phase 2

No-code flows, with an escape hatch when you need it.

Drag nodes. Connect with arrows. Publish. Most flows take 10 minutes. The hard ones — those that talk to your database — get an API node and stay readable.

Lead-qualifier flow

Published

🎯 Trigger · keyword "hi"

💬 Welcome · "Hi {{name}}, what brings you here?"

🔘 Buttons · Buying / Renting / Just browsing

→ Buying

📋 BHK + budget

→ Renting

📋 Move-in date

→ Browsing

📤 Send brochure

🔌 API · POST /leads/qualify

Routes to right agent based on score

Sample flow · 7 nodes · 3 branches · counts shown post-launch.

Eight node types

The building blocks every flow needs.

💬

Text

Plain message with variables (name, business, last-order-id) auto-filled.

🖼

Image / Video / Doc

Send media inline. Carousel templates supported via the same node.

🔘

Buttons

Quick-reply buttons (up to 3) — clicks become trigger events for the next node.

📋

List

WhatsApp List Message with sections + items. Selection routes to specific branches.

📝

Flow

Native WhatsApp Flow form — short-answer / multi-select / date / phone fields.

🔌

API call

POST/GET to your backend with the customer's data. Use response in the next node.

🔀

Condition

Branch on any field, button, reply text, or external API result.

🎯

Trigger

Keyword (case-insensitive), button-click, or external webhook starts the bot.

What makes ours different

Six things you should expect from a bot builder in 2026.

01

Drag-and-drop canvas

Pan, zoom, snap-to-grid. Connect nodes by dragging from output port to input port. Built-in undo/redo.

02

Live publish toggle

Edit a draft side-by-side with the live version. Publish swaps atomically — no in-flight conversation breaks.

03

Per-node analytics

Each node shows hit count + drop-off %. Spot the question that 40% of users abandon at, fix it, A/B.

04

Fallback handler

When a customer replies in a way the bot did not anticipate, route to a "send to human" handler with full context.

05

Variable substitution

{{name}}, {{lead.email}}, {{api.last_order.amount}} — anywhere a node accepts text.

06

Test mode

Run a private test on a connected number without exposing the bot to real customers. Each test is logged.

Who uses Bot Builder most

Three flows that pay for themselves in a week.

01

Insurance agents

Lead qualifier — name, age, annual income, policy interest, sum-assured. Routes to the right agent based on profile.

02

Real-estate agencies

Pre-screen — budget, BHK, location, loan-pre-approved. Saves 20-min phone calls; only qualified leads reach a human.

03

Healthcare clinics

Appointment booking — service, doctor, slot. Confirms via List message, books in calendar via API node.

FAQ

Common questions about Bot Builder.

Is this no-code or low-code?
No-code by default. Most flows can be built without writing anything. The API call node is the escape hatch — when you need real logic (database lookup, complex calculation), POST to your backend and use the response.
How do I avoid making my customer feel like they are talking to a bot?
Two patterns work: (1) be honest — start with "Hi, I am a bot. Reply HUMAN to talk to my team." (2) keep flows short — 3-5 nodes for a qualifier, not 20. Long bots feel bot-like; short ones feel like form-fills.
Can the bot read my Shopify orders?
Via the API call node — POST to a Shopify endpoint, parse the JSON, use {{api.response.order_id}} in the next message. Native Shopify integration ships in C-15 (Q4 2026); until then, the API node bridges it.
What happens when WhatsApp adds a new message type?
We add it as a new node type within 2 weeks of Meta announcing it. WhatsApp Flows, Carousel, Order Details, and Lists are already supported. Catalog message ships in B-05 (Phase 2).

Build a flow in 10 minutes. Run it for years.

Starter ships 1 active bot. Growth scales to 10. Pro adds the API call node + per-node analytics. Every plan ships with a 14-day free trial.

Start Free Trial ← Back to all features