List of Autotask Ticket Queues (In Progress)

List of Autotask Ticket Queues (In Progress)

"To Do" Queues

Each tech has a "todo" queue - items that should be addressed within the week but do not require scheduling with a customer. In general, these items may be treated as a lesser priority. This does not mean that these tickets should be ignored indefinitely.

Prioritizing "To Do" Tickets

As a guideline, tickets with a normal priority should remain in your todo queue for no more than 8 business days without being completed. Tickets with a high priority should remain in your todo queue for no more than 4 business days. 

Hint: There is a ticket template for each to-do queue. To effortlessly move a ticket into a specific queue, use the template. 
You can also create a ticket in a given queue via email using ThinkAutomation


In order to communicate to the queue owner that the ticket is more timely and customer is waiting on it, set the ticket priority to HIGH.  

Queues for scheduled work


Remote Support

Onsite Support

Help Desk - Work assigned to Mission Control Help Desk (They can see all queues and will initially see the ticket as long as its status is new and they are the primary and only resource. The queue is to help us stay organized. ) 

Alerts from Devices We Monitor - Sent either via SMTP or via Datto RMM to alert us to important device issues on devices we monitor. 

Notifications from Devices/Services we Monitor - Not as critical as alerts - sent via SMTP Sent via SMTP, IT Glue or Datto RMM - notifications about devices we monitor. Failed backups, domain expirations, disk space issues, etc. 


Other Queues 


"Workstation Offline" Tickets - Tickets that customer has been notified five times over five weeks that the device is offline but customer has not responded. Office admin / office intern can call customer as time permits. 
    • Related Articles

    • List of Note Templates in AutoTask

      Here is some info about Autotask Notes to start with. Once you understand notes, you'll find it helpful to be familiar with note templates. Notes are a type of form template in Autotask. Here are some of the more common note templates we use. Not all ...
    • Handling Customer Support Requests

      This article needs organizing when time permits. This is for current customers. For new customers, see “New Client Intake Instructions” Much of this info is intended for the office admin, but it is important for techs to know how to manage customers ...
    • Ticket Statuses (in progress)

      Much of the information regarding customer needs and issues is communicated between team members via tickets. For this reason, it's critically important that ticket statuses and notes are always kept up to date. Every resource on a given ticket is ...
    • Ticket Categories and How to Use Them

      The ticket options all flow from the category. So it's important to start with the correct category. Ticket Category Best Practices and Tips When you create a ticket, choose the category before doing anything else. The ticket's category can change as ...
    • Mission Control Help Desk Ticket Escalation

      What is a Ticket Escalation? An escalation happens when Mission Control can’t fully resolve a user's issue and needs to pass it to GGIT deeper investigation or higher-level support. It simply means the problem needs more specialized attention to get ...