Skip to main content

Automations 2.0 Feedback & Requests

  • August 13, 2025
  • 4 replies
  • 38 views
A

I recently emailed this to the Honeybook Concierge. Would love it if others would comment, upvote, provide their experiences so far, etc. 

 

I’m reaching out as a long-time user who relies heavily on automations to manage my client experience. I want to share some honest feedback about the new Automations 2.0 system, as I’ve encountered several challenges that are making my workflow more stressful and less efficient:

  1. Inability to Edit or Skip Steps for Individual Projects:
    Once an automation is running on a project, I can’t skip or remove steps for that specific client. If a step (like a welcome email) has already been completed manually or by a previous automation, I have no way to prevent it from being sent again without canceling the entire automation.

  2. No Option to Delete or Fully Remove an Automation Run:
    Even after canceling an automation run, it remains in the project’s history, which creates clutter and confusion.

  3. Manual Trigger Limitations:
    I can only apply automations with a manual trigger from within a project. This means I have to create duplicate versions of automations just to have the flexibility to start them when needed.

  4. No “Resume” or “Start from Step X” Feature:
    If a client books late or a step is already completed, I can’t start an automation from a specific step. I have to create a new automation for every possible scenario, which is time-consuming and error-prone.

  5. General User Experience:
    The new system feels less flexible and more complicated than before. It’s adding stress to my workflow, and I’m spending more time managing automations than serving my clients.

What would help:

  • The ability to skip, edit, or remove steps for a single project’s automation run.
  • The option to delete an automation run from a project entirely.
  • The ability to start an automation from any step, or mark steps as completed/skip for a specific project.
  • More intuitive controls for managing automations on a per-client basis.

I hope you’ll consider these suggestions as you continue to improve Automations 2.0. Thank you for listening to your users!

    This topic has been closed for replies.

    4 replies

    Laura Murphy-Find Your Freedom
    Forum|alt.badge.img+3

    100% to all of this. I’m a HoneyBook Pro and have been doing setups for almost 10 years now. I personally love automations 2.0 for the processes you KNOW are always the same - and (love the conditional logic) but these limitations are personally keeping me from moving my own account to 2.0 and keeping me from recommending it to many clients who pride themselves on personal experiences. The time savings of conditional logic is not yet worth the headache of having to cancel runs when you just want to skip a step, create new automations for every little scenario, etc. 

     

    To be clear, there are MANY steps forward with automations 2.0, and I think it’s INCREDIBLE for businesses who truly truly want to automate, but when you have projects that have their own nuances, it really limits the ability to customize the workflows.

     

    I have said from the beginning that while the automation capability is better, it feels like the ability to have a project workflow has been taken away. I agree with all of your feedback + all of your solutions and hope that it gets built!

      Alicia Bauer
      Forum|alt.badge.img+4
      • Alicia Bauer
      • Newcomer
      • August 15, 2025

      ​@Andrea Brandt -  Yes to all of this, I couldn’t have said it better myself, and I completely agree with everything Laura shared above.

      As someone who also supports other business owners in their systems, I see the value Automations 2.0 brings for streamlined, predictable workflows (especially with conditional logic!), but the current limitations are exactly why I haven’t fully switched my own account over yet either. The lack of flexibility, having to cancel automation runs just to skip a step, or needing to create multiple automations for edge-case scenarios, makes it tough to recommend for businesses that prioritize high-touch, personalized experiences.

      There’s so much good in Automations 2.0, it really is a powerful step forward, but I also hope we can find a balance between automation and project customization. I’d love to see some of these thoughtful suggestions implemented to bring back that true sense of flexible workflow management.

      Alicia, Brand and Web Designer + Honeybook Pro
        Bethany Wolf

        THIS.

        The new updates are great, but the functionality actually makes it much more difficult to work through these automations vs the old automations fully with my clients.

         

        Not having the ability to edit file templates, skip steps, start from a specific step, or even “fast forward” through wait times for clients who may have a quicker timeline than others is extremely frustrating. Constantly having to duplicate an automation to make small edits is not ideal when you’re trying to make things as efficient as possible.

         

        I hope the Honeybook team really hears the community on this topic and makes the suggested changes in automations 2.0 because it would really make a world of a difference in keeping the automations as simple and efficient as possible for business owners.

          T

          How is this not getting more attention? You hit the nail on the head. 

            Terms & PrivacyCookie settingsAccessibility statement

            © 2025 HoneyBook Inc.