We compared JIRA Service Management and Zendesk across several parameters based on our users' reviews. After reading the collected data, you can find our conclusion below:
Ease of Deployment: Opinions on the initial setup of JIRA Service Management vary. Some users found it uncomplicated, while others found it to be more complex and time-consuming. Zendesk's setup process was considered to be straightforward and effortless.
Features: JIRA Service Management is praised for its ticketing system, compatibility with Confluence, customization options, and reliable performance. Zendesk is highly regarded for its flexibility, strong security measures, user experience, and collaborative features.
Room for Improvement: Jira Service Management could add customization options, improve its time-based automation, and enhance the integration of its modules and DevOps tools. Zendesk could offer better asset centralization and implement an image-resizing tool. Users would like a better knowledge base and more analytics.
Pricing: JIRA Service Management is generally considered to be reasonably priced, but some users say the solution can become expensive when scaling up. Zendesk is considered expensive, particularly for the Enterprise plan. Users noted that additional services require extra payment and have suggested reducing the overall price.
ROI: JIRA Service Management provides financial advantages, reduced communication volume, improved productivity, enhanced transparency, and cost-effectiveness. Zendesk minimizes customer inquiries and delivers immediate ROI for small businesses.
Service and Support: JIRA Service Management users reported mixed experiences with technical support, whereas Zendesk's support is generally deemed satisfactory, with prompt response times.
Comparison Results: JIRA Service Management earned high marks for its ticketing system and user-friendly interface. Zendesk is praised for its customizability and robust security. The pricing of JIRA Service Management has received mixed reviews, with some finding it reasonable and others suggesting it could be more affordable, whereas Zendesk is considered expensive by certain users. The customer service and support for both products have received mixed feedback.
"Two features I like about Jira are its ticketing system and its compatibility with Confluence. Also, the Knowledge Base is one of the more valuable features that would really benefit us."
"The most valuable feature of the solution is its SLA, which everybody wants when it comes to a service-based offering."
"JSM's best feature is the integration with other Jira products."
"This service management solution has a good user interface. It helps improve your IT request requirements and makes tracking requests easier."
"Jira lets us customize the workflow to meet our requirements. The email and alert features are also handy."
"In Jira Service Management, the most beneficial features are process improvement, workflows, and escalations."
"The most valuable features of this solution are Incident and Request Management."
"Easy to use and user-friendly."
"It has good management, the ability to sign tickets based on content, the multi-channel support, the self service portal, the integration with Salesforce, the setup process, and the product features as we are currently using them."
"The product offers very good management. It has a great ability to assign tickets based on content."
"The stability has been very good."
"Its agility and simplicity are the most valuable features. This tool is very user-friendly."
"We rarely had issues with Zendesk."
"It is a scalable solution."
"What is cool about Zendesk Guide is how it works together with others Zendesk products. Especially with support and with the analytics. Put those together for a small or medium-sized company and it's a really powerful tool."
"Zendesk Support has a lot of good APIs."
"When you raise a ticket with Jira, there's no ability to see your other JIRA tickets."
"The customizations in Jira could be improved by being simplified. They are currently very complex."
"Every time there's a problem with JIRA Service Management, you have to have a look at how to solve it, and there's always a feature request or the feature request on the solution is too large and the development cycles are too slow."
"The initial setup is very complex."
"We have tried exporting some of the test cases into Jira from Excel. The interface for that isn't very user-friendly."
"The search function could be improved. We have to search a certain way. There is no generic search; it is more object-oriented search."
"I'd like to update the dashboard so that more features are available."
"There is room for improvement in support."
"You couldn't give administrative access to new hires."
"The dashboard could be better."
"If I write an article, and I have a team of 30 people, and they all have a Zendesk account, when I write an article, I send them an email. "Hey guys, I just wrote this article. It's one of the most popular topics this month on which we are not covered. Please check it and make sure that you include it in your resolutions". The issue is, once I send it to those 30 people, and they open it, the next morning, that article is the most popular article."
"The data you get when logged in to Zendesk Support differs from the data you get when you programmatically query Zendesk Support through its API because of a sync time delay."
"Zendesk Guide could be improved by allowing us to put our assets in one location. What happens now for each article, for example, is we have to upload the images for that article to that location, so the image reuse is still not something that they have perfected. If they could allow us to update all the images in one location, and then pull the image from there, it would be easier when working on Multibrand projects. There are no Multibrand updates available—we have to update each brand manually. For my company, I have come up with an API tool which allows me to push the content to multiple brands together, but if you don't have something like that, you have to manually do it."
"The price of the solution should be reduced."
"The solution could integrate better with QR codes from some websites such as Facebook."
"They have something called Zendesk Explore, which isn't as good as what they had in place previously."
JIRA Service Management is ranked 2nd in Help Desk Software with 73 reviews while Zendesk is ranked 11th in Help Desk Software with 57 reviews. JIRA Service Management is rated 8.2, while Zendesk is rated 8.2. The top reviewer of JIRA Service Management writes "Customizable, stable, and integrates well". On the other hand, the top reviewer of Zendesk writes "Stable tool, making it reliable for handling tasks but difficult initial setup". JIRA Service Management is most compared with ServiceNow, ManageEngine ServiceDesk Plus, BMC Helix ITSM, Freshdesk and IBM Maximo, whereas Zendesk is most compared with ServiceNow, Atlassian Confluence, Freshservice, Microsoft Dynamics CRM and Moveworks. See our JIRA Service Management vs. Zendesk report.
See our list of best Help Desk Software vendors and best IT Service Management (ITSM) vendors.
We monitor all Help Desk Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.