We performed a comparison between Freshdesk and JIRA Service Management based on real PeerSpot user reviews.
Find out in this report how the two Help Desk Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Technical support is outstanding."
"I like that it's very user-friendly. The way they designed this application, any layperson can just do some drag and drop actions and use it. It's not that difficult. It's also easy to implement. The most important thing is, you don't need to go to this application to create a ticket. You just send out an email, and the ticket is created automatically. I have never seen a feature like this before."
"The feature that I have found most valuable is the way that it connects to various folders especially because we use it as a CRM tool. We can connect it with our phones and our chat, and also with the API and have it as an email service. Freshdesk just makes our life easier."
"It's easy to use and integrates with other tools. We can embed Jira into it, link Jira tickets with Freshdesk tickets, and use it for our knowledge base."
"It generated reports for us, which helped us identify the status of requests and the aging of requests."
"The most valuable features of Freshdesk are the automation of tickets to assign them to different agents, and the managing of documents is easy."
"Omnichannel is one of the most valuable features of the solution."
"The organization that is possible with other departments is the solution's most valuable aspect."
"We get software developed faster."
"I like the history, the dimensioning, and how I can configure a space based on my preferences or the project circumstances."
"The solution offers lots of information on the website to assist with technical queries. There are also many community sites to help you troubleshoot any problems."
"The SLA, speed, the comments from agents' side, and the dashboard for agents are the most valuable features."
"The simplicity is good for our clients. The price is good."
"The flow of the reports is good."
"The visibility features are great."
"I find the Kanban chart where we put each story in to be the most valuable feature. We use the Kanban chart to revise the project every morning in our five-minute meeting."
"We have many cases where a ticket comes in, and it ends up having multiple team members working on it. It would be really nice to be able to assign a single ticket to multiple people, rather than having to create the parent-child hierarchy that they have set up. It generates a proliferation of tickets that I really don't want to have. Having to jump from a parent to one child and then to another child makes it harder for me to be able to see the entire case from end to end. A simple example is our new hire process or our termination process. We have people who leave. We also have people who come on board. We have got multiple people participating and doing things related to the leaving or onboarding process. Currently, I have to go to different tickets to be able to see whether all tasks are really done or not. If I could assign lots of people to one ticket, it would be really nice."
"There aren't any features that we want to enhance, but we need to mature in our usage of some of them. I can't say any feature is missing or needs improvement, but a tool's built-in features need to evolve customer feedback. We have a dialogue set up for that kind of feedback."
"It should enhance its service and its reporting capabilities."
"If Freshdesk had forms in it so that I could go to the portal and fill out a service request, that would improve it immensely and make it more valuable for enterprise customers, but that's not a current functionality. You can't have a certain catalog of any type. You can't be like, "Hey, I want to just go submit a ticket," and then type in. You can't prompt them to ask anything. It is just a blank form."
"Having so many tags makes everyday work a lot more complicated, and a lot more time-consuming."
"There are a few things we have asked for, like a forward button. When a ticket comes in, we forward it, but it doesn't sync up with the forward. That is the one they have to rework. The other is when we forward the ticket, it doesn't go all, or certain things don't go with it. We have told them about it, and they are working on it. It would be better if they gave us a more standard reporting template. Although they already have some, many aren't usable. It would be easier if we had more templates to work with."
"Freshdesk could improve its capabilities. It's missing the article formatting, and the overall look and feel make it not easy to use. The administration instructions on how to manage the automation, capability, and integration with third parties, such as chat or bots, are very important in these types of solutions."
"For integrations, we need to write code that communicates with their system in order to enable certain functionality in the system. This is a lot of work for their customers."
"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."
"I don't think the program is very scalable."
"What needs to be added in Jira Service Management is the user screen. You'll find it very weird if this is your first time using the solution. The user-friendliness of its interface needs improvement."
"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 price is a point of contention for me. It does overall work out as a significant amount of money that will be spent over a shorter period of time."
"The queries are weak and lack advanced functionality. You can do rudimentary queries, but you can't aggregate. You can't filter for a lot of things that would be useful, so you need to use plugins to write writing advanced queries. I run into problems when working with different organizations because they always have restrictions on what kind of plugins they allow."
"I think the performance can be better."
"The main issue with this solution is there's no limited subscription available for plugins we only use for a few people. If we only have a team of twenty using a plugin, we still have to purchase a subscription for the whole 200 users."
Freshdesk is ranked 6th in Help Desk Software with 27 reviews while JIRA Service Management is ranked 2nd in Help Desk Software with 73 reviews. Freshdesk is rated 8.4, while JIRA Service Management is rated 8.2. The top reviewer of Freshdesk writes "Incredibly user-friendly, flexible, and affordable". On the other hand, the top reviewer of JIRA Service Management writes "Customizable, stable, and integrates well". Freshdesk is most compared with ServiceNow, Microsoft Dynamics CRM, Spiceworks, BMC Helix ITSM and TOPdesk, whereas JIRA Service Management is most compared with ServiceNow, ManageEngine ServiceDesk Plus, BMC Helix ITSM, PagerDuty Operations Cloud and Zendesk. See our Freshdesk vs. JIRA Service Management report.
See our list of best Help Desk Software 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.
