Workflow goal exiting and routing to another linked workflow

[nharb]

I want to create a series of workflows that are linked in sequential order to each other but checks for certain variables before enrolling in the next one; essentially, I'm trying to create sequential dynamic workflows.

The only way I can think to link them is using the "enroll in another workflow action", but if I set a goal in which the contact exits before they hit that action or it disqualifies them, I'm unsure how to effectively set up enrollment triggers for each individual workflow to make sure they follow the order in which someone would flow through the entire sequence.

I always prefer several goal-specific simple workflows that link to each other and take someone on a journey based on their actions to long complicated workflows. The issue I always come across is the goal function - we want it to track success without exiting someone. Does anyone have an excellent example of how they have done this before?

[karstenkoehler]

Hi @nharb,

Have you considered adding the goal of the previous workflow as an enrollment criterion for the next workflow?

You could still have the previous workflow use the "Enroll in another workflow" action.

Best regards

[nharb]

If they don't enroll in the previous workflow becuase they met that workflow goal then that's where it gets tricky. I guess that's where the enrollment triggers need to be specific ("or" statements) but the issue is that I don't want them to be eligible to enroll in multiple WFs at the same time. It would be nice if I could use that function with the option to add an or statement, but I think it could get tricky fast. I'm wondering if I should create a list or custom property that updates the goal and the actual properties are then used for enrollment. Have you ever done this?

[karstenkoehler]

Hi @nharb,

In that case you could explicitly use the goal criterion for enrollment. Is that goal the same for all workflows?

Maybe if you could share a few more details, this becomes easier to discuss.

Best regards

[nharb]

I beleive I understand what you are saying. And no, the goal is not the same for each WF. Enrollment would reference specific properties for goals that some individuals may have or not have, so they might skip over some particular workflows. For example, let's say you have a contact where you need three pieces of information, A, B and C. Some contacts could have A, while others have A and C, and some have B or C data or another combination. Each workflow goal is to gather each piece of data, A, B, or C, using various resources and incentives. A, B, and C are also how we prioritize what data is more important, so we want to put people through in a specific order to get the most important information (A) first. Does this make sense? Part of this is thinking through all of the unique combinations, but I think you are also saying that the goal statements (or possibly even suppression lists in this case) would help ensure proper enrollment happens sequentially.

[karstenkoehler · Accepted solution]

Hi @nharb,

Correct, it sounds like you have pretty specific requirements for when a contact should enter each workflow and you should be able to define that precisely.

If information is known already, you could ensure via a suppression list that a contact does not enter the workflow they already have met the goal criteria for.

If information is unknown, you would prioritize A over B over C. You could do this by defining enrollment criteria "B is unknown AND A is known" for the workflow that's supposed to gather B. It wouldn't enroll contacts where A is still unknown and where the A workflow needs to do it's job first.

Best regards!