OleonSubflows, and references between them.
A flow can call another flow. The alternative is one canvas the size of a wall, which is how a bot becomes unmaintainable.
Chatbot flow builder
Draw the conversation, then publish it.
A flow builder that cannot be read at a glance becomes a thing one person understands and nobody dares change. So the useful features are not the nodes. They are the ones that keep a flow legible after it has grown to two hundred steps.
A map of the whole bot.
Jump by outline, search inside a flow, and see the shape of the thing rather than the corner of it you are standing in.
Every publish is kept.
A published flow is a version, and the old ones stay. Changing a live bot is reversible, which is the only condition under which anyone changes it willingly.
A guard on the live flow.
The version answering customers cannot be edited out from under itself by someone experimenting in another tab.
Tech specs
Every one of these is a screen in the product.
- Nodes, options, branches
- Subflows
- Reference another flow
- A map of the whole bot
- Jump by outline
- Search inside a flow
- Media inside a step
- Every publish is kept
- A guard on the live flow
- Label a contact by reaching a step
Questions
Before you ask.
The ones we hear most about Chatbot flow builder. If yours is not here, the answer is a message away.
Do I need to write code?
No. A flow is nodes, options and branches on a canvas.
Can a flow hand over to the AI agent?
Yes. Flows and the agent are two ways of answering the same conversation, and a step can pass it on.
What happens to a customer who is mid-flow when we publish a change?
Publishes are versioned and the live flow is guarded, so a conversation in progress is not rewritten underneath the person having it.
Keep exploring.
More of what Oleon does.
All solutionsIt starts with one conversation.
Bring the channels you already answer on into one place, and see what the rest of the week looks like.
Not ready to sign up? Join the waitlist and we will come to you.
