Skip to navigation

Orchestrate End-to-End Customer Journeys with Journey Builder

journey

Problem: Customer engagement often breaks down when teams juggle separate tools, keep data in silos, and lack visibility into how conversations progress. A reminder goes out in one tool, a follow-up happens in another, and no one can see whether the customer actually converted.

What is Journey: The highest layer. A journey combines messages, automations, and conversational flows into a multi-stage path that follows the customer across their lifecycle. It lets you focus on the business outcome rather than the individual steps, and gives stakeholders a high-level view of where customers progress or drop off.

Journey Builder solves this by bringing every customer touchpoint into a single visual workspace. You can design, automate, and monitor multi-stage journeys across SMS, email, WhatsApp, webchat, and voice, from the first inquiry through to the final business outcome.

What you can build with: key journey elements

Journey Builder’s drag-and-drop canvas gives you the following elements. You can combine them to control when, how, and to whom each step runs.

Conversation blocks

The block panel groups everything you can drop onto the canvas:

  • Active Conversation Blocks: your active use case automations (nurture, reminders, notifications) and conversational flows from My Automations.
  • Popular in {Industry}: ready-to-use automation and flow templates for the industry set in your account settings, for example Popular in Healthcare.
  • Other Conversational Blocks: every other automation available in the Automation Library.

Conditional branching

Send customers down different paths based on:

  • CRM fields: values on the lead or contact record.
  • Context variables: data captured earlier in the journey or session.
  • Business hours: route differently inside and outside your defined hours.

Wait and timing elements

Place these between any two steps to control pacing:

TypeElementWhat it does
Time-basedWait until specific timePauses until a set time, such as 9 AM the next day
Time-basedWait for X hours or daysHolds the journey for a fixed duration
Time-basedWait until business hoursContinues only when agents are available
Event-basedWait until responsePauses until the contact replies
Event-basedWait until status changeContinues when a CRM field updates, such as a lead moving from Pending to Qualified
Event-basedWait until integration eventContinues when a connected system sends an event, such as payment processed
Engagement-basedNo response in X hoursSends a reminder, escalates to a live agent, or nudges on another channel
Engagement-basedEngagement scoreSwitches path based on the contact’s engagement score

Decision elements

  • Response-driven: act on what the customer says. For example, start a screening flow when a candidate replies “I’m interested,” or update the CRM or ATS when they reply “Not interested.”
  • Data validation: continue only when a CRM or ATS field meets a validation rule.

AI interventions and human handoff

AI works alongside your journey to keep conversations on track. It can monitor sentiment and recognize intent, then escalate to a human agent when a customer shows frustration. Every handoff carries the full conversation context, so agents never start from scratch.

Who uses Journey Builder

The low-code builder is designed so non-technical teams can build and change journeys without engineering help.

  • Marketing teams design personalized nurture journeys that raise lead-to-conversion rates.
  • Customer success and patient experience teams automate onboarding, reminders, and follow-ups to reduce churn and no-shows.
  • Operations and IT teams connect journeys to CRM, ATS, EMR, and other systems so data stays in sync without manual follow-up.
  • Business leaders track outcomes across the whole lifecycle rather than individual messages.

Monitor journey performance

Because a journey measures a business outcome, you can see how well it is working, not just whether messages were sent.

  • Real-time insights: follow customer progress through events, outcomes, and sentiment.
  • Drop-off analysis: find the stage where customers abandon the journey.
  • Time to complete: track the average time customers take to finish each journey.

Use these insights to adjust active journeys, such as adding a reminder where drop-offs cluster or switching channels for contacts who don’t respond.