Opens already tidy
New journeys start with the nodes aligned. One click tidies a canvas that has grown.
TriggerWaitSplitGoal
Journeys
Build the path once. Let it run.
Automated, multi-step customer paths on a visual canvas that checks itself before launch.
Same customer profiles everywhereA person approves every sendWorks inside your rules
Cart recovery · journeyDraft
ValidTriggerAdded to cart0
ValidWait1 hour0
ValidSplitBought yet?0
ValidNo · WhatsAppReminder + offer0
ValidYes · ExitOrder placed0
ValidGoalOrder placed within 7 days
No goal set. This journey can never end.
Step 1 of 3
Drag the tiles
Trigger, wait, split, message. Each tile snaps onto the canvas.
What the canvas can do
Six things a journey does for you
Everything below runs on the same profiles and segments as your campaigns, so a path never works from a stale list.
Splits and conditions
Branch on events and profile attributes, then merge or exit each path.
Added to cartBought?Yes: exit
Waits and time windows
Wait a set time, or hold messages until the hours you allow.
Send 9:00 to 21:00
0:0012:0024:00
Any channel on any step
Email, SMS, WhatsApp, RCS, push or in-app, chosen per step.
EmailSMSWhatsAppRCSPushIn-app
Goals that end the path
When someone reaches the goal, they leave the journey and stop receiving its messages.
ReminderGoal reached: exit
Validate before go-live
The canvas lists every problem it finds. A journey with errors cannot launch.
Trigger setOK
Goal missingFix
Anatomy of a journey
Click any step to see what it does
Cart recovery5 nodes
Trigger
How people enter the path
- What it does
- You set
- Checked by
Validate reads every node before this journey can go live.
Journey vs Campaign
Pick the right tool for the send
Both use the same segments, templates and channels. They differ in how long the conversation runs.
Journey
Campaign
Best for
Paths over days or weeks
One-off or scheduled sends
Starts
On an event or segment entry
At a date and time you pick
Steps
Waits, splits, many messages
One message per audience
Ends
At a goal
After the send
Use cases
Paths teams build first
Welcome series
Greet a new signup, then introduce the product over the first week.
SignupEmailWait 2d
Abandoned cart
Remind after an hour, stop the moment they buy.
CartWait 1hWhatsApp
Win-back
Reach people who have gone quiet, with an offer worth opening.
Inactive 30dEmailPush
Onboarding
Nudge each person toward the step they have not completed.
SignupSplitIn-app
Payment reminders
Send before the due date and again after, within allowed hours.
Due in 3dSMSWindow
Festival offers
Time a themed offer to a segment, across the channels they use.
SegmentRCSEmail
FoxAI assists
Help on the canvas, a person decides
Draft from a goal
Describe the outcome and get a first journey to edit.
Best channel and time
Suggestions per step, based on how each person responds.
Validate
Plain-language fixes for each problem found.
Insights
See where people leave and which step carries the result.
Best practices
Six habits of journeys that work
Open each one, then mark it done. The readiness panel keeps count.
How in Flowfox
Pick the one event that means success, such as order placed, and set how long to wait for it.
How in Flowfox
Start with a trigger, one wait, one split and one message. Add steps only when results ask for them.
How in Flowfox
Add a time window to any wait that is followed by a message, such as 9:00 to 21:00.
How in Flowfox
Name nodes after what they do, for example Reminder or WhatsApp, rather than Node 4.
How in Flowfox
Open Validate, resolve each item, then run it again until it reports no errors.
How in Flowfox
Check step-level numbers in Analytics after a few days, then adjust one thing at a time.
Help Center
Guides to get a journey live
Help
Build your first journey
From trigger to go-live, step by step.
6 min readHelp
Goals and waits
Make sure people exit when they should.
5 min readHelp
Send your first campaign
For one-off sends, start here.
4 min readHelp
Set sending hours with time windows
Hold messages until the hours you allow.
3 min readHelp
Fix problems found by Validate
What each check means and how to resolve it.
5 min readHelp
Branch with splits and conditions
Route people by events and attributes.
6 min readHelp
Pick a channel for each step
Email, SMS, WhatsApp, RCS, push and in-app.
4 min readFrom the blog
Playbooks for lifecycle journeys
Blog
Welcome series that people finish
Ideas for the first week after signup.
Playbook · 7 minBlog
Abandoned cart: when to remind and when to stop
Timing, channels and exit rules.
Playbook · 6 minBlog
Win-back journeys, step by step
Reach people who have gone quiet.
Guide · 8 minBlog
Why every journey needs a goal
Ending a path is part of designing it.
Opinion · 4 minBlog
Onboarding paths by what is not yet done
Nudge toward the next step.
Guide · 6 minBlog
Journeys or campaigns? A quick way to choose
A short decision guide.
Guide · 3 minQuick answers
Common questions about Journeys
How many channels can one journey use?
Any connected channel on any step: email, SMS, WhatsApp, RCS, push, in-app and web.
Can people be in more than one journey?
Yes. Frequency caps keep the total volume sensible.
What happens when someone reaches the goal?
They leave the journey and receive nothing more.
Are journeys included in the starting plan?
Yes, in both plans.
Questions about Journeys?Editing live journeys, limits and setup are covered in the FAQs.
Read the FAQs