HaloITSM provides ITIL aligned help desk software that can be installed on premise or in the cloud. Boasting over 25 years of experience, HaloITSM has been developed to offer a feature rich application whilst maintaining a simple to use interface. Features include: Incident Management, Problem Management, Change Management, Asset Management, Service Catalogue, Telephony Integration, as well as the best of breed mobile apps. The vendor describes the following five differentiators: 1.…
$49
per month per user
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.
$10,000
per year
Pricing
HaloITSM
ServiceNow IT Service Management
Editions & Modules
On Premise
$49
per month per user
Cloud
$49
per month per user
Starting Price
$10,000.00
per year
Offerings
Pricing Offerings
HaloITSM
ServiceNow IT Service Management
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
There is 15% discount for all charities, educational institutions and non-profit organisations.
HaloITSM offered the highest level of functionality, available as standard, at our price level. Halo support during our trial period was second to none and unrestricted. We had a list of deciding factors covering the most important areas of functionality and HaloITSM covered …
Verified User
Manager
Chose HaloITSM
Based on our requirements, this is how we scored them. Halo - 78, ServiceNow - 77, Ivanti - 67, Jira - 57, Freshservice - 41. This was based purely on our requirements and whether additional modules required additional licences.
If you want a value for money full system, which you could use out of the box then this is the one for you. If you want a system that can take care of tasks then this is the one for you. [HaloITSM] is easily scalable with very competitive pricing. New features are added regularly based on best practices and customer requirements.
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 Self Service Portal is very easy to configure and the end-users have commented on how easy it is to log and manage their own calls.
Asset and User Management works very well and it is simple to link them to tickets. Looking up ticket history for particular Users or Assets is also very useful.
The ability [to] use different ticket types and templates is fantastic. The added ability to merge and clone tickets is also a great benefit.
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've made overall positive experiences with the Halo support. The only thing to increase would be some follow ups on feature requests. If someone would reach out to me, telling me wheter or not my feature request will be considered in future updates or not.
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.
HaloITSM offered the highest level of functionality, available as standard, at our price level. Halo support during our trial period was second to none and unrestricted. We had a list of deciding factors covering the most important areas of functionality and HaloITSM covered all of these.
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.
It enabled us to allow our Service Desk Staff to work from home during COVID and this has continued ever since.
We have halved our average resolution time.
Some of the automation processes, when implemented alongside the MS Power Platform, have saved approximately 30 hours a month. This includes times when customers were unable to access the system until they had been trained. This is now automated via Halo and they get sent to on-demand training, instead of waiting up to 3 weeks for the next scheduled session.
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.
