Skip to main content
Contributor ⭐️
Oct 19, 2023 1:02 PM UTC
Question

Journey Orchestrator triggered by stage change

I have an onboarding journey that is supposed to “launch” upon a CS Stage Change. We are seeing a delay here. Is there a way to make an onboarding journey (email sequence/JO) trigger at a Stage Change? 

4 replies

dayn.johnson
VIP ⭐️⭐️⭐️⭐️⭐️
Oct 19, 2023 2:35 PM UTC

What’s the delay, @jbaselice? Possibly an overlap of Gainsight syncing with the underlying data?

Translate
Staff CS Content & Comms Manager, 2x Gainsight CS Ops Product Council Member
jbaseliceAuthor
Contributor ⭐️
Oct 19, 2023 4:01 PM UTC

Was told by our consultant that a Stage Change will not trigger a JO in real time. That we have to set the JO to a set time (not real time). I didn’t phrase my question correctly -- I see now. Basically the question is “can a stage change trigger a JO to email in real time or does the JO have to be set on a certain time”

Translate
dayn.johnson
VIP ⭐️⭐️⭐️⭐️⭐️
Oct 19, 2023 4:29 PM UTC

That makes sense… 

Our onboarding (and new mid-cycle user if a company is out of onboarding) programs are based on the user’s first paying login date (to account for users who may have logged in during a PoV).

Translate
Staff CS Content & Comms Manager, 2x Gainsight CS Ops Product Council Member
alizee
VIP ⭐️⭐️⭐️⭐️⭐️
Oct 23, 2023 8:47 AM UTC

@jbaselice You wouldn’t be able to bring in participants in real-time nor to - imagining you’d have your participants waiting in a conditional wait - to trigger the email in real-time since conditional waits have got an 11-hour re-evaluation cycle. And trust me, that 11-hour cycle is a nightmare as it would end up sending emails at weird o’clock. 

The most sensible approach currently will be to schedule your JO to run daily. 

You could envisage creating several clones that run at different times of day to mimic the instant sending (maybe have 4 programs, running every 2 hours from one another which would cover an 8 hour time period). However, that comes with other issues though: it’ll be using up your JO bandwidth and could cause delays on other programs (or other programs cause delays on those). 

Translate
The most expensive part of building is the mistakes. That's true in construction. Not so much in CSOps. So ask questions, make mistakes and learn. All views expressed here are my own.