Skip to main content
katerina_nemcova
Helper ⭐️
January 11, 2021
New Idea

Journey Orchestrator - trigger per account, not participant

  • January 11, 2021
  • 11 replies
  • 181 views

Hi All,

 

A quick question regarding JO - we use it for auto-renewing our low-touch accounts where the program is fairly simple:

- bring in participants (billing contacts) who have now failed to renew, send them final 30 days notification - then wait for 30 days - check if they have renewed in the last 30 days, if still overdue, send an internal Termination notice to start the suspension process.  

 

The termination notice goes to our Internal team  - the issue being that more often than not, we have multiple billing contacts on file and so when one account fails to renew, there are multiple/duplicate termination notices being generated - one per each billing contact rather than per account ( albeit they all are sent to an internal email address). 

 

Is there a way to ensure only one termination email is sent out per account rather than per participant? I know the program journey is tracked per participant so I guess there isn't  a way to do this but it would be really useful functionality.

 

Thanks

 

Katerina 

    11 replies

    alizee
    VIP ⭐️⭐️⭐️⭐️⭐️
    February 22, 2023

    100% on all of this.

    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.