It's was almost comical when sitting in the demo and you ask those questions, "What about this scenario?" and then it's a quick "Yep, we can do that. Here is how you could approach that.". In most instances, you can take the core software and make it your own with relative ease. The support has been fantastic in responsiveness and answering questions about how to make the application fit our business. Before we used supaTools, we were floundering with what assets we had and what tickets were our priority. With the SLA integration, we are now providing a better service to our internal customers and have really good data to make good business decisions.
Pros: The environment is web-based and has a lot of different automation and integration points including active directory for logins. We utilize email ingestion through our Office365 account and it works like a champ for creating tickets and responding to tickets via email. The core allows you to add, remove, change features and fields with ease. Templates are key for incidents, which you can create many of to allow customers to fill in minimal aspects of an issue while still giving you pre-populated fields for reporting and SLA needs.
Cons: With any highly customizeable system, you run the risk of making things too complicated.If you have your internal processes defined well, it makes the transition to this product very easy.