📊 Flowchart: Ready Replies

The ‘📊 Flowchart’ button opens a visual editor that shows how ready replies connect to each other in a scenario.

This is not a setting for an individual reply, but a top-down view of the entire dialogue: which reply follows which, where branching occurs, and where the client goes after clicking a button.

---

What this button does

When you click ‘📊 Flowchart’, a visual diagram appears, consisting of blocks and arrows.

Each block represents a separate ready reply. The arrows indicate where the client goes after clicking a button or sending a message.

This helps to see the logic of the scenario as a whole and to notice where a branch ends or loops.

---

Why this is important for business

When there are more than 5–10 ready replies, it becomes difficult to keep all the logic in mind.

The flowchart helps to:

• see how the client navigates through the scenario;
• identify dead-end branches;
• understand where to add the next step;
• check that there is an exit from any reply;
• present the scenario to a colleague or business owner without explanations.

---

When to use it

• Complex support scenarios: first a question → then a clarification → then a reply or handover to a person.
• Sales funnel: message → button → next step → application or consultation.
• FAQ with branching: if the answer to a question depends on what the client selected.
• Logic check: before launching a new scenario.
• Team training: to show in the flowchart how the dialogue with the client works.

---

How to use it step-by-step

1. Open the ready reply that is part of the scenario.
2. Click ‘📊 Flowchart’.
3. Study the diagram: which replies are connected, where the forks are.
4. If necessary, go back to editing and add missing links.
5. Open the flowchart again and check that the logic has become clearer.

---

Example

An online store is creating a support scenario. Through the flowchart, it is visible:

“Greeting” → “What are you looking for?” → if “Delivery” → reply about deadlines and regions → if “I want to order” → application collection.

In the flowchart, it immediately becomes clear that after the reply about delivery, the client returns to the menu but cannot immediately place an order. A “Order” button is added — and the funnel is closed.

---

Important nuances

• The flowchart shows only related ready replies — if a reply leads nowhere, it will be a separate block.
• A complex flowchart is often a sign that the scenario is better broken into parts.
• Do not try to cram everything into one scenario — sometimes it’s easier to create several separate ones.

---

Related features

• Ready Replies
• Buttons for Ready Replies: Overview

Main point

The ‘📊 Flowchart’ is a look at the entire scenario. It helps to avoid getting lost in connections and to spot issues before the scenario goes to clients.