Autotask PSA is designed as a complete IT Business Management Platform for MSPs, now from Datto (resulting from the Autotask merger with Datto in 2017).
N/A
ServiceNow IT Service Management
Score 8.4 out of 10
N/A
ServiceNow is a fast-growing service management provider that went public in 2012. Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management, and (on the higher tier ITSM Professional plan) ITAM and software asset management.
Our Company uses Service now for a long time. I have seen the evolution and honestly the product has recently surprised me. The improvements have been incredible in terms of speed and ease of use. My team is very happy with the product. The interaction has improved remarkably …
Verified User
Engineer
Chose ServiceNow IT Service Management
Integrations with other products are very easy in ServiceNow IT as compared to other tools. Support is amazing comparatively. Transparency and flow of work are clearly visible. It has Multiple features and we can customize them as well. The search feature can be improved a …
In my opinion, Datto Autotask is exceptionally complicated to set up, manage, and use on a daily basis. I would think the target market for this product would be someone managing a team of 20 - 50 people, possibly more. In my experience, for it to run properly you will need to dedicate at least half an FTE to running this product in an organization of that size per month. I would not recommend it for companies with less than 10 people or for companies that value quick communication with their clients. I would not recommend it for companies using Datto's RMM product. The integration exists, but it is clearly a bolt-on. They were not developed together and they are slow to talk to each other. Frequently you cannot add details from RMM sessions into the PSA without manually copying the ticket number, and if the ticket is more than a week old, then you can't even find it with the ticket number.
In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
The graphical calculations on time spent on requests, how long they were open for, who worked on a ticket last.
Grouping by priority so you can determine easier what needs to be addressed sooner rather then later. This also helps if Account Management has conversations a technician is not aware of so they can prioritize efficiently.
The email updates that are sent out to the technicians so they are aware of upcoming or stale tickets.
When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.
It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
The portion of Autotask that we've used other companies for prior to using Autotask is the Endpoint Management. The Autotask Endpoint Management (AEM) portal integrates perfectly with their PSA/CRM tools. It's alerting features are much better than the above software as there aren't a bunch of superfluous and unneeded alerts. Instead, it only alerts for things that you specify that you want. Alerts aside, for the PSA/CRM, I don't have much to compare it to as Autotask was the first PSA we tried. It's hard to imagine a PSA having more features or doing a better job than Autotask.
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.
