If the "Has Encounter" field denotes the transaction, and you need to send an email 10 months/305 days after that transaction, you could build a triggered campaign saying Data Value Changes, with Attribute as "Has Encounter" and a constraint for new value = TRUE. In the flow, you could add a wait step of 305 Days, and then send the email.
Hope this helps!
This almost works. It has to be a specific type of encounter/transaction in which we label. When trying to add a constraint, I can't get the right attribute category to show up as a constraint option. If you choose encounter, it could be any encounter which could throw off the reminder email program.
1 of 1 people found this helpful
I would set this up as a batch campaign rather than a trigger campaign with a wait step.
The trigger and wait would get messy here because you would also have to account for updates to the customers "last transaction date". Essentially, the lead would need re-enter the campaign each time a customers "last transaction date" changed. This would require another campaign to remove leads who's "last transaction date" changed and then building your campaign so that a lead can qualify multiple times.
By using a batch campaign you can let the smart list dictate who should receive the email on the day of deployment. The smart list criteria should be: last transaction date in past before 304 days AND last transaction date in past 305 days. Setting the smart list up in this manner will ensure that only transactions 305 days ago are included in that days batch email deployment.
Hope this helps.
Thanks Joseph, I will look into the batch campaign to see if this might be a better option.