There's a very old slide deck, which I might have if I have time. Maybe Jessica has it. But you know you sound smart, so I bet you can design what you want and then do it. The traffic cop is like this: Trigger on Conditions If X, then do Y if Z, then do A allow repeats With engagements, it's worth recalling the following: you'll have to trigger on lifecycle or a key change like score if you do a batch redo, then same deal, but you could have new options if fields or list members move. DO NOT remove a lead from the Engagement, move to an Empty Stream and List so you can re-route back you can "traffic cop" inside engagements based on Stage/speed/etc. Lead can be in ONE stream at a time. I suppose I'd base this on my Engagement or Stream Goals and somehow allow that to trigger the movement to re-route leads. I wrote about this at the Summit 2016. Nurture Waterfalls.
... View more