Flow Builder

Design structured conversation flows using the Live Bots 365 visual Flow Builder.

Last updated: April 19, 2026
Last updated:

The Flow Builder is a visual, node-based editor that lets you design structured conversation paths for your AI assistant. Instead of relying entirely on AI reasoning to navigate a conversation, you define the exact steps, branches, and outcomes — giving you precise control over how calls progress.

When to Use Flow Builder

Flow Builder is the right choice when your conversation has a predictable structure with defined decision points. Common use cases include:

Appointment booking sequences
Lead qualification scripts
Customer satisfaction surveys
Patient intake processes
Compliance-required call scripts
Multi-step order status checks

Core Concepts in Flow Builder

Nodes

Each step in the conversation is represented as a node. A node defines what the assistant says at that point in the call.

Branches

After each node, you can define multiple branches based on the caller's response. For example, if the caller says 'yes,' go to the booking node; if they say 'no,' go to the follow-up node.

Entry Point

Every flow has a single entry point — the first node the assistant reaches when a call begins.

End Nodes

End nodes mark the conclusion of a conversation path. You can define different end states such as 'Appointment Booked,' 'Not Interested,' or 'Transfer to Agent.'

Tool Nodes

Special nodes that trigger a tool action — such as checking calendar availability or sending an SMS — before continuing to the next step.

Building Your First Flow

1
Open the Flow Builder

From your assistant's configuration page, switch the mode to Flow and click Open Flow Builder.

2
Add your entry node

Drag a Speak node onto the canvas and write the assistant's opening line.

3
Add branches

Connect the entry node to branch nodes based on the expected caller responses.

4
Build each path

Continue adding nodes for each step in the conversation, connecting them with branches.

5
Add tool nodes where needed

Insert tool nodes at points where the assistant needs to take an action, such as checking availability.

6
Define end states

Add end nodes to each terminal path and label them with the outcome.

7
Test the flow

Use the test interface to walk through each path and verify the conversation behaves as expected.