How to optimize your Sends using a retry?

When applying DESelect Engage on your journeys, there will always be 2 paths where the contacts will go through, the Include and the Exclude paths.

Contacts who appear to be not saturated will go through the Include path and will carry on to receiving the campaigns. However, what happens when contacts are saturated and go through the Exclude paths? Normally, they would need to exit the journey. 

So what if you retry sending the same communication at a different time to see if the contacts are by then not saturated anymore?

In this approach, for the Excluded contacts, you are setting journeys so you can retry multiple times to send the same communication, instead of exiting them from the journey. This can be seen as throttling or finding the perfect moment for each send (without necessarily reducing the number of communications sent).

Below is an example.

See how the Exclude branch is followed by an X days wait, and a retry to send the email by joining the Include paths back to the original Include path.

Things that you need to consider using this approach:

1. The first Engage item will be the Send you have configured in the Calendar, and the following ones will be new Sends, to be able to track the results separately.
2. These new Sends do not appear in the Calendar, but in List View > Unscheduled Sends or in the Dashboard. By not being visible in the Calendar, it will have an impact on your planning.