Skip to content

Build a chatbot flow

Create a no-code chatbot in RetroChat: messages, quick-reply questions, typed answers, forms, conditions, AI answers and hand-offs to your team.

A flow is the conversation your chatbot has with visitors. You build it from steps in the dashboard under Chatbot, with no code.

Create a flow

  1. Open Chatbot and click New flow.
  2. Start from a template (Welcome & triage, Lead capture or Contact form), start blank, or import a file. See Import and export flows.
  3. Add and connect steps. Every step says where the visitor goes next.
  4. Press Test and talk to your flow exactly as a visitor would.
  5. Activate it. Only one flow is active at a time, and activating one switches the others off.

The builder shows a map of the whole conversation. It also warns you about problems, such as a step that leads nowhere or a question with no answer path.

The steps

Step What it does
Message Shows a message, then moves straight on.
Question Asks something and waits for an answer, saved to a variable.
Form Asks several questions at once. The visitor fills in one form and sends it, then the flow carries on.
Condition Checks variables with IF/ELSE rules and picks a path. Visitors never see it.
AI answer Lets the AI answer the visitor's questions from your knowledge base (Business and Autopilot plans).
Hand off Brings in a person. The chat moves to Waiting in your inbox.
End Says goodbye and ends the bot's part of the chat.

Questions

A question can take an answer in five ways:

  • Choice: quick-reply buttons. Each button can lead to a different step.
  • Text: a free-text answer.
  • Email: the format is checked, and the email is saved to the contact.
  • Phone: saved to the contact.
  • Number: handy for team size, budget or quantity, which you can compare in conditions.

Every answer is saved to the variable you name, such as topic, team_size or email. Answers saved to name, email or phone also fill in the contact's profile.

Forms

A form step asks for several details in one go, instead of one question at a time. It suits contact details and project or support requests, where visitors would rather type everything at once.

A form can have up to 10 fields. For each one, choose:

  • A label, such as "Company" or "What can we help with?".
  • A type: short text, long text, email, phone, number, or a dropdown of choices.
  • Required or optional. Optional fields are marked "(optional)" for the visitor.
  • The variable the answer is saved to. It's filled in from the label, and you can change it.

The widget checks the answers before sending: required fields, a valid email or phone number, a number where you asked for one. Details the visitor already gave, such as their name and email, are filled in for them.

When the visitor sends the form:

  • Every answer is saved to its variable, so conditions and messages can use it. Answers saved to name, email or phone fill in the contact.
  • Your team sees the answers as one message in the chat, and under Collected by the chatbot on the contact.
  • The flow continues to the next step: a condition, a hand-off to your team, an AI answer or anything else.

If the visitor types a message instead, the form is shown again. Talk to a person still works at any time.

The Contact form template is a ready-made example: one form for name, email, company, topic and a message, then a hand-off to your team.

Use answers in messages

Put a variable in double curly brackets and RetroChat fills it in:

Thanks, {{name}}! We'll send the quote to {{email}}.

Conditions

A condition step checks its rules in order. The first rule that matches decides where the visitor goes. If none match, the visitor takes the else path. See Variables and conditions for every rule and the built-in variables, such as whether anyone on your team is online.

Hand off to a person

A hand-off step moves the chat to Waiting and notifies your team. If nobody is online, RetroChat asks the visitor for their email, so you can reply later. See Office hours and offline chats.

Visitors can also press Talk to a person at any time, even in the middle of a flow. You can rename or hide that button under Widget.

Tips for flows that people finish

  • Keep it short. Three to five questions is plenty. Ask only what changes what happens next.
  • Prefer buttons to typing. Buttons are faster to answer and easier to branch on.
  • Use a form for details that belong together, like contact details or a project brief. Keep it to the fields you really need.
  • Say why you're asking for an email, for example "so we can send your quote".
  • Always offer a way out. Add a "Talk to a person" choice where it helps.
  • Test every branch. Use Test with different answers before you activate.

Example

The Northwind Hours sample flow shows:

  • a quick-reply menu;
  • a team-size question;
  • a condition that sends big teams to sales;
  • an AI answer step;
  • an "is anyone online?" check before the hand-off.

You can import it as-is and adapt it.