How to enable Automatic Evaluation in an Escalation Rule
Automatic Evaluations enable Escalation Rules to trigger automatically instead of waiting for a manual execution by a user. By default, an Escalation Rule will NOT perform Automatic Evaluation, so this is enabled on a per-Escalation Rule basis.
This KB assumes you have already enabled the required webhook that notifies Rocketship of new/updated tickets. If not, refer to the KB Create Autotask Ticket Callout Webhook.
- Open your Escalation Rule in Rocketship Admin.
- Go to Automatic Evaluation Policy (refer to screenshot).
- Set Enable Automatic Evaluation to: YES
- Set When Status Changes To…: <trigger status>
- Click Save
Understanding the Status Changes To Field
This is an important field to understand how Automatic Evaluation works. To ensure Escalation Rules don’t fire every time a ticket is created/updated (which would lead to unintended escalations), the Automatic Evaluation requires that a ticket be sent to a specific Ticket Status.
For example, let’s say that you want the Default rule to trigger after a ticket is triaged. You have the ticket status set to ‘New’
- Autotask will notify Rocketship of the update via the webhook mentioned above.
- Rocketship will review any Escalation Rules with Automatic Evaluation enabled.
- Of those, it will refine the list to ONLY those where When Status Changes To.. is equal to “New”.
- Of those, it runs an Escalation Rule competition to find the winning rule, and then it runs that.
- If an Escalation Rule is not found for any reason, Rocketship does nothing.
Related Articles
Setup your first Escalation Rule in Rocketship
When you first setup your account in Rocketship, most of the needed default settings and rules are created for you. However, not all of the rules are enabled. We do this to ensure Rocketship only updates tickets, service calls, etc., when you are ...
How to create an Escalation Rule in Rocketship
To create an Escalation Rule in Rocketship: Log into Rocketship Admin Go to Dispatch&Escalations Click Create Rule in the Escalation Rules window Set the Name to be short but descriptive, e.g., “Network Support Tickets” If desired, set Schedule Type ...
Handling Escalations from Non-Escalation Rule Team Resources using the Bypass Feature
Occasionally, a resource working on a ticket may need to escalate it, but they are not part of the escalation rule teams associated with that ticket. This situation often arises when a ticket is handled by a third party (e.g., an outsourced ...
Troubleshooting Escalation Rules: Common Reasons for Non-Matching Tickets
Escalation Rules map tickets in Autotask to escalation paths used by Rocketship to assign and (if configured) automatically schedule resources. At times, a ticket may not match an Escalation Rule. This KB describes how to troubleshoot when an ...
Dynamically Update Who is Available in an Escalation Path
There are times you want to have very dynamic Escalation Rules where the people assigned change frequently. For example, you may have a triage tier and the person assigned to triage changes daily. There are three ways to do this: Set Resource to ...