So - the goal is to send to one contact on the account but it doesn't matter which contact? 


What is the reason for failure - incorrect or out-of-date information, bounce-list, blacklist? Is there a way to exclude these.


How do you have Entry Criteria set? Are participates allowed to re-enter? And is there a Sync schedule for participants?


I'm not sure if this is possible and I don't have a use-case myself, but would be interested to see the expected behavior if you set participants to re-enter after drop and then sync daily or something if that would pull a fresh list or just the same contacts again and again. 

---

Hi Dale, depending on the importance of the notification, I'd guess this might be a use case where you'd want the customer to designate a specific contact to receive this notification so that it went to the person in their company best suited to take any necessary action. They may even want to assign this to a distribution list email address so that it goes to multiple people. 





If that's the case, it might make sense to create a field on the Account object to store the 'designated email contact' and then use that in your program. Would this work?

---

Great questions and suggestions.  I'll go through in order





John,


It will matter which contact but at the moment it only matters that we deliver the data to one contact per account.  This is a new process and we are making adjustments each month based on customer feedback.


The majority of failure reasons are bounce-list and missing token.  This gave me ideas.


At the moment we do not have participants re-entering or a sync schedule because we are still fine-tuning the program each month.


I did some testing on participants re-entering and it appears that as long as the query and contact data remains unchanged, the same participant is selected each time.





Ideas: Assuming this can be done, I'm going to try to merge contacts with the bounce list in the query builder next time around.  That should prevent pulling contacts who would fail for that reason after passing the uniqueness criteria.  MIght be nice to have a built-in bounce-list pre-filter feature in programs.  I will also be looking at removing old entries from the bounce-list to keep it fresh.





Dan,


Fantastic suggestion and yes our ultimate goal is to identify the right person or persons to receive the report.  The target account list changes each month and we have several contact fields we can leverage for identifying who gets it and adjust based on customer feedback.





Ideas: Add a Gainsight Communication Type multi-picklist on the contact object for this and other initiatives.


Bonus idea - add a Gainsight Opt-in checkbox for general cases.





Thanks for the great feedback

---

For missing token - can you adjust the outreach/program to allow the email to go through even if tokenized field is null. We do this occasionally when we need to send an important operational email since the message is more important than making sure we have their first name for example. I think the box is checked by default on outreaches so you have to uncheck. 

---