Skip to content
Welcome to our Knowledge Base
Categories
Table of Contents

Defining the Escalation Path in Ticket Routing Rules

Every Ticket Routing Rule has an Escalation Path. The Escalation Path defines the order that Rocketship will escalate a ticket. Let’s take an example:

For HelpDesk tickets, you want this order:

  1. IT: Tech 1 Team. This is your Level 1 helpdesk and they get all new tickets.
  2. IT: Tech II Team. This is your Level 2 helpdesk and they only get tickets that Level 1 can’t resolve.
  3. IT: Service Manager Team. This is your service manager and she only gets tickets that your Level 2 can’t resolve.

In an Ticket Routing Rule:

  1. Click on Edit Ticket Routing Rule in the Escalation Path window
  2. Drag & Drop the teams from the Unassigned Teams box into the Assigned Teams box — this is an ordered list, so you can move them up/down as needed
  3. Click Save Changes
Defining the Escalation Path in Ticket Routing Rules › Giant Rocketship | Autotask
Editing your Escalation Path

Once done, you’ll see the Escalation Path has been updated in the Ticket Routing Rule:

Defining the Escalation Path in Ticket Routing Rules › Giant Rocketship | Autotask
The finalized Escalation Path for this Ticket Routing Rule

UPCOMING DECEMBER WEBINAR ON AUTOTASK KANBAN

In this webinar, Dustin Puryear, Autotask expert and MSP industry veteran, will show you how to set up Kanban boards in Autotask, integrate them with your workflow rules, and how to get the most out of them.

Share via
Copy link
Powered by Social Snap