Journeys
A visual, branching automation builder — for flows a simple sequence can't express.
A Journey is a flowchart you build once: a trigger that starts it, messages it sends, waits in between, and branches based on what the contact does (or what your data says). SalesByte runs it for every contact who enters, forever, until you turn it off.
Journeys requires the Growth plan or above.
Example: a cart-abandonment follow-up that stops early for anyone who already bought:
- Trigger: A Shopify cart is abandoned
- Wait 1 hour
- Send: "Still thinking it over? Here's 10% off."
- Check cart status → already bought? skip to End. Still abandoned? continue
- Wait 6 hours
- Send a stronger nudge
- End
Triggers
What can start a journey — tags, fields, WhatsApp replies, Shopify orders, and more.
Steps
Every building block you can drop onto the canvas — sends, waits, branches, and actions.
Journeys vs. Sequences
Both send a series of messages automatically. The difference is branching:
| Sequences | Journeys | |
|---|---|---|
| Messages | One after another, fixed order | Can branch based on replies, tags, filters, or data |
| Channels per flow | One channel | Mix WhatsApp, SMS, RCS, and Email in the same flow |
| Logic | None | If/else conditions, wait-for-reply, product/cart branching |
| Good for | A straightforward nurture drip | Anything with a "then what?" — different paths for different people |
If you're not sure which one you need: start with a Sequence. Reach for a Journey the moment you find yourself wanting "...but only if they clicked the button" or "...unless they already bought."
Key concepts
- Trigger — the one thing that starts the journey for a contact. See Triggers.
- Steps — sends, waits, branches, and contact actions, connected on a canvas. See Steps.
- Runs — one per contact per journey; tracks exactly where that contact is right now.
- Re-entry — by default, a contact already active in a journey isn't enrolled a second time until their current run finishes.
- Test mode — a new journey starts in test mode, so you can walk it through with a test contact before publishing it live.
Publishing
A journey does nothing until you Publish it. Before it lets you, SalesByte checks for the obvious ways it could misfire — like a trigger pointing at a Shopify connection that isn't set up, or a branch with nowhere to go — and tells you exactly what to fix.