Journeys
Automate follow-ups with triggers, waits, decisions, sends, tags and tasks.
A journey automates a sequence of steps for each person who enters it: for example, thank a new donor, wait two days, then invite them to an event.
Open Messaging › Journeys.
Building a journey#
- Choose a trigger, for example a donation, a sign-up or a tag being added. Decide whether a person may re-enter the journey.
- Add steps. Each step has an ID and points to the next step:
| Step | What it does |
|---|---|
| Wait | A number of minutes, until the next allowed send window, until a fixed time, or until an event happens (with a timeout) |
| Condition | Checks a field and sends the person to a "yes" or "no" step |
| Send | Sends an approved message on any channel |
| Tag | Adds or removes a tag |
| Call list | Adds the person to an active phone-bank call list |
| Task | Creates a task for a staff member |
- Save a draft, then publish. Publishing creates an immutable version.
Versions#
Each person stays on the version that was published when they enrolled. Publishing a new version affects only new entrants, so nobody gets half of one journey and half of another.
Safety#
Every send step uses the same audience rules, suppression, quiet hours, frequency caps, content screen and wallet as a normal send. A person who opts out leaves every journey immediately.
Monitoring#
The journey page shows enrolments, people in flight and people who exited, plus how many visited each step.