If my first workflow enrolls contact A in Sequence 1 and my 2nd workflow tries to enroll contact A in Sequence 2, will it just not do it b/c you cannot enroll one person in more than one sequence? Or will it enroll them when they are no longer in another sequence?
We currently enroll contacts in sequences via a workflow that looks at a list. But we may have multiple lists that include the same target. So we want to enroll in one sequence, but after that one has completed, enroll in another sequence.
Hi @esealpha,
The second workflow will not wait and sequence enrollment will fail.
There are various ways you could approach a delay:
- Delay until property value is changed (“Currently in sequence is False”)
- Work with properties “Last sequence enrolled” and “Last sequence ended date” for enrollment in your second workflow
Keep in mind that contacts might unenroll from a sequence because they have met one of these unenrollment criteria: Unenroll contacts from a sequence
Immediately enrolling them in the next sequence might not be a good idea. Instead you could consider simply combining sequence 1 and 2 to achieve the same behavior and ensure that contacts don’t continue receiving emails from the second sequence after, for example, replying to the first sequence.
Let me know if you have any follow-up questions!
So, we add a delay to the enrollment workflow (using the “Currently in sequence is False” for example). Essentially, we’re saying don’t enroll someone if they are already enrolled in another sequence. If that is the case, then how do we eventually enroll them? I’m assuming that would mean we would need to set the trigger to re-enroll contacts? And if that is the case, would it then re-enroll someone else who’s already been through that particular sequence?
We’re still figuring this out, but we aim to have sequences running constantly. But going to a specific group of targets. Since we’re just starting out, we’re running into some crossover from multiple lists. But eventually, those lists will dwindle, and there will only be one or two people at a time. But we still need to build in the delay to ensure we automatically enroll people as needed.
Hi @esealpha,
@esealpha wrote:
So, we add a delay to the enrollment workflow (using the “Currently in sequence is False” for example). Essentially, we’re saying don’t enroll someone if they are already enrolled in another sequence.
That’s not what I wrote, no. You would enroll the contact but use the “Delay until property value is changed” option within the workflow. Once the value turns to False, you could then enroll the contact into the next sequence from the workflow.
@esealpha wrote:
And if that is the case, would it then re-enroll someone else who’s already been through that particular sequence?
You would have to make sure that you set up enrollment and unenrollment criteria or branches to check whether someone has been through a specific sequence already. HubSpot would not do this automatically.