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 Escalation Rule doesn’t match a ticket as expected.

There are 2 main reasons this can happen:

• The Escalation Rule’s Ticket Criteria aren’t configured to match the ticket.
• The Escalation Rule is disabled.

We’ll discuss each of those in turn.

How to Test Escalation Rules

You can test an Escalation Rule to see if it will match, without actually performing an Escalation, via the Predict button in Rocket/CMD. This will query the Escalation Engine to determine what it would have done if an actual Escalation had been invoked.

Ticket Criteria Mismatch

This is probably the most common! Often, you may create an Escalation Rule that is too granular, e.g., you want it to match “Issue X, SubIssue B, Queue C” when in fact the ticket is “Issue X, SubIssue B, Queue D”. Notice that the actual Queue is D, but the Ticket Criteria in your Escalation Rule restricts matching to be all three, including “Queue C.”

In this case, you either need to add an additional Ticket Criteria to match the Issue, SubIssue, and Queue C, and a second one with identical ticket values but with Queue D instead of Queue D, or you can remove the Queue restriction.

Escalation Rule is Disabled

There may be times when you disable an Escalation Rule during testing and forget that you have it disabled. Disabled rules are never included in an Escalation evaluation.

• Related Articles

• 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 ...

• How to Define Escalation Rules Specific to a Customer Group

  The Escalation Engine in Rocketship is versatile in that you can build out very specific workflows for helpdesk, NOC, co-managed, VIP customer accounts, etc. First, let’s remember that the Default Rule is your “catch-all” rule and should handle the ...

• Understanding Escalation Methods in Rocketship

  In Rocketship, the Escalation Engine plays a pivotal role in orchestrating the assignment and routing of tickets among different Teams and Resources. To grasp the concept of Escalation Methods, it’s essential to distinguish them from Escalation ...

• How to Test Ticket Criteria for Escalation Rules in Autotask

  When creating Escalation Rules, you will define Ticket Criteria to match a ticket against an Escalation Rule. How to test Ticket Criteria The best way to test Ticket Criteria, i.e., to check which Escalation Rule will match a given Autotask Ticket, ...

• Defining the Escalation Path in Ticket Escalation Rules

  Every Ticket Routing Rule has an Escalation Path. The Escalation Path defines the order in which Rocketship will escalate a ticket. Let’s take an example: For HelpDesk tickets, you want this order: IT: Tech 1 Team. This is your Level 1 helpdesk, and ...