Hi ​@Vincent1983 

Thank you for posting your question in the community! This is a good question. 

Typically, Klaviyo does not automatically resend a message when it soft bounces (and if an address bounces 7 consecutive times, it will be suppressed). 

But, you should be able to achieve resending the welcome message if someone bounced using a cloned version of the message, following a conditional split that looks for Bounced Email where bounce type is soft, with a 24 hour wait step beforehand. 

For example:

And the conditional split would look like:

I would caution you that if you try and resend the email again and it still bounces, increased bounces on your domain/IP could over time impact your email deliverability. So, I would only recommend doing this sparingly for only your most important messages. 

I hope this helps!

​@In the Inbox 

Thanks ​@In the Inbox 

This helps! The warning you give. The flow would keep running nonetheless is if we resend email 1. We are just adding one more email to the flow. 

I guess you could even do another conditional split where you detect if the second email also bounced and then do a profile property update and suppress? This way you are even more strict than klaviyo itself. Or is supression not possible via a profile update? 

Thanks.

Vincent

Hi ​@Vincent1983 

Glad to hear this was helpful. 

I think if you are adding just one email to try and resend to the bounce, you should be OK. My only caution was if you end up seeing a lot of bounces on this flow, and then resending to those addresses, only to see them bounce again. But, I would expect you would have a lot of contacts going down this path every month. 

24 hours between two soft bounces isn’t a lot of time so I don’t think you need to do a suppression right away (especially seasonally, like the summer time, when people are traveling more often for longer periods of time). 

Unfortunately, you cannot do a direct contract suppression via a profile update step in a flow. But, you could add or remove a contact from a list (maybe setup a list to suppress once a quarter, or something), or you can set up a webhook step to suppress a contact. 

Again, I don’t think you need to go this far given I wouldn’t expect you’d have a lot of bounces other than a handful each month, not to mention, if you are sending campaigns as well, all of that traffic will blend together to balance your deliverability reputation.

I just wanted to caution you on driving more bounces via a flow which could lead to deliverability issues in the future. I’d just monitor this as you get it live and assess what is a reasonable threshold for you and your account. 

I hope this helps! Let me know if you have any other questions!

​@In the Inbox