In Automations 2.0, do branching paths ever reconnect?
If an inquiry follows the "No" path but later schedules a consultation, is there a way to bring them back to the "Yes" path?
Or would I have to rebuild the entire consultation sequence inside the "No" path to account for that?
I feel like this could turn into a massive, duplicate-heavy automation. Am I missing something, or is this just how it works?
Page 1 / 1
I wish! This would be a fantastic integration.
@Cindy C , one possible work around is to duplicate that automation from that “Yes” point and have the trigger set to that specific session scheduled.
I just went through this entire process and had to build everything out several times...needless to say, my automations look far more impressive than they actually are!
@Ashley Rufino I’m not entirely sure my brain could handle that. And I don’t think it would work since it’s the same session I’m referencing in each of these stops.
Here, I’ll show you my stupidly complicated automation so you can see what I’m talking about. And this isn’t even half of it. This is just an example of the branching. I’d branch out the questionnaire but it’s a conditional logic typeform questionnaire that needs to actually have conditional logic in it. So having that as a Honeybook questionnaire—WOULD absolutely help this process, it wouldn’t be as helpful to me and the client.
And I guess one of the other things that is just kind of … well, I guess I’m not sure if it’s helpful or not is whether or not the inquiry emails me back instead of schedules a session. That’s a drop-off branch.
MAYBE a zapier integration would help but I honestly have never used it so I don’t know if that would be an answer even if it was integrated.