Triggers need a HUGE upgrade.
I can't seem to narrow the automation by Workflow type unless I am using the Contact or Job as a trigger.
This issue caused an abundance of automated text messages to go through during our initial sync that we did not anticipate (though we probably should have, hindsight is 20/20).
Customers whose invoices were paid months ago were sent text messages thanking them for paying their bill. I could go in and change all of my automations related to Invoices and Estimates to workaround this, but it just feels like that takes away from the usefulness of this automation system... yet again.
There is so much missing from this automations system that really centers around the limitations to triggers and conditions, some examples of what cannot be conditioned/triggered that would be invaluable...
- Template Name (Invoices, & Estimates in particular)
- Workflow (under EVERY TRIGGER) , or the ability to have separate folders for automations assigned to each workflow for example: Residential Workflow Automation Folder, and a Commercial Workflow Automation Folder ( could just be the ability to create automations folders that you self assign to a particular workflow)
- An ANY and ALL Conditions sections (so that you can use both/separate Require ALL conditions to be true and Require ANY condition to be true)
There are several ways you could go about structuring these developments, but it's a huge inconvenience.
New Example: we use a different type of Estimate Design Template to send "Change Order Estimates" that double as a change order form or agreement with the customer. This keeps us from having to duplicate work, and allows us to easily convert a CO Estimate into a CO Invoice for any additional payment amounts that might be required.
The trouble is, when a CO Estimate is created... automations revert our customer's status' and the flow of automations all the way back to the negotiations phase of the sales cycle. We have to do a ridiculous amount of "clean-up" in the system to get the customer and their account back up to speed.
In addition to cluttering their Job and/or Contact accounts, the change in status' will remove Jobs/Contacts from their appropriate board, thus making them invisible to the appropriate team member.
Right now, the only "work-around" that we have for this is fixing it manually... but the simple ability to use triggers for Design Templates would resolve the issue.
Honestly, if there is a label or input field in JobNimbus ... there should be an ability to trigger and/or condition by it. It would resolve at least 50% of the issues most people have with automations (excluding those that occur due to user error- and I assure you I've had plenty of those as well).
!!! Still finding a multitude of examples and situations where this would be useful!!!
Lucy Cruz commented
The plethora of automations that were triggered when we synced our systems was SUCH an annoyance for our customers and team! The automations are all-or-nothing, thus you have automations triggered when you don't want them to, or you have none at all. A big reason we chose JobNimbus as the new CRM was for the convenience of automations...it needs an update!
Obviously, there are a lot of other ideas created in this area, but honestly... I think this pretty much sums all of those complaints into one.