# Make your AI agents predictable.

Product: Flow Builder

Define the critical steps, connect the right actions and plan for exceptions. Test the paths before publishing a flow your team can understand and improve.

This text view is an overview of the Flow Builder page and its published questions. The canonical HTML page contains the native flow example, paths, release controls and deployment illustrations.

## Flow Builder questions.

### How does a flow make an AI agent more predictable?

A flow gives each step a defined purpose, available tools and explicit paths. Your team can see the process, test its branches and review the recorded conversation. That makes behavior easier to control and investigate; it does not make every model response or external system infallible.

### Which decisions are deterministic, and which use an LLM?

A Logic node can evaluate configured rules against variables. Conversation paths can use a model to interpret a customer’s words. Use rules for business decisions with exact criteria, and model-based conditions where intent needs interpretation. Test both, especially when information is missing or ambiguous.

### What happens when a tool cannot complete an action?

Define the required inputs, inspect the returned result and configure what happens when the request cannot be completed. The right response might be another question, a different path or a human handoff. Do not treat an attempted tool call as a confirmed booking, payment or update.

### Can a person take over when the flow reaches its limit?

Yes. For a live phone call, use a configured transfer tool and the correct destination. Make the escalation condition part of the flow, then test availability, unanswered calls and the customer experience. Handoff behavior depends on the channel and transfer setup.

### How should we test a flow before customers use it?

Try expected requests, unclear intent, missing details and unavailable services in the editor. Inspect the chosen path and available tool records. Then test the assigned assistant on the actual phone or website channel. An editor conversation alone does not verify audio, routing, embedding or every external action.

### Can we change or restore a published flow?

Work on the draft, review the changes and publish when your team is ready to update the live flow. Version History can restore an earlier design to the editor. Review and publish that restored design as needed; restoring an editor version is not the same as confirming a live rollback.

### Can we use the flow on both calls and website chat?

Publish the flow, then select it in the assistant’s LLM settings. For calls, connect that assistant to the intended phone configuration. For website chat, connect it to the widget. Validate each channel separately: voice transfers, audio and website interactions do not have identical requirements.

[Talk to sales](https://www.assistable.ai/contact)

Source: https://www.assistable.ai/solutions/flow-builder