Feature Request

Automations _should_ work if they are turned on at the account level even if they are turned off globally.
Right now I would LOVE to be able to setup an automation that sends a notification to the customer day before service. The problem is most clients do not want this. Only a handful of customers will benefit from this. Using the existing framework I have to build an automation and turn it on globally and then go through absolutely every single account that doesn't want the notification and turn it off. this could be a thousand accounts. Huge time waster, but its the only way it works. What would be better is if I could create the automation and have it off globally and turn it on at the customer level for the 5-10 clients who need it. Why this change must happen is because it brings in consistency with how everything else works in the software. For example, you can turn off late fees globally and turn them for just 2-3 customers at the customer level. Same with card on file required and deposit thresholds. All can be off globally and then turned on or configured at the customer level. FAQ - You might be thinking, 'well we need a way to turn the automation off globally if its broken or triggering incorrectly without going through each account to turn it off individually.' Yes that's true and that could still be possible by deleting the automation. Deleting an automation at the global level should be the best way to remove it from all customers. Please vote for this. Love Always, Brian Rand
0
·
Automation
Load More