HaloPSA vs. Jira Service Management

Having been in IT for 10+ years and used so many different PSA platforms, I must say working with HaloPSA has been simply amazing. Straight out of the box, it's fast. It's feature-rich. It's easy to set up the basics, and the onboarding team was amazing. The onboarding team actually spends time with you, human on human, walking you through the setup and getting it working how you want. No one else does that included. Yeah, sure, you can pay CW and the other huge amounts of money, and they sort of help you, but HaloPSA helps you from the start; it seems they realise if they help set it up correctly in the first place, it reduces support calls. We can run our business from day one - very customer-centric. We have been using HaloPSA for a year now, and there is still plenty to learn and develop on the platform, but every week we are learning new things that we can do. The support team is great; they are humans who understand the issues we face, so they get things working fast. We have suggested some missing features to the dev team, and so far, they have implemented all of them - WOW. Don't get me wrong, as with all platforms, HaloPSA is not perfect. It's young, but it's maturing fast, very fast, and they are getting integrations built with the major players in the IT industry, which is fantastic. Yes, a few times, the link to Xero broke, which was annoying, but unlike the platforms we used in the past, the support team spoke to us and told us what the problem was and got it fixed, so you can't ask for more than that. Their growth has been fantastic to see, but again this has meant a bit of change around with account managers, support personnel, etc., but everyone they bring on is just as good as the last. All in all, migrating to HaloPSA was the best software/platform decision I have made in our business since I began the business. I would recommend HaloPSA to any IT business. Well done, Team HALO. Keep up the awesome work.

I think using a ticketing system is very easy to use and allows multiple teams to create help desks in the same portal. In terms of internal usage, I think this is a great option. However, suppose you're trying to keep internal items and external helpdesks in the same instance. In that case, this is not ideal, as there is no effective way to separate the two instances to protect internal data better.

Incentivized

• Workflows
• Stock Control
• Quoting

• Integration with many of the most common tools companies are using (Slack, MS Teams, Salesforce, ... etc)
• Natural workflow with Jira (as product development / project management tool) which makes the full fix and follow up of the tickets / issues very easy to follow
• Allow multiple different entry points and work flows for as many different needs your teams / company have

• Stock control
• There are 3-4 different ways to do that same thing
• Documentation

Incentivized

• Navigating through issues outside of a kan ban board can be confusing and task heavy.
• It's easy to clutter up the tool. It could use some easy clean up capabilities.
• User interface is decent, but could use work to make it more intuitive.

Incentivized

If you're used to other tools in the Atlassian ecosystem, you'll feel right at home with JSM. It's also a platform that technical folk can easily pick up. However, I wouldn't recommend using JSM as a company's first jumping off point into Atlassian. There are a lot of other 'newer' tools that provide sleeker ITSM systems at a similar cost.

Incentivized

I gave JIRA a 9 rating since for me JIRA works according to its purpose. Since there is a customer portal, our clients can leave a comment or communicate with us using the PR ticket that way it is easier for us to also request any additional information we need for our investigation.

We have used and tried several other PSA vendors and HaloPSA was our favorite by far. Many others were either much too overly complicated, clunky, slow to respond to issues, incomplete, or they simply failed to deliver on promises made, especially in terms of integrations.

Zendesk is a similar ticketing system that our organization used before JIRA Service Desk. The main drawback of Zendesk was that it can only be used as a cloud service. This means that our company data would be living on the internet at the hands of their security team. Another drawback of this is the price is significantly more expensive rather than hosting it yourself. Zendesk does have some additional features such as commenting on multiple tickets at once that JSD does lack. However, switching to JSD was significantly more cost effective because we have the ability and the infrastructure to host our own ticketing system, something that Zendesk could not provide. Ultimatley switching to JSD saved us money and allows the ability for integration with all of the other Atlassian Suite products that we use on a day to day basis.

Incentivized

• Improve our technicians efficiency
• Helped improve asset recording
• Knowledge base

• It is definitely cheaper than Salesforce
• It allows the IT service desk to be more organized and respond more quickly to tickets, which can save time for both agent and requester.
• Some things are "not quite there" developmentally, so this means that internal IT will need to spend more time developing and testing the product.

Incentivized