Skip to content

Build your own

Picking a trigger, adding steps and waits, branching on a condition — and what happens when you edit a flow that's already running.

3 min readUpdated August 15, 2026Managers · Owners

Templates run out at about the third flow. After that you're building the one that's specific to your salon — the follow-up after a treatment that needs aftercare, the nudge before a membership's credits expire.

New flow → Build it myself asks for a name and a trigger, and then hands you an empty editor.

A flow's steps: a condition on whether the client is tagged VIP, a different text down each branch, then a two-day wait and a follow-up text, each with buttons to add a step, a condition or an A/B split after it.
Steps run top to bottom. A condition splits the path; everything below it rejoins.

Adding steps

Two views of the same thing, on the flow's own tabs. Steps is the list — easier to read and to edit. Map is the same journey drawn as a diagram, which is the one to open when a flow has branches and you've lost track of what rejoins where.

  1. 1

    Press Add step and pick what it does. Most are Send text or Send email.

  2. 2

    Write the message. Insert a merge tag drops in the client's name and the details of what triggered the flow, each shown with an example value, and there's a test send at the bottom of the editor.

  3. 3

    Add a Wait between messages. This is the step people leave out, and the reason a flow feels like a machine when they do.

  4. 4

    Use Add condition where the message should differ — one path for clients who match, one for everyone else. Both paths rejoin afterwards.

  5. 5

    Use Add A/B split to test two versions of the same message against each other at random.

  6. 6

    Set the goal on the Details tab, so the flow can tell you whether it worked.

Waits are the design

A flow with no waits is a text arriving the same second the appointment is marked complete, while the client is still paying. The template that thanks people waits two hours for exactly that reason.

Think in the client's time, not the system's. A thank-you a few hours later reads as considerate. Two days later reads as automated. The same message at either end of a wait is a completely different message.

Editing a flow that's already live

The Steps and Map tabs both say it: editing an active flow is safe — changes only reach clients once you publish. Your edits sit as a draft, everyone already in the flow carries on with the published version, and a banner appears offering Publish when there's something unpublished.

The Details tab is stricter. The trigger, the goal and the enrolment filters say Deactivate to edit, because those decide who is in the flow at all — and changing that under the feet of people mid-journey isn't something the product will let you do by accident.

Narrowing who gets enrolled

A trigger enrols everyone it applies to. Enrolment filters on the Details tab narrow that: same conditions the rest of RewireBox uses, so a flow can fire on every completed appointment but only for clients who bought a colour service.

Left empty — which is the default — every client the trigger applies to is enrolled automatically.

Common questions

Can I edit a flow while it's running?

The steps, yes — your edits are a draft until you press Publish, and clients already in the flow carry on with the published version until you do. The trigger, the goal and the enrolment filters need the flow deactivated first, because changing those mid-run would change what everyone in it is doing.

What can a step do besides send a message?

Wait, branch on a condition, split A/B, add or remove a tag, credit a client's balance, grant an offer, send a portal link, create a task for the front desk, call a webhook, or wait for an event to happen.

What's the difference between a condition and an A/B split?

A condition sorts clients by something true about them — tagged VIP, say. An A/B split sorts them at random, so you can compare two versions of the same message fairly.

How do I try it without sending to clients?

Open a message step and use the test send inside it. Leave the flow as a draft while you do — a draft enrols nobody.

Can I get a flow back to how it was?

The Details tab keeps a version history of what was published and when.

Can I start a specific client through a flow?

Enrolments → Enrol client, or Enrol a segment for a group. That's the only way a Manual only flow ever runs.

Related articles

Can’t find what you’re looking for?

Book a 20-minute walkthrough and we’ll answer it on a screen share — or start free and try it on your own salon’s data.