Managing Escalation Rates with Escalation Cooldowns
The Rocketship escalation engine manages both dispatching new tickets and escalating assigned tickets. There are times that a single person may escalate a ticket before you want that to occur, or when two people may try to escalate the same ticket at the same time. To manage this, the escalation engine provides an escalation “cooldown” setting.
Escalation Cooldown Settings
There are two settings that govern how quickly a ticket may be escalated after a previous escalation.
- Escalation Cooldown Minutes. This governs how quickly a ticket may be re-escalated after a previous escalation.
- Escalation Requestor Cooldown Minutes. This governs how quickly a ticket may be re-escalated by the same requestor after they previously escalated a ticket.
When managing the “cooldown,” the escalation engine will use the greater of the two values.
Example Use Case
First, let’s assume that Escalation Cooldown Minutes is 0 and Escalation Requestor Cooldown Minutes is 1. Now, let’s say you have a dispatcher that is escalating tickets. They escalate a ticket at time 10:01 and then click escalate again a few seconds later.
The escalation engine will not allow this request to be made since the requestor (i.e., the Dispatcher in this example) escalated this same ticket less than 1 minute ago. However, another person could escalate this ticket and the escalation engine would allow it based on the configuration. To disallow the second user from escalating the ticket within the same minute, Escalation Requestor Cooldown Minutes would also be set to 1.
Setting Defaults
By default, the escalation engine is configured to disallow a double-escalation by the same requestor within a 1-minute timespan, but it will allow another user to escalate the ticket within the 1-minute timeline. You can alter this to best suit your needs.
Updating the Setting
To update these settings:
- Log in to the Admin Portal
- Click on Dispatch&Escalations->Escalations Home
- Click on Custom Settings View
- Update the values as needed
Related Articles
Overview of Scheduling Constraints for Escalation Rule Teams
The new Scheduling Constraint feature allows you to set specific active periods for your Escalation Rule Teams. This can be useful for managing coverage outside of regular business hours, setting up special teams that are active before or after ...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 ...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 ...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 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 ...