Settings
66 results found
-
Work orders and automation
Trying to automate work orders when completed to move the parent contact from a certain status to another status, the issue is that we may have multiple work orders for one job but only one work order for another, then when we move the worker order to completed it wont move the parent file to the new status because only one work order was created. Is there a way to base the status change regardless of how many work orders you create for a parent file?
7 votes -
Automations to Change Work Order Status
Would like to be able to Work Order status as an option in the actions of an automation. For now, actions can update contacts and jobs, but it would be helpful if it could update the Work Order too.
6 votes -
Complex Automation Conditions
Currently, an automation with multiple conditions can trigger by requiring ALL or ANY of the conditions to be true. I need to be able to adjust specifically which conditions must work together.
Our company has many tasks that complete at certain stages but that do not follow a specific order. So I need to be able to set a condition that can look for one series of conditions AND a second series of conditions and so on at the same time. I can't really split this up because the tasks are handled separately, and the completion order just depends on…
6 votes -
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...…
6 votes -
Days in status being part of automation conditions
For days in status as part to an option in the conditions section of automations.
6 votes -
Templates trigger Automations
Would like to be able to trigger Automations when a specific Template is used; notifies our admins of new proposals, etc.
6 votes -
Assign To as a possible Action is Automations
Would like to see the option to assign team members, ie production manager to a job at a specified stage or status. This would go in tandem with how email replies are associated with Assignees. I would like my production manager to automatically receive emails for a job when it enters Production.
6 votes -
Automate document creation
I would love to take a customer who has agreed to a proposal to move to a new status that triggers document creation from a template like a contract etc.
6 votes -
Separate automations for each location
It would be nice to be able to set automations specific to each location as some items are applicable to some locations but not others.
5 votes -
Ability to Pause Particular Automations, or Make them Active vs. Inactive without Deleting
Something that would be Critically Important for updating automations while the system is in use would be having the ability to pause automations. Along with our realization today that automations for Invoices/Estimates were going to be triggering on all workflows (see suggestion " Triggers need a HUGE upgrade"), we realized that we couldn't just pause these automations during a transitional phase.
This signals to me that I'm also not going to be able to work with automations unless we're ready for them to go live immediately. This makes the time window for making changes to automations VERY short.
5 votes -
Automations - Deleted Tasks or Branching
Automations continue to run for tasks that have been deleted. Branching automations would be very helpful in preventing these issues, as it could aggravate the recipients and cause confusion.
For example " I thought I rescheduled my appointment, but I'm still getting texts for an appointment at 8AM?! What is going on?!"
Branching would allow us to say: When A happens, if B is true, then do C. BUT If B is false, then do D instead (or do nothing).
5 votes -
Advanced Logic paths for automations
When creating an automation, the conditions are very limited because they are specific to the type of automation, and the trigger can not be made to be very specific. also, the actions are limiting since we can only send emails, update record status, etc.
what would be ideal is if we could add additional conditions which apply to other job details.
for example, we have an automation which, upon sending an estimate, it updates the status to "pending customer approval." the only issue we have is that we use the new estimates for preliminary contingency agreements with no dollar amount.…
4 votes -
Email Notification When EagleView is Uploaded
I would like to be able to set up an automation so I can be notified when an EagleView report comes in.
4 votes -
Automation for multiple invoices or based on multiple record types
I progress bill, meaning I bill up to 3 times (deposit, in-progress, and final bills). Having an automation that can change the job's status once all invoices have been paid or be based on all invoices being closed and the jobs status matching a specific status would be very helpful. I need to make sure the automation only happens from the Pending Payments status and ALL invoices created have been paid/closed
4 votes -
4 votes
-
Estimate Automations - condition around workflow type
The ability to place a condition on an estimate automation for the workflow type.
4 votes -
Maintain existing workflow on parent records when an automation with multiple status change actions on it gets triggered
Improve automation action capabilities so that two or more status change actions that occur in different workflows can exist on the same automation, without them conflicting and some times changing the Contact Type or Job Type of the parent contact or job record to a different workflow.
4 votes -
Expand the different conditions that are allowed for automations to trigger on.
For instance, allowing an automation to filter by a certain word in the name of a job. Allow greater freedom for creating more specific conditions for automations.
3 votes -
Job Automation With Ability to Change Type, Not Just Status
Warranty jobs go in the warranty workflow, but sometimes they end up not being warranty. This means the type/workflow needs to change. Our sales reps only really change statuses, not the workflow/type, because it requires extra time to open the edit box. We need to create an automation that changes the type/workflow based on a status in the warranty workflow that triggers this change.
3 votes -
Contact Automation With Ability to Change Type, Not Just Status
This is needed because it is not possible to create a job automation with a parent contact Type condition. My workaround was going to be to have the parent contact of the job change to a status that is a trigger status to change the contact type (so the use of both a job and a contact automation to accomplish what we need).
3 votes
- Don't see your idea?