HubSpot Ideas

sarahcocos

Adding 'Don't Send To' lists for Automated Emails

We've had to create custom workaround logic branches within our workflows to achieve our goal but it would be great if Automated Emails could include the 'don't send to' list option, similar to the standard/classic emails.

Here's our use case and background:

We want to customize our workflows with active lists that determine 'unengaged contacts' for those workflow automated emails, so enrollees can receive our intro emails (ie the first three emails) and after those, we can lock down the middle/back half of our emails if they aren't opening or engaging with us.  We'd like these contacts to stay in the workflow but be suppressed from receiving any other future emails if they do not engage with the emails up until that point in time.  This would help our send score and help us determine what an unengaged contact "looks" like (versus Hubspot's unengaged contacts that uses the last 11 emails, which is too many in our opinion).

 

In our workflows we can't use a suppression list, because we still want to include these contacts but they may decide to open an email later on and we still want them the opportunity for them to receive our emails moving forward, but we're having to do quite a bit of workaround  to achieve this. We have to create an if/then logic for every email based on their engagement list to receive each email, when it would be great to just have a 'do not send' list that we can add to those automated emails to keep the workflow canvas as clean as possible. 

We really want to keep the door open to these contacts if they choose to open our emails once enrolled but also not get dinged for sending any emails to them until they reach the 11 unopened emails that HubSpot deems as unengaged. We need to tighten this number up to protect our sending score to eliminate graymail issues. Please add this list setting to your automated emails to make our lives easier! Thanks. 

1 Comentario
amsteiner
Participante

Yes, this would be so helpful. I do the same kinda workaround — I create "has received x email" lists and branch off that, but it gets unwieldy.