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.
$10,000
per year
TOPdesk
Score 8.7 out of 10
Mid-Size Companies (51-1,000 employees)
TOPdesk is the flagship highly-modular cloud-based or installed ITSM service desk and asset management solution from the Dutch company of the same name, for enterprise companies.
N/A
Pricing
ServiceNow IT Service Management
TOPdesk
Editions & Modules
Starting Price
$10,000.00
per year
No answers on this topic
Offerings
Pricing Offerings
ServiceNow IT Service Management
TOPdesk
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
The TOPdesk license model:
- Modular: Organizations purchase only the modules needed
- Saas or On premise
- Supports unlimited number of assets.
- End users OR service agents based. For flexibility in the number of agents for e.g. extra busy times of the year, the end user license allows adding agents without any restrictions, no day passes needed.
The IT Asset Management tool that is included and the way you connect that to your support portal is one of the things where ServiceNow is stacking up against Jira or TOPdesk for example. The features are unlimited and that is why we prefer this tool.
Verified User
Consultant
Chose ServiceNow IT Service Management
ServiceNow feels like a more robust and polished product the creation of workflows and flexibility to customize is better than with the rest of the applications, it is also easier to integrate with external applications as these 'connections' are regularly updated to …
Compared to Horizon, Freshdesk and ServiceNow IT Service Management, TOPdesk offers a much finer user interface. I also find the different modules and clarity much nicer to use. Automation and Asset Management have also had an update, making these much nicer to use as well.
We have assessed TOPdesk together with ServiceNow, Salesforce Service Cloud (we already use Salesforce), Heat and Cherwell. Reason for chosing TOPdesk:
- SAAS (requirement)
- Pricing model (functionality versus license model) --> relative low investment to start TOPdesk
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.
I think TOPdesk is best fitted in small to medium businesses, if there is someone capable of programming the rule sets. Those can be hard to create properly or maintain over time. The knowledge base and Self Service Portal can provide users with some insights and help, even if the SysAdmin is unavailable at that time. I don't think it is suitable for larger companies, because I personally think it will get quite messy then.
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.
TOPdesk provides a clean and modern interface for all of its modules. Many of the modules have a similar look and feel, which makes it easy for users to utilize each one.
Its workflow system allows administrators and developers to define what needs to occur when certain events happen. This can ensure that processes happen in the correct sequence.
TOPdesk includes a vast API system to allow for external systems to integrate with it, and for TOPdesk to communicate with external systems.
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!
The requirement to fill out certain fields before a ticket can be closed can be cumbersome. This could be a requirement for some organizations though.
The field mappings from Azure AD to user data could be a little more precise. Some of the fields just don't translate.
When setting up the system to intake emails as trouble tickets, it can be tricky when people reply after a ticket is closed. It will create multiple tickets from this.
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.
As the project manager for the system, I find it to be intuitive and helpful to keeping our technicians in the field and working rather than running back all the time for paper copies of work orders. I think once we have a solid year under our belt there are things that we can work to expand on. The technicians like it because they can look back at old work orders to see what we did in certain locations to make repairs. All the notes are contained on the system rather than relying on someone else to put them in and dig them back out. The system benefits the technicians when they use it to their advantage. We are also finding reduced calls to the office asking about work order statuses. The customers are getting real-time updates on their requests.
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.
Sometimes I think some things are hard to find. I often do not know if I have to search in Settings or in Modules. In some cases the user has to do a lot of clicks for example to link a key to a user. Something could work a little smarter.
Like I said somewhere else in this review: the helpdesk of TOPdesk is top of the bill! In the Netherlands, that is. I can not plea for the helpdesks in other countries, but I guess the TOPdesk organization will make sure the quality of the helpdesk is the same in every country.
Although being a SAAS solution, TOPdesk performs pretty fast. One can imagine that any SAAS solution is slow or has hiccups, but we have not experienced such with TOPdesk. Pages load quickly, logging in goes smoothly. We have made reports on premise in the past - that always took some time, as you might expect with such complex tasks. It seems that in the SAAS solution TOPdesk somehow has managed to make it even faster!
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.
TOPdesk is easy to use and affordable with all the major features required for any organization to smoothly manage its services. We were not quite sure at the beginning if we should go with the TOPdesk for IT service management but we started getting used to it in just a few months. Now, after using it for 3 years, it has been a backbone tool of our organization. The customer support provided by TOPdesk is fast and reliable.
We had Topdesk in-house here training staff for almost a month (2-3 hour meetings 3x a week.) It was invaluable and we were able to take that training and share with the rest of our IT staff. Once implemented we were able to fly from there. The challenges we found were in how to get started. Once started the knowledge base offered from Topdesk has been invaluable.
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.
Online training documentation is easy to access and consume. There is no real challenges with finding information on how to use the product and some really helpful knowledge base items that show us how valuable these options are in our own implementation of it. The online training we've used has been self driven
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.
It was a challenge to port over years of the same thing and we ended up keeping old ideas in Topdesk that we will eventually weed out as time passes and we learn how users view categories and flows of tickets. Planning is key but bear in mind that just because you used to do it this way doesn't mean you still have to
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.
TOPdesk was picked as our new Helpdesk solution due to the Asset Management module and the ability to integrate to Active Directory. When we work with the product demo we enjoyed the way TOPdesk does its work flow. Just about any field in the system is customizable. I have found their knowledge base of the product to be well written and up-to-date.
TOPdesk is very flexible and scalable. Every department in you organization can you the software. Perhaps some persons need some training, but that can be provided by TOPdesk ot some keyusers.
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.
The self-service portal has allowed us to shift left massively. Students can find the solutions themselves very often.
It has allowed easier collaborative working between teams.
We are more efficient as we do not have to ask the student to repeat their question and we can record everything necessary in the incident. This provides an improved student experience as well as improved staff efficiency.
