Jira Service Management vs. Zoho Desk

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

Zoho Desk is a great customer service tool. It is very easy to track the ability to receive tickets and send responses in Zoho Desk. There are lots of options for customization. The knowledge base feature is very extensive and powerful. It makes creating internal and external FAQs easy.

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

• It provides a simple widget code with a few clicks once you decide to integrate it with your website or application.
• There is a very user friendly dedicated mobile application for Zoho Desk for Android and IOS devices.
• You can easily track all of your tickets and agents from the dashboard interface.
• You can insert tags with each ticket to group them into specific categories for analysis and troubleshooting.

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

• The biggest drawback that I am facing while using the platform is that their ticketing system is not that great [in my opinion]. It does not give us the option to add sales tax and other charges in the invoices which leads to a big problem for us.
• [I feel] its customer support needs improvement.

Incentivized

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

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 give [Zoho Desk] [an] overall usability score of 9. This is partly due to the search functionality needs improvement. There are several times where I am left unable to find a ticket and have to generate a new one. I am hoping in the future that they will make some changes!

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.

As Zoho Support is based in a different timezone to ours it can be an issue that we cannot get an immediate response to an issue. But I will say that once their Support is in the office they are fairly good to respond. they have resolved almost all issues I have told them about, but Zoho have also made system changes and not communicated these beforehand which means we are faced with something new and cannot get support on this until their support team is in the office

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

We selected Zoho Desk as we needed a platform that was going to allow the business to grow through both usage and staffing numbers. We wanted something cost-effective but still offered standard features in an effective cloud-delivered solution but would still allow customization by our internal dev team, to derive better value from the service where it natively didn't do what we needed it to. FreeAgent was okay for a while, but Zoho Desk has allowed a vast improvement in our service offering to end customers.

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

• Zoho Desk has created an organised sytem of support which alows me to help my customers more efficiently.
• By saving resolutions as articles, Zoho Desk has provided a training resource for current customers and support staff as part of solving problems.
• All new customers become part of a database of customers who continue to receive support and education from forums created by the articles and customer questions.

Incentivized