What nodes does it generate?

It builds a greeting node, one node per user intent, a fallback node for unrecognised input, and an escalation node for handing off to a human. Together these cover the core structure of any task-oriented bot.

Does it build a working chatbot?

No — it designs the conversation flow and writes a prompt for each node's response. You take those prompts into your AI tool or bot platform to generate and wire up the actual replies.

How many intents should I add?

Start with your three to six most common user requests. Covering the top intents resolves the majority of conversations; rarer ones can fall through to the fallback and escalation paths.

Is my flow data sent anywhere?

No. The designer runs locally in your browser. Your bot purpose, intents and escalation triggers are never uploaded or stored.

Chatbot Conversation Flow Designer

Chatbot conversation flow designer

Good chatbots are not one big prompt — they are a small set of well-defined nodes that route the user to the right answer or to a human. This tool helps you map that flow. Enter your bot’s purpose, the intents users will arrive with, and the triggers that should escalate, and it produces a dialogue tree with a ready-to-use AI prompt for every node.

How it works

The designer turns your inputs into the standard structure every task-oriented bot needs:

A greeting node that states what the bot does and offers your intents as quick replies.
An intent node per user request that confirms understanding, asks the one clarifying question that matters, and sets expectations.
A fallback node for when the bot does not understand, which apologises and offers a rephrase or a human.
An escalation node that hands off cleanly to a person when your triggers fire, summarising what has been collected.

Each node carries its own prompt, anchored to your bot’s purpose, so the responses you generate stay consistent across the whole conversation.

Tips and examples

Write the purpose as a concrete job — “help customers track orders and start returns” beats “customer support” — because it flows into every node. Keep intent names in the user’s words (“track my order”, not “order_status_lookup”), since those double as the quick-reply labels. Pay special attention to the escalation node: the fastest way to lose trust is a bot that traps a frustrated user, so list explicit triggers like “asks for a human” or “refund over £100” and let the flow hand off gracefully. Generate the responses, then test them against real example messages before you ship.