Freshservice is a cloud-based service desk and IT service management (ITSM) solution that currently serves more than 10,000 SMB, mid-market, and enterprise customers worldwide.
$29
per month per agent
Jira Service Management
Score 8.0 out of 10
N/A
Jira Service Management (formerly Jira Service Desk, now including features from the former Mindville Insight, acquired by Atlassian in June 2020) is a service desk software that is purpose-built for IT, service, and support teams. The software provides everything IT and support teams need out-of-the-box for service request, incident, problem and change management. Jira Service Management integrates seamlessly with Jira Software so that IT and development teams can work better together. Users…
ManageEngine ServiceDesk Plus was a good product that offered good value for money but its automation is quite poor for us and the support we received from them was very hit and miss. The product is also looks dated and has not changed much over the years. Jira Service …
Verified User
Team Lead
Chose Freshservice
We chose Freshservice because it struck the perfect balance between ease of use , modern design and enterprise grade ITSM functionality.
Price and ease of use was our main reason for going with Freshservice, also the implementation time compared to what I have used in the past was a big selling point
Freshservice's UI and UX scheme is much easier to navigate than other products. Most modules or configurations are easily accessible via the admin section and workspace management is segmented off from global administration, allowing for business units to designate their own …
Main reasons for choosing Freshservice where: - It has a user-friendly interface from agent use to configuration and administration. -High grade of customization options without a large use of external consultants.
As we are a smaller IT team, and a medium sized organization, we found most options for an ITSM to be more robust and overkill for our needs. Freshservice hit the mark in terms of features and pricing.
We used OTRS before Freshservice, and Freshservice is much easier to use and manage. We were checking on Service Cloud, as another branch of the company has implemented this, but there were a lot of features Service Cloud had problems with implementing that we take for granted …
Fresh Services was a turn key product that I did not have to take months to configure. We are a small organization and did not have the man power to undertake a product that would become a major project to get off the ground.
Freshservice was much faster to get up and going compared to Jira. And the user interface was intuitive and required little time to familiarize and start evaluating. Freshservice also offered competitive pricing for non-for-profit industry that we are in (Education)
Freshservice' beats ServiceNow and Jira Service Management on two key areas: user experience and ease of use (for both users and agents) and out-of-the-box readiness.
We found that both ServiceNow and Jira Service Management require significant configuration and building to get …
There were many good reviews about the product, and I must say Freshservice stood truly on those reviews. Freshservice offers a more modern and intelligent User interface as compared to other solutions available in the market, giving it a positive edge. Also, Freshservice is …
We found Freshservice to have the best balance between pricing and features. While you don't get nearly as many possibilities as with ServiceNow (e.g., the ability to build nearly any type of workflows from end-to-end), the solution is quite user-friendly with not much of a …
We went with Freshservice against Jira for cost efficiency. Freshservice was cost-effective for the same set of features that the Jira cloud offered. We wanted a tool to manage our patch testing test cases more easily without purchasing an additional plug-in as Jira and Fresh …
FreshService is easier to use and to train your team. It is cheaper too and the support it gives is really nice. You can feel that are not alone while you are setting up the portal and the feedback is very prompt. I do not say that the others are bad, but they really do not fit …
Student Health Business Systems Analyst / IT Operations
Chose Freshservice
We picked Freshservice over the others for many reasons. The first would be the ease of implementation. Another is due to the nice interface the system has. We also like the way we can push out a small piece of software to pull in the asset information for asset management. …
Brilliant for an ITIL Service Desk solution for use by IT department.
Can be used to manage incoming IT emails automatically ticketing them
and replying to users reducing work load of first line support. Can be
Freshservice is well suited for companies looking to implement ticketing / case management across the organization, but only if IT will be using it. Otherwise, I'd recommend Freshdesk. IT departments that don't function in the ITIL style of incident, request, change, and project management may find it overkill if they are only looking for a simple Help Desk solution.
I think using a ticketing system is very easy to use and allows multiple teams to create help desks in the same portal. In terms of internal usage, I think this is a great option. However, suppose you're trying to keep internal items and external helpdesks in the same instance. In that case, this is not ideal, as there is no effective way to separate the two instances to protect internal data better.
Integration with many of the most common tools companies are using (Slack, MS Teams, Salesforce, ... etc)
Natural workflow with Jira (as product development / project management tool) which makes the full fix and follow up of the tickets / issues very easy to follow
Allow multiple different entry points and work flows for as many different needs your teams / company have
To have more options on what to do with the emails that arrive in the support mailbox (which goes to Freshservice), Setting some special rules or detailed filtering is not possible.
Non 3rd party tools to connect to Intune are missing. Additionally, the third-party tool available in the store is not satisfactory. It would be nice to have native support for importing devices from our Azure cloud.
The contract requires you to prolong your contract end-date by two years instead of just one year, which to us is a bit aggressive.
We are pretty invested in Freshservice right now and have integrated it pretty heavily into our environment, so it would be hard to move away from it. For the most part, we are happy with Freshservice and the ease of use it gives us in managing tickets through the system. The only complaint we've had is customer service.
The UI design of Freshservice is simple and intuitive. You don't have to be a technical expert to navigate your way into the different pages/modules available. There are no buttons that are hidden in plain sight. Even our HR team required little to no help when they started using Freshservice.
If you're used to other tools in the Atlassian ecosystem, you'll feel right at home with JSM. It's also a platform that technical folk can easily pick up. However, I wouldn't recommend using JSM as a company's first jumping off point into Atlassian. There are a lot of other 'newer' tools that provide sleeker ITSM systems at a similar cost.
Most reports are quick, however, it can take some time for emailed exports to come via email. It would be helpful to have the exports live in the system rather than having to wait on emails.
Support from OEM is decent but needs improvement. Sometimes OEM also needs to understand the criticality of the customer and help as an Ad-hoc, which is somewhat lacking at Feshservice. Although the normal support team is well-equipped and helps according to the matrix, if something critical for the partner or customer requires immediate attention, it still goes through the L1-L2-L3 levels, which wastes a lot of time.
I gave JIRA a 9 rating since for me JIRA works according to its purpose. Since there is a customer portal, our clients can leave a comment or communicate with us using the PR ticket that way it is easier for us to also request any additional information we need for our investigation.
Their documentation is pretty good, but only available in English. This makes it difficult for some of our users to understand. There are also some basic video courses available.
Creating the correct groups for the stakeholders and enabling the right notifications are one of the most important aspect of the implementation. Creating Change templates will also help in the long run and it's a good practice to create one, if applicable.
Easy setup and a lot of customization which can be made. They offer the full ITSM tool for 75$ per agent and all the PRO are included in the package, which makes it easy to calculate and use. There are only a few add-ins that you need to pay for, based on the number of agents or the number of executions.
Zendesk is a similar ticketing system that our organization used before JIRA Service Desk. The main drawback of Zendesk was that it can only be used as a cloud service. This means that our company data would be living on the internet at the hands of their security team. Another drawback of this is the price is significantly more expensive rather than hosting it yourself. Zendesk does have some additional features such as commenting on multiple tickets at once that JSD does lack. However, switching to JSD was significantly more cost effective because we have the ability and the infrastructure to host our own ticketing system, something that Zendesk could not provide. Ultimatley switching to JSD saved us money and allows the ability for integration with all of the other Atlassian Suite products that we use on a day to day basis.