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 7.9 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…
$0
per month
ManageEngine ServiceDesk Plus
Score 9.3 out of 10
N/A
ServiceDesk Plus is free help desk software from ManageEngine, a division of Zoho Corporation.
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 is on par with ManageEngine SD Plus in terms of: 1. No/Low code configuration, 2. ITSM module certification 3. SLA 4. CMDB etc. However, the level of support that ManageEngine offers with its post-sales engineer is better than that of Freshservice. While using …
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 …
The user-interface, Marketplace, out-of-box Orchestrations and ability for Admins to perform product specific configurations at much easier and faster pace is a much loved feature of Freshservice, when comparing it with other ITSM solutions.
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 …
Freshservice is much faster and sleek and easier to use. if you want easy setup go with Freshservice. if you want to have clunky, hard to edit, etc. go with ManageEngine. The problem is ME has too much stuff it offers and not enough room to fit it.
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
JSA has specific focussed technical verticals concentrating on ticking and service desk features such Incident management, Service request management, Problem management, Configurations management, Serivce desk, End user mobile app, Performance dashboards, Cutom reports, …
Jira Service Management is one of the strongest rival of Manage Engine Service Desk Plus. If we compare, both of them are really good for incident management and workflows. But when time to decide, Manage Engine Service Desk Plus is front of Jira Service Management with a few …
Verified User
Manager
Chose ManageEngine ServiceDesk Plus
We are actually moving away from ServiceDesk Plus to JIRA Service Desk. This is because of the flexibility that JIRA offers versus the more "locked in" fields in ServiceDesk. It also is going to allow us to better customize our requests and track our SLAs on different types of …
We use JIRA and Spiceworks in different departments in our company, but neither had the features we were looking for when it comes to end user facing help desk solutions. JIRA is great for our coding/development teams but it doesn't have the ease of use that service desk plus …
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.
ServiceDesk Plus is very easy to configure at the start, and then adjust the categories and rules as the implementation is refined. Its greatest strength is the ability to program without requiring a full time administrator. There is very little jargon involved. Reporting not so much. The canned reports are useful but do not always cover some of the basics. Fortunately, the user groups freely share report definitions so one could springboard from something close to your desired result.
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
Ticket logging for end users, so they can see the progress on their help requests
Asset management; it has an agent that can be installed on machines which can then feed back information on installed software, active times, logged on user etc
Project management; larger projects can be managed within ManageEngine ServiceDesk as well as end user help tickets, where progress/milestones etc can be recorded
Active Directory import of users, so that it automatically updates when users are created/deleted and links their accounts in ManageEngine ServiceDesk with their email address as well to enable email alerts
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.
When trying to select the top row ticket, you have to be careful not to select all tickets. Happened to us twice and we assigned all open tickets to one technician. Took a few minutes to correct.
Site is sometimes a bit sluggish to respond. Don't know if that is an issue with our network infrastructure or the program itself, though.
When users send emails to the help desk, we sometimes experience delays until the tickets appear on the site for the technicians.
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.
In the current contect the requirments is around having a tool that is focused and can handle large ticket volumes and tracking incident, problem and user requests concerning end users. Jira has built in functionality to address the above practice needs faily easily and has a substantial amount of customizable reports for generating the relevant intelligence.
we are looking at other tools like Zendesk which may replace ServiceDesk. We are currently evaluating both tools to see which one would serve our needs better
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.
It is still very cumbersome, lots of data entry on the back end to build how we want it but it is still not completely user friendly. Many functions still dont work and contacting someone for help isnt always easy or we get told solutions for issues we have just arent built yet.
In our 3 years of using Freshservice, we've experienced several outages in the first 2 years. There were times where it only took minutes or hours but there are also times where it took a few days. Each time, Freshservice remained transparent and constantly communicated their progress. We haven't had one in the past year which indicates Freshservice have improved their servers.
Pages load quickly but internet connectivity can also play a big role. Integrations doesn't affect the performance but internet connectivity may be a big factor. As a company with most employees working from home, different network providers from different areas/countries can have different experiences. Search load time needs improvement.
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.
Our network administrator usually gets a good response when contacting ManageEngine ServiceDesk Plus customer service. They are quick to respond and so far have been able to eliminate most of our issues. We have been through several upgrades of the software over the years and have no issues to report in regards to customer service.
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.
Spiceworks was free, which obviously had both benefits and limitations - I will say that the community around Spiceworks has always been great. If we could replicate that experience with the ME user base, it would be terrific.
Freshservice allows flexibility with contract terms and pricing model. Monthly and annual payments are allowed. The unit pricing needs a bit of improvement. It would be great if they offer unit pricing per capability instead of one pricing for all the capabilities. Small businesses have different use cases and not every agent needs all the modules available.
We were able to scale easily across multiple departments. As our company keeps growing, we have not needed to change anything in terms of scaling since we started using Freshservice. There were no changes to the admin and end-user experience from when we were a 1,000-employee company vs to our current head count of 2,000+.
The tool does not scale well from an ROI perspective. As you add a customer, you must add a new instance, hence a new license.
The tool is probably on the expensive side (34,000 USD per 130 technicians per year).
There is no usage beyond incident, change, and problem management. The CMDB feature is extremely limited and cannot generate additional ROI. There is no knowledge-base or integration with other software (other than ME Desktop Central).