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.
"I'm mainly working in the ITSM module of JIRA Service Management, and the integration between the system incident and how you can link all the records to the change makes it quite powerful."
"I like the precise ticket management capabilities. JIRA Service Management is easy to use as well."
"It's easy to set up the solution."
"JIRA SD also helps for much better feedback on the work being done. All colleagues can see what is happening."
"The simplicity is good for our clients. The price is good."
"The most valuable features are the flexibility of defining your own workflows and automation around the workflows, and the integration with the gate or any repository."
"Easily integrates with other tools."
"One of the best things about JIRA is that it searches for answers while questions are being typed so some tickets do not need to be submitted."
"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 the ease of use. If you take the standalone product, it is so easy to use, but if you want a tailor-made Zendesk Guide, you can't do it yourself. However, you can use a template that already exists—they have a lot, and they're very cheap, around 300-400 euros—and use it on all your brands. It's a very easy product to use."
"The most valuable features of Zendesk Support are collaboration, reports, and a self-service portal. The customer and team can see all the information needed from the portal."
"It is a scalable solution."
"Zendesk Support has a lot of good APIs."
"We rarely had issues with Zendesk."
"Its agility and simplicity are the most valuable features. This tool is very user-friendly."
"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."
"The product could improve its asset management."
"JIRA Service could benefit from improvements to its voice support."
"In-built chat is missing in JIRA Service Management."
"If JIRA were more of a substantial stand-alone product that covered more needs for project management, we wouldn't be using a suite of products."
"The customizations in Jira could be improved by being simplified. They are currently very complex."
"Include a split configuration in a layer part to allow cloud services to have almost full admin rights in SaaS."
"Initially, as a completely new user, the interface was not very user-friendly, with many cluttered options."
"They need to work on the speed of Jira."
"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 price of the solution should be reduced."
"The support team is time-consuming, and they don't find the answer to our problem."
"They have something called Zendesk Explore, which isn't as good as what they had in place previously."
"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 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."
"The dashboard could be better."
"Sometimes if there was a way to just flag the actual issue out of those email chains - that would be really helpful."
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.