I have a workflow that I am trying to create for a recurring retreat. The flow is simple, I want to send a confirmation email, a reminder, and then a post retreat email.
I am having a hard time ensuring that the emails will not overlap (for instance, how do I make sure those attending the retreat june 24th, do not receive the “post retreat” email from the June 17th retreat). Will I need to make an individual workflow for each retreat weekend?
Let me know if anybody else has found a work around.
Hi @DLoback,
In my experience, separate workflows are the way to go. Things become messy if you try to create one automation that does it all. Once you create one retreat workflow you can use it as a blueprint and clone it for following events.
It would be possible to make everything work in one workflow (using branches, unenrollment criteria and re-enrollment based on a date property) but it would be finicky and prone to error. With separate workflows, there is a much smaller risk of things going wrong.
Could you elaborate on the overlap? Should some contacts then simply not receive a follow-up email? The easiest fix here seems to be a quicker send of the follow-up emails so it doesn’t overlap with the invite of the next email.
Otherwise, if you’re creating date-based workflows, you set up your enrollment criteria in such a way that contacts still enrolled in the previous workflow are excluded. Once they finish the previous workflow, they would enter the next and skip and emails that were sent previously, thus avoiding the overlap.
Best regards!