When to Use Tickets Vs. Tasks

When to Use Tickets Vs. Tasks

Tasks are used when both of the following are true:
  1. There is an Autotask Project in which the task can be created
  2. The work to be done in the task is not customer-facing (no appointment with customer). 
If either of these is not true, you must use a ticket. (Tickets can also be associated with projects.)

If you need to schedule a service call with a customer, the service call must be attached to a ticket, not a task. 

    • Related Articles

    • Creating Tickets: Best Practices

      Set the Category FIRST When creating a ticket or starting work on a new ticket which arrived via email, the first thing to do is to choose the category. Everything flows from the category. If you choose the correct category, you will be presented ...

    • Creating Recurring Tickets and Service Calls

      What are Recurring Tickets? We use recurring tickets for scheduled maintenance that must be done on a recurring basis. The recurrence instances of each master ticket have a number appended. For example, if the master ticket is T20190528.0050, then ...

    • VPN vs. Remote Desktop Services

      This is Sonicwall specific but can be edited for use with Todyl, Meraki, etc.  Splsahtop is a Remote Desktop service. Remote Desktop services like Splashtop work differently from the VPN. With the VPN, the user is bypassing their office machine and ...

    • Account Classifications: Managed Services vs. Break/Fix

      In the IT field, from a business standpoint, there are two types of customers: break/fix and managed services. Our managed services customers are the priority of our business. The needs of break/fix customers are secondary to that of the customers ...

    • Deferred tickets

      Tickets with status of Deferred will become “follow-up needed” and moved to L1 queue 7 days before their due date. (WF Rule NYGG07) When deferring a ticket, you should move it to the deferred queue so it doesn’t clutter up the main (L1) queue.