Preventing and identifying contacts enrolled into multiple nurture workflows

[SilvanaPSI]

Hi - 

Wondering if someone has any ideas on how to solve this.

We sometimes find contacts enrolled into 2 or more nurture workflows at the same time. We started by using "Remove them from specific workflows" and adding all exclusions here, but this doesn't seem to be working as we wanted to. Because it only works at enrollment time, it won't work even seconds after the contact has already been enrolled. 

Any suggestions on how to easily identify contacts that double-enrolled in workflows? Or on how to prevent this?

We can't use the "remove them from all other workflows" option as we have many data management workflows that would be affected by that. 

Thanks 

[bcarter00]

@KKarkar I like the elegance of the solution you suggested here, but how do you typically populate the "last nurture enrollment date" property with data?

[karstenkoehler · Accepted solution]

Hi @SilvanaPSI,

I like to solve this by documenting on the contact record that the contact is being nurtured. This could be done in various ways, for example with a "Last nurturing enrollment date" date property.

For a contact to enroll in a nurturing workflow, you could either define that this date must be unknown or sufficiently far in the past.

By doing this in each workflow (setting the value and restricting contacts from entering), you don't have to juggle multiple workflows. Additionally, the "Last nurturing enrollment date" property can be very useful in reporting.

Best regards