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.
"Jira Service Management is flexible. It is easy to navigate without requiring extra learning. The user experience has been good."
"It has improved our work in a number of ways. First, it has made everything much faster. Before Jira Service Management, it could take weeks to resolve a ticket."
"The automations will really help the company by delegating work the way your company operates."
"The most valuable features are the management tools."
"We have an Agile environment and using Jira makes it easy to adhere to Agile best practices."
"The visibility features are great."
"With Jira Service Desk, the simplicity of setting up a quick form and getting the service desk running quickly is very helpful."
"Useful for tracking issues with development."
"It's very convenient to use."
"The feature to move over my customer experience team tickets for different specialists is very valuable for my team."
"We rarely had issues with Zendesk."
"I found the user experience with vendors on Zendesk to be straightforward, especially when it comes to understanding and searching for specific tickets. The search and navigation tools are easy to use, and I haven't encountered any issues with delays or communication gaps in ticket resolutions."
"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."
"It is very easy to connect back and forth between the requester and the person fulfilling the ticket."
"One of the most valuable features is that Zendesk gives you a lot of configurability, and a lot of leeway in terms of customizing the look and theme. Zendesk offers you the facility to design your own landing page, as well as the look and feel of the entire knowledge base. At the same time, they offer themes that you can simply purchase and implement. Either way, it can really be turned into the right look and feel of the knowledge base required by our company, which is very important—if you have a bland-looking page, most of the time, people will lose interest. Zendesk also allows you to test the customizations before you publish it. It gives you a sandbox location where you can test everything new that you're trying to create and publish, which is very interesting."
"It's a very stable tool, very powerful."
"I would like to see improvement in the ability to filter completed tasks."
"With Jira, we were unable to implement time-based automation in its ticketing system. We would like a feature where we can define tickets based on severity, then tickets are automatically escalated to the next level after a set period of time if they go unanswered."
"It has change management and incident management, but CMDB is not there. It's also not as user-friendly as ServiceNow."
"This solution lacks features for project management."
"We have a lot of add-ons, however, instead of the add-ons, for example, cloning could be better."
"The product does not have the capability to sort queued tickets by product. This would be useful in making workflows more efficient."
"When you raise a ticket with Jira, there's no ability to see your other JIRA tickets."
"A lot of users have said that they want a feature that was on the on-prem version of Jira and the vendor can't deliver. They're either unwilling or unable to give feature parity."
"The support team is time-consuming, and they don't find the answer to our problem."
"The solution itself wasn't easy to set up."
"Zendesk Guide's customization could be improved. I would like it to be easier and maybe open-sourced, so that if you have a developer in your company, you can do it yourself. Right now, that isn't allowed, so you need to have it done via the integrator. Another improvement—this is nit-picking—is that it could be less easy to make changes. Some things are so easy that they sometimes look a little amateur-ish. Most of the templates are built-in so they can be used directly, so they are very simple."
"One of the drawbacks of Zendesk is that it doesn't provide a secure way for us to send data. So, we usually use a secure SharePoint folder link. We put that in the Zendesk ticket so that the requester has a secure way of getting to their data."
"The solution could integrate better with QR codes from some websites such as Facebook."
"The dashboard could be better."
"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 price of the solution should be reduced."
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, Freshdesk, BMC Helix ITSM 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.