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.
"Provides excellent management features."
"This is a flexible tool for logging and tracking issues efficiently."
"The links between the help desk and Jira issues and between Confluence and Jira issues are most valuable. I can write requirements in Confluence and link them to user stories in Jira and test cases. I can see my test coverage and all that kind of stuff. The integration between these three is very useful. It is pretty customizable, and it integrates well. There are a lot of add-ins and a lot of connectors to third-party products. In my last company, we used Test Royal for managing all the tests, and it integrated perfectly with that. For any issue or bug, we could see what tests have been run and the complete history of the tests."
"The customer portal with connection with our knowledge base has been most valuable."
"Easily integrates with other tools."
"The initial setup is pretty easy."
"The simplicity is good for our clients. The price is good."
"What I really like about this solution, is how it manages the queues, the tickets and the routing."
"The feature to move over my customer experience team tickets for different specialists is very valuable for my team."
"The initial setup is simple and straightforward."
"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."
"It is very easy to connect back and forth between the requester and the person fulfilling the ticket."
"It's a very stable tool, very powerful."
"Its agility and simplicity are the most valuable features. This tool is very user-friendly."
"It is a scalable solution."
"Zendesk Support has a lot of good APIs."
"In-built chat is missing in JIRA Service Management."
"The product could improve its asset management."
"I'd like to update the dashboard so that more features are available."
"The way it handles subtasks can be improved. We would really like the ability to have different types of subtasks. If we have a user story for a feature, we would like to have a subtask for documentation, a subtask for requirements, a subtask for development, and a subtask for testing. Right now, we just make four subtasks, but there is no way to specify their type, so we have to add a custom field to specify what type of work is this. It just means you've got to look at more data. For logging time or time tracking, we would like to have something using which we can define the work type we're doing. We would like to log whether we're working on a bug, a new development, scope change, or rework. We've got a user story for which we do the dev, and then we have to do more dev. It is the same story, but some of it could have been a scope change, and some of it could be a rework because we either screwed up the first time or missed something obvious. Currently, we have to have a custom field and track that separately. It would be nice to have some kind of work type for logging time."
"The initial setup is very complex."
"The deployment can be a bit complex, especially for those who are not technical."
"The interface could always be updated and improved."
"JIRA Service could benefit from improvements to its voice support."
"It wasn't easy to set up so we're only using a third of all of the features,"
"The solution itself wasn't easy to set up."
"The dashboard could be better."
"There is always a network issue with Zendesk. But we don’t know whether it is managed. The network issue is that when I call, it does not let us."
"The solution could integrate better with QR codes from some websites such as Facebook."
"As per me, there arent much significant issues or areas for improvement with Zendesk, as my usage of it is limited. I appreciate its ability to organize tickets effectively based on tags, allowing me to easily gather and analyze customer feedback and requests."
"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."
"It needs to improve in terms of its flexibility, price, and installation."
JIRA Service Management is ranked 2nd in Help Desk Software with 73 reviews while Zendesk is ranked 10th 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 "Straightforward, very transparent, and very well organized". JIRA Service Management is most compared with ServiceNow, ManageEngine ServiceDesk Plus, BMC Helix ITSM, Freshdesk and Freshservice, 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.