Draw the conversation the way you want it to go
AI answers open questions. What must happen in a fixed order — taking an order, booking an appointment, collecting an address — needs a drawn path nobody improvises on. The visual builder is that path.
- Buttons and menus
- Keeps the customer's answers
- Hands over to the AI
When AI alone is not enough
AI is excellent at answering and unsuited to cases where the order itself is the requirement. Collecting an address before a name, confirming quantity before price, skipping a mandatory question — none of these shows up in a single answer; they show up as an incomplete order reaching you. A drawn path makes the order a property of the build rather than a plea in the instructions.
How you build one
Start from the trigger
A word the customer types, a button tap, or their arriving from a particular ad or QR code.
Place the steps
A message, an image, buttons, a question whose answer is kept, a condition that splits the path — by dragging.
Wire the endings
Write the order to a sheet or your store, hand over to a person, or pass to the AI to continue freely.
Preview, then publish
Run the flow on yourself first. Most mistakes show up on the first attempt, not in review.
What you can put in a flow
Buttons and menus
Buttons end ambiguity: the customer taps instead of typing, so no dialect or misspelling gets in the way.
Questions whose answers are kept
Name, address and order number are kept on the conversation, then used in later messages and in your sheet.
Forms inside the conversation
Collect the customer's details one question at a time instead of a form on a page they must leave for. The answers are kept on the conversation and written to your store or sheet.
Conditions that split the path
Inside the city or outside, returning customer or new — each goes their own way without an extra message.
Handover to the AI
When the customer steps off the path with a free question, the AI agent takes over, answers from your knowledge, and returns them.
Handover to a person
On a condition or a button, pausing automation until the conversation ends, so two voices never answer one customer.
A flow versus AI alone
| AI alone | ArabyBot | |
|---|---|---|
| An open question about price | Excellent | Hands it to the AI |
| A fixed order for taking an order | May skip a question | The order is built in |
| A mandatory field | A plea in the instructions | It does not proceed without it |
| Buttons instead of typing | No | Yes, which ends the dialect problem |
Questions people actually ask
Flow or AI?
Both, each in its place. The flow is for anything with a fixed order — an order, a booking, collecting details. The AI is for the open questions: a price, a policy, a size. The customer moves between them inside one conversation.
Does it work on every channel?
It works on WhatsApp, Messenger and Instagram. Button shapes differ slightly by what each channel allows, and the preview shows you the difference.
Can I edit a flow that is live?
Yes, and the change applies to new conversations. Ones already running finish on the version they started with.
Draw your first flow in minutes
By dragging · preview before publishing · handover to the AI and to a person
Start free