Skip to main content

I built out my Inquiry Automation 2.0 after finally figuring out that all active automations run universally, all the time (more or less).

After having to build in some stop gaps like: Session scheduled? yes > end automation (because a session being scheduled will also trigger the Consultation 2.0 to run) but not all clients immediate schedule a consultation.  Session scheduled? no >  Did they respond at all?

My only stop gap for that is to create a task after the session split that if I check that they did respond that it ends the automation. (Last thing I need is for it to “WAIT” and then I forget it’s waiting and then it continues running down paths.) 

This has made my old linear automation REALLY REALLY complicated and long. And it’s difficult to see if I’ve built it correctly because there are 3-4 different places where I’ll wait for a session to be scheduled (or not), or get a response (or not), before I send a check-in and then the same tasks and paths are repeated down certain branches. 

And while this would be a fantastic feature to run completely automated and such a time saver—that’s only going to work if these automations can tell if there was a response. Otherwise, I feel like it’s more complicated than it’s worth right now. One automation has taken me hours to build. And I’m still going to have to babysit it. Possibly even MORE now than OG Automations. Which is a major bummer.

That’s a very very long way to ask: is there a way to print this out as a PDF or any other way to check to see if these crazy branches are set up right? 

Hey Cindy! I hear you, you definitely want to make sure that’s all set up correctly before activating them for your real clients. Unfortunately, I don’t think there’s any way to download your automations as a PDF (we shared your feedback internally though, and lots of improvements for automations 2.0 are going to be released throughout this year, based on member feedback!).

The way I’ve found that’s easiest for testing and confirming how my automations are going to work in real life is by creating a project type: test in my company settings, and then changing the trigger for all my automations that I want to test to only run specifically for project type: test. Then I activate those automations and pretend to be a new lead by filling out my lead form with project type “test” selected (or you could manually create a project and tag it with that project type - depending on what you’re wanting to test). Then in your case, definitely see what happens if you schedule a session (or not) using the client-facing scheduler link in that test project. Personally I found this the most useful for testing because as I ran through the possible workflow with my test project, it helped me identify other loopholes or cracks that I needed to fill with my automations.

This help center article can help run you through this idea, too: https://help.honeybook.com/en/articles/10345380-run-a-test-automation

Reply


Terms & PrivacyCookie settings

© 2024 HoneyBook Inc.