Journeys
Build lifecycle journeys from a simple brief
Sortment creates the journey structure, message steps, timing, branches, and measurement plan, based on your goal, audience, trigger, and channels
No credit card · No migration · One revenue metric moved in 30 days
First 14 Days Onboarding
Draft
Publish
Assistant
Subscription started
Is Push enabled?
Yes
No
Welcome Push
Welcome Email
Reject
Accept
Wait 3 days
Sessions in last 7D
No sessions
Atleast 2
More than 3
'Miss you' SMS
Education tips
Feature teaser
Wait 2 days
Tag 'Promising'
Sortment AI
Create an onboarding journey for new paid subscribers, starting from the moment they subscribe.
Created journey
I’ve created a Day 0–14 onboarding journey focused on first value, habit formation, and early churn prevention.
Any ideas to improve open rates?
Added suggestions to canvas
I’ve added a few suggestions to the canvas for review, including using a light push nudge for users with notifications enabled.
This can increase early visibility during onboarding while keeping email as the primary channel.
Ask or follow up
Journey Capabilities
Built for real lifecycle complexity
Beyond basic drip sequences — branching logic, multi-channel steps, goals, API triggers, and overlap controls, all powered by AI agents.
Track goals and see where the journey drops
Tracks goal completion step by step, flags where users drop off, and surfaces the probable cause.
Email exits are high after repeated subject exposure.
Step
Reached
Exited
Exit Rate
Email · Day 0
2,860
514
18%
Push · Day 2
2,346
621
26%
Goal reached
1,725
—
—
Likely cause: subject line seen 3× in 14 days
Suggested: shorten subject · reduce send delay
No user enters two journeys at once with suppression
Sortment checks every user for active journey enrollment before entry, suppressing conflicts or queuing them automatically.
2,860 users are ready to enter this journey, while 428 users are being held in the re-entry queue after exiting.
Conflicting Journey
Overlap
Resolution
Retention — Winback
340
✓ Suppressed
Onboarding — Day 7
88
✓ Queue after exit
Trial Upgrade
0
—
No user is in two active journeys simultaneously
Branches based on what users do.
Routes users differently based on what they do — opened, clicked, converted, or exited.
No login in 7 days
"We've missed you"
Wait 48 hours
Was the email opened?
All your channels in one workflow
One journey, multiple channels, preference checks and suppression applied at every step.
Step
Channel
Status
1
Sent
2
Push
Sent
3
SMS
Day 5
4
Webhook
Exit
Triggers on events, schedules, or API calls.
Trigger on user actions, schedules, audience changes, journey exits, or API calls. (Confirm API depth with product team.)
User action (event)
Audience enters segment
Schedule
API call
Journey exit event
What one marketer built in a year
BryteBridge scaled a new brand from 2 states to 20 with one lifecycle marketer, no data engineering team, and Sortment.
10x
Revenue, year-over-year
2,000+
Campaigns shipped in 12 months
1
Marketer. No engineers.
The business case
Why lifecycle teams use Journeys
The highest-leverage journeys close a single lifecycle gap — first value, drop-off recovery, or conversion before the window closes.
Guide users to first value
Build onboarding journeys that move new users through the steps that matter before they disengage.
The faster users reach value, the longer they stay.
Signup, no first action
Setup incomplete after day 3
Feature adoption gaps
Recover users before churn
Create journeys that catch usage drops, renewal risks, and inactivity signals before they become lost accounts.
Act before the user stops caring.
7-day login gap
Renewal risk, 30 days out
Dormant high-value accounts
Convert intent into revenue
Launch journeys around trial expiry, upgrade intent, and cart behavior so every conversion window gets a follow-through.
Intent without a journey is a missed opportunity.
Trial-to-paid window
Abandoned checkout
Upgrade signal detected
Start where you are. Go as far as you want.
How teams use Sortment
Add Sortment to Braze, Iterable, or any other ESP without migrating, or use it to replace your CEP entirely.
Pilot with your existing stack
Full CEP replacement
Your warehouse. Your ESP. Sortment sits in between.
Sortment connects to your warehouse and works with your existing ESP, so you can build real-time audiences, AI-created traits, and segments without data team support.
One platform. Every channel. No handoffs.
Sortment replaces your CEP entirely. Journeys, campaigns, segments, content, analytics, and AI agents all run in one platform.
No more coordinating across Asana, Jira, or Slack. No shared resources, no data team tickets, no waiting. Everything your lifecycle team needs to execute, in one place.
SMS
In-app
Push
Webhooks
QUESTIONS?
FAQs
How does Sortment's journey builder differ from traditional drag-and-drop tools?
What kind of journey logic does Sortment support?
Can I edit a journey after Sortment generates it?
How does Sortment prevent users from being in too many journeys at once?
How do I measure whether a journey is working?
Secure & Compliant
Enterprise-grade security for world-class campaigns
AGENTS
CASE STUDIES
RESOURCES