Flows

A flow is the path a task follows: its stages (for example Booked → In the chair → Done), the details filled in at each one, the buttons that move it and the notices to the customer or the team. What you sell lives in the catalog (services, products and plans); each service picks a flow, and several services can share the same one. Each task copies its service's flow when it is created and moves through its stages.

Not to be confused with Rules, which do things on their own when something happens.

Flows live in My business → Flows. Owners and Managers can see them; editing is for the Owner.

Build a flow

1. In Flows, tap New flow (it starts from the simple flow of the mode you choose) or open one and tap Duplicate: the copy is independent.
2. Add or rename stages with + Add stage. The Timing says where each one falls: Before service, In service or Final.
3. In each stage, + Add data (text, number, yes/no, options, date, photo, signature, checklist…) and choose Visible to: Team, Customer or Both.
4. Add button to another stage to set how the task moves on: the destination, who taps it and which details it requires.
5. Try it with ▶ Test flow (see Test a flow) and tap Save.

System flows cannot be edited: duplicate one to build your own.

One flow for several services

In the service, Edit → Flow shows the flow it uses and lets you pick another one of the same mode. If haircuts and haircut + beard are handled the same way, give them the same flow: you build it once and it changes for all of them.

• Picking another flow for a service only changes new tasks; open ones keep theirs.
• Saving a shared flow publishes a new version for all its services. Before you confirm, you see which services use it and how many open tasks move in each one.

The bot asks the customer for what is missing

If a task's stage has details or buttons seen by the Customer, and the task was created in the chat, the bot asks for them in the same conversation, one at a time, and moves the task once they are complete. For example, a "Reference photo" stage: the customer books a haircut, the bot asks for the photo, saves it to the task and moves it to the next stage. The team sees it in Today and charges it as usual.

• If the customer asks something else halfway, the bot answers and then comes back: "Shall we continue with your …?".
• The bot never taps team buttons, never charges or sets amounts, and never cancels without a YES from the customer.
• 24 hours after the task entered the stage, the bot stops asking and the team takes over.
• The photo is requested on WhatsApp and Instagram. On Telegram and the website chat, the bot says that detail is completed with the team. The signature is always completed with the team.

Wagy and flows

Ask Wagy "which flow does the haircut use?" or "what steps does the color flow have?": it shows the stages and which services use it. It can also assign a flow to one or more services, rename one of your flows and add, remove or move stages, always with a plan you confirm. Creating flows and editing details, buttons or notices is done in the panel.

For developers

Flows are read and published through the API (/v1/flows) and MCP (list_flows, get_flow); a service's flow is its flow_id. See Endpoints.