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 escalation team) or in a co-managed ticket scenario.
By default, Rocketship routes escalated tickets from non-escalation rule team resources to the first escalation rule team (Tier 1). However, depending on your business rules, you may want to bypass the first tier.
Bypass On Escalations Setting
The Bypass On Escalations setting allows you to specify that an Escalation Rule Team will never receive an escalated ticket but can escalate tickets out. For example, if an outsourced escalation service works on a ticket and escalates it, the ticket could be routed directly to Tier 3 instead of going through Tier 1.
This setting is particularly useful for scenarios where certain teams should not handle escalated tickets but need the ability to escalate tickets themselves.
By configuring the Bypass On Escalations setting, you can ensure that tickets are routed efficiently according to your specific business needs.
To access this setting:
- Click Edit on the Escalation Rule Team in the relavant Escalation Rule
- Click on the Advanced Tab
- Enable “Bypass During Escalations”
- Click Save
You will then see your tiers modified in this way:
In this screenshot, the 2nd tier will never receive escalated tickets (whether Up or Down) from Rocketship, but will still match as the related Tier if they escalate a ticket.
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 ...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 ...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 ...Using Ticket Routing to Automate Dispatch & Escalations
With Rocketship for Autotask, it is easy to use ticket routing to automate dispatch & escalations. Ticket routing is how you shuffle tickets around – whether it’s a dispatch, which is assigning a ticket to a resource when there’s been no assignment ...