Skip to main content

Going Live — Publishing and Managing Journeys

You've built your journey. Now let's get it running — and learn how to safely make changes once it's live.

Publishing Your Journey​

When your draft is ready:

  1. Click Publish Changes in the journey builder toolbar
  2. Your draft becomes the live version
  3. The entry trigger activates — contacts start flowing in
  4. The journey is now running on autopilot

That's it. Your automation is live.

The Draft/Publish Model​

Score CRM uses a safety-first approach: you always edit a draft, never the live version directly. This means you can tweak a running journey without accidentally disrupting contacts who are mid-flow.

Here's how it works:

DraftPublished
Who sees itOnly you, in the editorLive and processing contacts
Contacts flowingNoYes
Can you edit it?Yes, freelyNo — create a draft first

When you're editing a published journey, you'll see a yellow banner:

"You are editing a draft. The live journey continues to run unchanged."

This means your changes are safe to experiment with — nothing affects live contacts until you hit Publish.

Making Changes to a Live Journey​

  1. Open the journey and click Edit Journey
  2. A draft copy is created automatically
  3. Make your changes
  4. Click Publish Changes to deploy the update
  5. Or click Discard Draft if you change your mind

What Happens to Contacts Already in the Journey?​

  • Contacts already mid-journey continue on the previous version's flow — no disruption
  • New enrollments use the new version
  • This prevents awkward situations like someone receiving a duplicate email because you rearranged steps

Version History​

Every time you publish, Score CRM saves a snapshot. To view past versions:

  1. Go to the journey detail page
  2. Click Version History
  3. See every version with its publish date and who published it

Rolling Back​

If a new version isn't performing well:

  1. Open Version History
  2. Click Revert on the version you want to go back to
  3. A new draft is created from that version
  4. Review it, then publish
info

Reverting creates a new version going forward — it doesn't erase history. Your version timeline always moves forward, so you have a complete audit trail.

Pausing and Resuming​

Sometimes you need to stop a journey temporarily without scrapping it. Use the Pause button in the toolbar.

When paused:

  • Contacts stay exactly where they are (frozen in place)
  • No new contacts are enrolled
  • No emails are sent
  • Delays keep counting — but contacts won't advance until you resume

Click Resume to restart everything from where it left off.

When to pause:

  • You spotted an error and need time to investigate
  • Seasonal break (e.g., pause holiday campaigns in January)
  • You're making a big change and want to be extra careful

Duplicating a Journey​

Click Duplicate in the toolbar to create an exact copy of the journey as a new draft. Great for:

  • Creating a variation to A/B test different approaches
  • Building a similar journey for a different audience
  • Using an existing journey as a template

Enrolling Contacts Manually​

Even with automatic triggers, you can manually add contacts anytime. Click Enroll in the toolbar to:

  • Enroll a specific list of contacts
  • Enroll individual email addresses
  • Great for testing before you publish, or for ad-hoc additions

Journey Lifecycle at a Glance​

New Journey → Draft → Publish → Live
                                  ↓
                           Edit Journey → New Draft → Publish → Updated Live
                                  ↓
                              Pause ↔ Resume
                                  ↓
                              Archive (retire)

Best Practices​

  • Always test first — enroll yourself (or a test contact) before publishing to a real audience
  • Pause before investigating — if something looks wrong, pause the journey first, then diagnose
  • Keep version notes — mentally track what changed between versions so you can compare performance
  • Don't over-publish — plan changes carefully rather than publishing small tweaks constantly
  • Use Duplicate for experiments — instead of editing a working journey, duplicate it and test your idea separately