When should you use Tickets vs Projects?
As many have pointed out, the project module in Autotask can sometimes appear a bit complex at first. However, with the right approach, it becomes a valuable tool.
Smaller changes qualify as a Ticket
To streamline your usage, the first step is to differentiate between requests that qualify as projects and those that are essentially non-standard changes. Smaller tasks or projects are best managed through tickets with a specific process. This approach allows you to leverage ticket functionalities for change management, including change info fields, approval workflows, and customizable UDFs. You can also employ workflows and notification templates to fine-tune the process. Often things like onboarding a new employee or Microsoft user can be small enough to fall under tickets, even though they are small changes.
Larger changes qualify as a Project
Upgrading your Project Management
Even when you use Projects entirely as the creators of Autotask intended, the functionality is still sometimes limited and other times overcomplicated. That’s why we created Proxuma.
You can try Proxuma today using this link: Try it today