Key Concepts
How a Contact Moves Through a Journey
- Enter. A record is written to a custom data table, a contact joins a segment, your system enrolls them through the API, or someone adds them from the dashboard.
- Plan. Journeys works out the next call or text that is allowed, and when.
- Reach out. When it is due, every rule is checked again, and then the call is placed or the text is sent.
- Listen. An answered or missed call, a reply, or a change to the record leads to a fresh plan.
- Move on or finish. The contact moves to a later stage when its conditions hold. The journey ends for them when the goal is met, they opt out, the limits are used, or nothing is left to send.
An Example
An appointment confirmation journey:- Way in: each new row in an
appointmentstable, timed from itsappointment_time. - Goal: the row’s
statusis Confirmed. - Confirm stage:
- A call the day before at 10 AM, with two attempts.
- A text two hours later if the call was not answered.
- A call the morning of the appointment.
- Reschedule stage: entered when the customer replies asking to reschedule, with a call from a rescheduling agent.
Playbook and Guided Modes
In both modes the timing rules, calling hours and limits are the same. Guided mode only chooses among the calls and texts that are already allowed.