As we begin to go live with many different campaigns being sent out of Journey Orchestrator -- we have become increasingly concerned with inundating our customers with email touch points without even knowing it. With multiple programs running in parallel for different purposes -- we are worried that numerous automated campaigns may have the same individual kicked into them at once when they meet the campaign's conditions to begin.
It would be nice to have some sort of logic built into the system that recognizes "Bob has received emails from the 'Renewals' and 'Feature Adoption' programs today -- let's hold off on sending anymore to Bob until tomorrow even if he has emails queued up and ready to be sent to him today"
"Fatigue Control" Logic Built into Journey Orchestrator
None
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
I haven't explicitly tested this exact scenario, but you could add as part of your bionic query a check against the email logs object to only include contacts where the most recent automated email from specific program types was sent more than X number of days ago.
Our future - we will be building a Bionic Rule to calculate total sends per contact from Gainsight, Marketo, and other sources and populate an MDA table to use. We'll then upsert that back to the SFDC Contact record so that our other email sends outside of Gainsight can fitler off the same numeric value.