PulseJourneys
Drawn once. Running on its own. Welcome series, follow-ups, re-engagement: all as a canvas you can read, with a log that explains every contact's path.
Draw what should happen. In five kinds of step.
A journey is a canvas: steps and the lines between them. Small on purpose, because a welcome series is not a programming language, and yes/no is how humans actually branch.
- Five kinds of step: start, send, wait, branch, end
- Branches ask a yes/no question about the person
- The canvas stays exactly as you arranged it
- Enter by hand, in bulk from a list, or on a named event
- Draft until activated: nobody gets a half-built series
Then read any journey back. Person by person.
Every enrolment keeps a log that only adds to itself: what happened, when, and why. The question “why did they get that email?” always has an answer.
- One active enrolment per person per journey
- Re-enrolment only after the last run finished
- Every step logged: succeeded, failed, skipped, waiting
- Emails go out through the same machinery as campaigns: unsubscribe included
- Opt-in re-checked at every send, not just at entry
Automation with manners. The rules that keep a journey trustworthy.
One at a time, per person
A contact holds one active enrolment per journey: the welcome series cannot double-send because someone clicked twice.
Traceable, contact by contact
The log only ever adds, never rewrites: which step, when, what happened. “Why did Amara get that email?” has a factual answer.
Consent gates every send
The opt-in check runs at each send-email step. Someone who unsubscribes mid-journey stops receiving; the journey carries on without mailing them.
Waits that keep their word
A wait schedules the next step to the minute and survives restarts: three days means three days, not “whenever the server remembered”.
Draw your welcome series. The beta is open now.
Three ways: enrol someone by hand, enrol a whole list in one action, or start people automatically when a named event fires on your site (a signup, a purchase), with a cooldown or a once-only rule per journey. One thing to know: joining a list does not start a journey on its own yet. Your welcome series will not fire by itself when someone subscribes: you run the bulk enrolment for that list, or trigger on a named event instead.
A yes/no question over the same conditions audiences use: fields on the contact, and behaviour like opened, clicked or visited. True goes down one edge, false down the other.
Today: wait, branch, and send email. That’s the honest list. A journey cannot tag someone, update a field on their record, or notify another system yet. Automation that writes to the record itself lives in Reach, not here.
The step is logged as failed and retried; after repeated failures the enrolment is marked failed rather than looping forever. Failures are rows you can read, not silence.
Only after their previous run ends: one active enrolment per person per journey. Event-triggered journeys add a cooldown, or once-only, so a repeat signup doesn’t restart the welcome.