Allow a customer to go down multiple if/then branches in a workflow

[TFacilitator]

In the current process for if/then branches, when a customer tests positive for the specific if/then parameter they are sent down that first branch despite the fact they may test positive for multiple branches.

If your intention is to send your customer down multiple branch journeys the only way to do this is to create multiple workflows and have the customer processed in each with their journey being split across multiple workflows. 

it would be good to have a situation where you can "re-insert" a contact after they have tested positive for one branch of the workflow to then keep getting tested for each of the parameters until all parameters are exhausted thereby keeping your total potential customer journey in one workflow and also being able to track their total engagement in that single area.

Would it be possible to have a function where the if/then parameter does not "stop testing" after a customer meets a requirement but continues to be tested against all parameters and send down all "yes" branches at the end of the if/then test?

[rwolupo]

yes ... nice idea

[FHeller]

Thank you for suggesting that!!

Same problem here with assigning different touchpoints to various leads!

[inenot]

Same problem here, also in assigning different touchpoints. Would be nice to see this being possible

[EGJade]

This would also be handy if a contact signed up to multiple workshops that required separate confirmations.

[joseph_cone]

This feature would be very useful.  I'm having to recreate if/then branches on a second level when just letting criteria decide which branches should and shouldn't run makes more sense... instead of forcing heirarchy. 

[LUlrich]

+1.

This would keep cadences much cleaner.

[CRichardson]

This is really needed, my current workaround for this is creating seperate workflows for each option just to make sure that contacts can go through multiple options. Fingers crossed it gets added as extra functionality soon!

[RDobos]

+1

[ABarta]

+1

[liam42]

+1

[aulicki]

You can use multiple checkboxes in a single workflow, but it takes some extra set up time. Your first if/then branch should be your first checkbox criteria. Branch all other if/thens off the "Yes" branch, and redirect the "No" branches to the next yes branch.

Multiple Checkbox Example (Ice Cream Flavor):

• Vanilla
• Chocolate
• Strawberry

Workflow Example:

• If Vanilla is Known
  • Yes branch then checks if Chocolate is Known
  • No branch goes to action > If Chocolate is Known Branch (above)
    • If Chocolate is Known
      • Yes branch then Checks if Strawberry is Known
      • No branch goes to action > If Strawberry is Known (above)
    • If Strawberry is Known
      • Yes branch goes to remainder of actions

[MagdaPrichodko]

Yes! I have branches based on multicheckbox property User Case with 6 options. Meaning a contact can have more than one user case. And I want to send a contact relevant email sequence based on every user case assigned. So if they have 2 user cases they will receive 2 email sequences etc.

In my case the solution suggested by @aulicki would have 36 branches.... ufff. Or 6 workflows. Not ideal. 

Anyone found anything simpler?

[Florian_Lengoc]

Good idea, this functionnality is also native on Zapier.

It's possible to send multiples branches at the same time, on the same workflow.

[LaurelShoger]

This would be a wonderful reature to have. We are looking for this same concept and hit a brick wall

[CD001]

+1

[ASpringer]

PLEASE +1 

[RBonney]

This is a nightmare for sending event reminders for events with multiple dates, The size and complexity of the workflows I am making just to send reminders/add to calendar links is INSANE. Please release this feature.