Flows that reach the right person.
Build lifecycle journeys on a visual canvas — triggers, branches, waits, sends. Enter people from any event or segment, split on what you know about them, and send on the channel they prefer.
A canvas that stays structured.
Journeys read top-to-bottom, like the logic they encode. No spaghetti graphs — every step is explicit, every branch is readable, and publish is a deliberate act with versions you can roll back.
Start from any signal
Track events, form submissions, segment entry, schedule — anything your sources emit can open a journey for exactly the right person.
Branches, waits, sends
Condition splits on traits and behavior, timed and event-based waits, and message steps that render your own templates per channel.
Consent and quiet hours
Delivery respects each profile's consent and your quiet-hour windows by default. The journey decides what; the guardrails decide whether and when.
Every message, in their words.
Merge any trait or event into your templates — first name, plan, the last thing they looked at — and preview exactly what each person sees before it sends. One journey, thousands of personal messages, with missing values caught before they reach a real inbox.
Amara's flow below is an illustrative walkthrough, not a customer case study.
Every run, on the record.
Activity and version history live inside the builder — see who entered, what each step did, and which published version made the call. When something looks off, you read the run, not the logs.
How versioning works
journeys-personThe people who own the lifecycle.
Journeys is for the marketer who's tired of filing a ticket to send a message — and the engineer who's tired of the tickets. Design the flow, watch exactly who it touched, and change it without a deploy.
Build your first journey in an afternoon.
Runs in our cloud or your VPC · SOC 2 Type II in progress