Free Chatbot Builder Flow Check: Find Dead Ends, Broken Buttons and Missing Exits Before You Publish (Free Flow Map Checker)
Free chatbot builder tools make it easy to drag in messages and buttons, and just as easy to publish a bot where visitors get stuck: a button that leads nowhere, a step with no way back, or a booking path that never reaches a person. This guide shows how to write your bot as a one-line-per-step map, check it for the five problems that break most button bots, and fix them before a single visitor sees it.
⚡ In short
- Write the whole bot as a text map before you open any builder.
- Every step needs buttons or an exit. Every button needs a real destination.
- Every step should lead to a person or a contact form within a few taps.
- Keep paths three taps deep and four buttons wide.

Why map first
Builders hide the problems you create
Visual builders show one block at a time. You zoom in on the booking path, wire up three buttons, then move on to delivery questions. Nothing warns you that the “Weekend” button points to a block you renamed an hour ago, or that the pricing branch has no way back.
Visitors find these problems in seconds. They tap a button and nothing happens, or the bot stops talking. They don’t report the bug; they close the chat.
A text map fixes this because you can see the whole bot at once. One line per step, with the message and where each button goes. It takes ten minutes to write, it works for any free chatbot builder or paid one, and it doubles as documentation when someone else edits the bot later. If you haven’t decided which tool to use yet, our chatbot builder guide covers targeting and our AI chatbot builder walkthrough builds a booking assistant block by block.
The format
How to write a one-line-per-step map
Each line is one step: a short name, a colon, the message, then a “>” followed by the buttons. Each button is written as Label=next step, separated by “|”.
Mark the exits
Some steps end the conversation on purpose. Mark a handover to a person with [person], a step that collects a phone number or email with [form], and a natural finish with [end]. Everything else must have buttons.
Start at the top
The first line is where the chat begins. The checker counts taps from there.
Keep names simple
Use short lowercase names like prices, delivery or book. Typos in names are the most common cause of broken buttons, which is exactly what the checker catches.
Free tool
Check your bot map
Paste your map or load the example. The checker finds broken buttons, dead ends, unreachable steps, steps with no way to a person, and paths that are too deep or too wide.
Write your bot’s map, one step per line: step: message > Button=next step | Button=next step. Mark steps that reach a person with [person], a contact form with [form], and a natural finish with [end]. The first line is where the chat starts.
Runs only in your browser; nothing is sent or saved.
The five problems
What each problem means and how to fix it
Broken buttons
The button points to a step that doesn’t exist, usually after a rename. Fix the name or create the step.
Dead ends
The bot says something and stops, with no buttons and no exit. Add “Anything else?” with Back and Talk to a person.
Unreachable steps
A step no button leads to. In the example, “refund” is written but never linked. Either link it from the start menu or delete it.
No way to a person
From some steps a visitor can only go round in circles. The example’s “compare” step is also a dead end, so anyone checking plans can never ask a question. Every path should reach a person or a contact form.
Too deep or too wide
More than three taps to an answer, or more than four buttons on one step, and visitors give up. Merge steps or move rare options under “Something else”.
Starter shapes
Three map shapes for a free chatbot builder
Most small-business bots fit one of three shapes. Pick the closest, write it as a map and adapt it.
The menu
A start step with three or four buttons (prices, delivery, hours, something else), each leading to a short answer with Back and Talk to a person. Best for shops and clinics with a few repeated questions. Keep it two taps deep.
The funnel
A start step that asks one qualifying question (“Is this for home or business?”), then one more, then a [form] step that collects a phone number. Best for services where every enquiry ends in a call. Keep it to three questions.
The router
A start step that sorts visitors by need (sales, support, billing) and hands each to the right person with a [person] step. Best for teams where different people answer different topics.
Whichever shape you pick, run it through the checker each time you edit it in your free chatbot builder. Most bugs appear on the second or third edit, not the first, because that’s when steps get renamed and buttons get moved.
Before you publish
Test the map with three real questions
A clean map isn’t the same as a useful one. Take three questions customers really asked last week and walk them through the map by hand. Does each one reach the right answer in three taps or fewer? If a common question needs “Something else” and a person every time, it deserves its own button.
Then test the exits during opening hours and after them. A [person] step at 11pm should collect contact details rather than promise a reply in minutes. In LiveChatBot, opening hours switch the widget to an away form that collects an email or phone number, so out-of-hours handovers don’t vanish. Our opening hours guide explains the setup.
Where LiveChatBot fits
Buttons, typed questions or both
Every free chatbot builder makes a different trade-off. Button trees are predictable but rigid: visitors can only ask what you anticipated. Bots that answer typed questions handle more wording but need good knowledge behind them.
LiveChatBot takes the second route. The AI Agent answers typed questions from the knowledge you give it, with a small free monthly allowance per website, and the free keyword bot answers from your saved replies when AI isn’t available. Flows start conversations proactively, with up to six conditions such as page, source and number of visits. Widget cards add tap-to-open buttons for WhatsApp, call, email or a link.
The map is still worth writing. Its steps become your saved replies and knowledge, its exits become your handover and away form, and its first line becomes your welcome message. See Flows for the proactive side.
Frequently asked questions
Do I need to map a bot if my free chatbot builder is visual?
Yes. Visual builders show one block at a time, so broken links and dead ends are easy to miss. A text map shows the whole bot at once.
How many buttons should one step have?
Four or fewer. More than that wraps awkwardly on a phone and slows visitors down. Put rare options under “Something else”.
What counts as an exit?
A handover to a person, a step that collects contact details, or a natural finish such as a confirmed booking. Every other step needs buttons.
How deep should a bot go?
Three taps to an answer is a good limit. Deeper paths lose most visitors on the way.
Does the checker work for any builder?
Yes. It checks the logic of your map, not a particular tool. It runs only in your browser and nothing is sent or saved.
Map it, check it, then build it
Turn your map into saved replies, knowledge for the AI Agent and a welcome Flow, with an away form for out-of-hours handovers. Start free on livechatbot.in.