What Is a Chatbot Flow Builder? A Plain-English Guide

A chatbot flow builder is a tool that lets you design an automated chat conversation step by step, usually on a visual canvas or as a list of blocks, without writing code. Each step is something the bot does, such as sending a message, showing buttons or asking a question, and the customer's answer decides which step comes next.

If you have heard "flow", "journey", "bot builder" or "automation" used for the same thing and want to know what it actually involves, this explainer is for you. It covers the building blocks, how flows differ from keyword replies and AI, a worked example for a Nairobi property agency, and what to look for when choosing one.

What are the building blocks of a chatbot flow?

Almost every flow builder uses the same handful of blocks, whatever the vendor calls them.

In chat.or.ke's Automation & Flows, flows can start from a keyword, a welcome menu or a Click-to-WhatsApp ad; steps can send messages, buttons or lists, ask questions and save the answers as variables, call a webhook and personalise the next message; and automation can be paused on any chat so an agent takes over.

How is a flow builder different from keyword auto replies and AI?

The three are layers of the same toolkit, each suited to a different kind of question.

• Keyword auto replies answer one question with one message: "location" gets the address. Quick to set up, but each reply stands alone.
• Flows run a multi-step conversation with a goal, such as collecting a booking. Predictable and easy to audit, but only cover the paths you designed.
• AI assistants answer open questions in free text from your business information. Flexible, but can make mistakes and need review.

Most businesses use keyword replies for one-off facts, flows for processes and AI for everything nobody scripted, with a person behind all three. For a deeper comparison, see AI chatbot vs rule-based chatbot.

What does a chatbot flow look like in practice?

Here is a worked example for a property agency in Nairobi that runs Click-to-WhatsApp ads for apartments in Kilimani and Kileleshwa. Before the flow, agents spent much of their day replying to enquiries that did not match the listing's budget or area.

Trigger. A prospect taps the agency's ad and sends the pre-filled message. Because the flow is linked to that ad, the agency can see which ad the lead came from.

Step 1: Buttons.

Thanks for your interest in our Kilimani apartments! Are you looking to: [Rent] [Buy] [Talk to an agent]

Step 2: List (if Rent). "What is your monthly budget?" with rows: Under KES 60,000 · KES 60,000–100,000 · KES 100,000–150,000 · Above KES 150,000. Saved as budget.

Step 3: List. "Which area?" with rows: Kilimani, Kileleshwa, Lavington, Westlands, Other. Saved as area.

Step 4: Question. "When would you like to move in?" Saved as move_in.

Step 5: Question. "And your name?" Saved as name.

Step 6: Personalised summary. "Thanks, [name]. You are looking to rent in [area] with a budget of [budget], moving in [move_in]. An agent will share matching units shortly."

Step 7: Hand-over. The chat lands in the agency's shared inbox, assigned to the agent for that area, and the lead appears in the CRM pipeline so it can be followed from enquiry to viewing to signed lease.

The rent figures are the prospect's budget bands, not anything the agency or platform charges. "Talk to an agent" at step 1 skips straight to the hand-over, so nobody is forced through the questions.

What are the benefits of using a flow builder?

The main benefit is consistency at speed: every enquiry gets the same questions answered in seconds, at any hour, and arrives at your team complete.

Others include:

• No developer needed to build or change a flow.
• Cleaner data: answers from buttons and lists are structured, so they are easy to tag, filter and report on.
• Better use of staff time: agents start with qualified leads rather than "hi, is it available?"
• Easy to measure: you can see where customers drop off and fix that step.
• Reusable: the same flow can be triggered by different keywords or ads.

What are the limits of chatbot flows?

Flows only understand what you planned for. A customer who types "I need a 2-bedroom near Yaya with parking for two cars, budget flexible" in the middle of a list step may get "Please choose an option" instead of a helpful answer.

Ways to soften this:

• Keep flows short, ideally under six steps.
• Accept typed answers where you can, and repeat the options at most once.
• Let an AI assistant answer open questions outside the flow.
• Put a "talk to a person" option on every step and recognise words like "agent" or "mtu".

Over-built flows are the other common problem. If a customer has to tap four times to get a price, the flow is costing you sales.

What should you look for in a chatbot flow builder?

Check these before choosing a tool:

1. Interactive WhatsApp messages: native reply buttons and lists. See interactive WhatsApp messages explained.
2. Variables and personalisation: save answers and reuse them later in the conversation.
3. Several triggers: keywords, a welcome menu and ad clicks.
4. Hand-over and pause: pass a chat to a person and stop the bot on that chat.
5. Same inbox: the flow, the AI and your agents should share one inbox and contact history.
6. Webhooks, if you need to send data to another system later.
7. Clear pricing: whether automation costs extra. On chat.or.ke, flows and the AI assistant are included; you pay per message sent, such as KES 0.75 for a reply within 24 hours, with no monthly fee. See pricing.