As new paths, questions, integrations, and business rules are added, it becomes increasingly difficult to visualize the chatbot's complete behavior through form-based configuration or config files alone.
Creating service flows for chatbots can quickly become a complex task.
As new paths, questions, integrations, and business rules are added, it becomes increasingly difficult to visualize the chatbot's complete behavior through form-based configuration or config files alone.
The tool's goal is to let any user — technical or not — visually build service flows through a simple, intuitive, and highly interactive interface.
Instead of thinking in code, the user starts thinking in conversation.
Imagine needing to create a flow like:
Mensagem de Boas-vindas
↓
Perguntar Nome
↓
Perguntar Setor
↓
Se Atendimento
→ Transferir Atendimento
Se Suporte
→ Transferir Suporte
Caso contrário
→ Transferir Geral
When this flow is represented only through forms or lists, visualizing it becomes difficult. The user loses context.
Maintenance becomes more complex. And small errors can go unnoticed.
The main proposal of the ChatFlowBuilder Composer is to use a visual, block-based approach.
Each chatbot action is represented by an independent box.
Examples:
The user can see the entire flow just by looking at the canvas.
Beyond the boxes, the connections between them play a fundamental role.
Each connection represents the next step in the conversation.
Example:
Mensagem
↓
Pergunta
↓
Condição
↙ ↓ ↘
A B C
This visualization makes it easier to:
The flow becomes understandable in seconds.
Each block displays important information directly in the interface.
For example:
A question can display:
Qual setor deseja falar?
as well as:
Salvar em: setor
This way the user quickly understands:
This significantly reduces the learning curve.
Clicking on a box opens a dedicated configuration screen.
Each modal has:
The goal is to turn configuration into a guided experience.
When building large flows, small features make a huge difference.
That's why the Composer includes features such as:
Allows quickly duplicating similar components.
Example:
Pergunta Nome
Can be cloned to create:
Pergunta Telefone
with just a few adjustments.
Quick removal of unnecessary components.
Keeping the flow clean and organized.
The flow has a clearly defined entry point.
This makes it easier to:
The user knows exactly where the conversation begins.
Using a flow-based editor brings several advantages:
In many cases, simply observing the flow is enough to spot bottlenecks and opportunities for improvement.