SOLVED
1 ACCEPTED SOLUTION
Accepted Solutions
You can have a controller campaign when someone is added to the program that requests the three invite campaigns. Have a brief wait step (~10 minutes) in between each of the requests.
Then add an exclusion to invites #2 and #3 to say don't send if invites # 1 or 2 have been sent in the past x days or weeks.
This will let you throttle the messages and prevent them from all going out at once for someone who is added late in the game.
Example of the controller campaign I use below -- I use it for reminders and not for invites but the logic could work the same.
Controller Campaign
SMART LIST
Program Status is Changed in [your event]
New status [your triggering status, in my case, registered]
FLOW
A short wait to allow data to synch back and forth from the webinar provider, then request the first reminder campaign, another longer wait, then the second reminder campaign.
Reminder Campaigns
Both reminder campaigns have a similar wait step using tokens - wait until 3 days before webinar date, or wait until day of the webinar date. In both cases, if the date has passed, the email will send immediately.
However, the second campaign has an additional filter in the smart list to prevent the email sending if the other reminder email has sent in the past hour:
The outcome is -- if registers on 3 days prior or earlier, campaigns execute as intended.
If registers 2 or 1 days prior, will get an immediate reminder, then one the next day. Not ideal but I can live with it.
If registers same day, will get the first email and be blocked for the second.
Then add an exclusion to invites #2 and #3 to say don't send if invites # 1 or 2 have been sent in the past x days or weeks.
This will let you throttle the messages and prevent them from all going out at once for someone who is added late in the game.
Example of the controller campaign I use below -- I use it for reminders and not for invites but the logic could work the same.
Controller Campaign
SMART LIST
Program Status is Changed in [your event]
New status [your triggering status, in my case, registered]
FLOW
A short wait to allow data to synch back and forth from the webinar provider, then request the first reminder campaign, another longer wait, then the second reminder campaign.
Reminder Campaigns
Both reminder campaigns have a similar wait step using tokens - wait until 3 days before webinar date, or wait until day of the webinar date. In both cases, if the date has passed, the email will send immediately.
However, the second campaign has an additional filter in the smart list to prevent the email sending if the other reminder email has sent in the past hour:
The outcome is -- if registers on 3 days prior or earlier, campaigns execute as intended.
If registers 2 or 1 days prior, will get an immediate reminder, then one the next day. Not ideal but I can live with it.
If registers same day, will get the first email and be blocked for the second.
You can have a controller campaign when someone is added to the program that requests the three invite campaigns. Have a brief wait step (~10 minutes) in between each of the requests.
Then add an exclusion to invites #2 and #3 to say don't send if invites # 1 or 2 have been sent in the past x days or weeks.
This will let you throttle the messages and prevent them from all going out at once for someone who is added late in the game.
Example of the controller campaign I use below -- I use it for reminders and not for invites but the logic could work the same.
Controller Campaign
SMART LIST
Program Status is Changed in [your event]
New status [your triggering status, in my case, registered]
FLOW
A short wait to allow data to synch back and forth from the webinar provider, then request the first reminder campaign, another longer wait, then the second reminder campaign.
Reminder Campaigns
Both reminder campaigns have a similar wait step using tokens - wait until 3 days before webinar date, or wait until day of the webinar date. In both cases, if the date has passed, the email will send immediately.
However, the second campaign has an additional filter in the smart list to prevent the email sending if the other reminder email has sent in the past hour:
The outcome is -- if registers on 3 days prior or earlier, campaigns execute as intended.
If registers 2 or 1 days prior, will get an immediate reminder, then one the next day. Not ideal but I can live with it.
If registers same day, will get the first email and be blocked for the second.
Then add an exclusion to invites #2 and #3 to say don't send if invites # 1 or 2 have been sent in the past x days or weeks.
This will let you throttle the messages and prevent them from all going out at once for someone who is added late in the game.
Example of the controller campaign I use below -- I use it for reminders and not for invites but the logic could work the same.
Controller Campaign
SMART LIST
Program Status is Changed in [your event]
New status [your triggering status, in my case, registered]
FLOW
A short wait to allow data to synch back and forth from the webinar provider, then request the first reminder campaign, another longer wait, then the second reminder campaign.
Reminder Campaigns
Both reminder campaigns have a similar wait step using tokens - wait until 3 days before webinar date, or wait until day of the webinar date. In both cases, if the date has passed, the email will send immediately.
However, the second campaign has an additional filter in the smart list to prevent the email sending if the other reminder email has sent in the past hour:
The outcome is -- if registers on 3 days prior or earlier, campaigns execute as intended.
If registers 2 or 1 days prior, will get an immediate reminder, then one the next day. Not ideal but I can live with it.
If registers same day, will get the first email and be blocked for the second.
.png)