Jira Service Management vs. Vision Helpdesk

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

I think that there is probably nothing that Vision Helpdesk can't do given enough work to customize it. The problem is that you almost have to have someone dedicated to knowing everything there is to know about the system and then have them be the administrator of all the customizations and feature additions you want. It's great that it can do so much, but it's not great that it's so complicated and has very little out-of-the-box configurations.

Incentivized

• 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

• The best thing for us - the timer. It's really cool. We can start the timer and end it when support finishes. It's very important for working with other companies we give support for.
• Good-looking, with good visualisation and usability dashboard.
• Ticket transfer between support users, comments, ticket printing.
• The best price and functionality, comparing to other help desks.
• Support. Best support I have seen on internet. Helped with setup, and helped with few minor questions.

• 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

• Chat feature.
• Remote desktop.
• Get more integration with other software and Mobile apps.

In the current contect the requirments is around having a tool that is focused and can handle large ticket volumes and tracking incident, problem and user requests concerning end users. Jira has built in functionality to address the above practice needs faily easily and has a substantial amount of customizable reports for generating the relevant intelligence.

Incentivized

For us it's really best solution.

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

Really simple, good-looking interface, many features and customizations

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.

Support from Vision Helpdesk was rather lackluster. We uncovered a bug pretty early on in our use of the system and it took them about a month to fix it. Our internal admin of the system had to keep pestering them to get it fixed. It wasn't critical to our business but was something we needed fixed and it just seemed like they didn't care that much about fixing it.

Incentivized

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

Vision Helpdesk was more open for an NGO while the other companies were more attended on the "big-money", which we don't have as an NGO. Second point is that Vision Helpdesk is very easy and simple to use. Not too much installation, programming etc.

Incentivized

• 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

• Most cost-effective help desk software I have researched from Kayako to SAAS [products] like Zendesk.
• We got more features and easy customization done with Vision Helpdesk which where not possible for Zendesk and Kayako was too costly.
• Ticket tracking has been easier and faster with Vision Helpdesk; for our web hosting business we prefer a download version which is not possible with SAAS help desk providers ( Zendesk or Freshdesk).