Online ITSM Service Desk with Incident, Problem, Change, Release & Asset Management, in addition to powerful ticketing & automation
It was easy to get started and allowed us to integrate into out ERP software to allow tickets from it.
I feel bad even complaining about it because it's so simple to use but I feel as if the interface could use an update.
Filter reviews (490)
Probably the best tool for Help Desk Management
Comments: This is probably the best I used for ticketing. The support is really good, the only bad thing is that you have to contact mostly via chat.
The features it provides are really good. The ticketing flow is easy to follow, we can handle our Service Catalog, integrate with Active Directory, manage Asset Inventory and now we started using the Project management tool.
The configuration (Initial Setup) is kind of complex. Design the flows is friendly, but complex if you have many rules, but the good thing is that support guides all the way during this process.
You can do a lot of great things with Freshservice
Comments: Complete platform for IT service management and reporting on client needs. It gives me the ability to develop material that can be provided as assistance to customers, as well as report back internally to the team and to top board management.
I appreciate that it is not only affordable, but also demonstrates a lot of value due to the fact that it comes with a lot of features considering how much it costs. FreshService is capable of competing with ServiceNow in terms of IT service management, and I am accustomed to utilizing ServiceNow.
The constraints placed on portal design, in addition to the requirement of having HTML coding skills. I have not been able to determine whether or not it is possible for us to have parent portal sites that include kid pages, and the process of developing these pages will require experience in coding.
Best ITSM / ESM tool out there
Comments: We are solving 1200 tickets a week with a team of 22, and automating resolution of 320 tickets a week using workflow automator. We were able to get up and running with Freshservice with only 3 months for planning, build and implementation.
- Very little initial configuration needed - features work out-of-the-box - User experience (UX) very very good - modern, quick and easy to use, looks great - Workflow automations and orchestrations allow significant and valuable automation with little work - Sandbox mode allows safely making and testing changes, and syncing them into production easily - Ticket approvals system works very logically and very well
- Sandbox sync sometimes fails and needs Freshworks support intervention - Only the main requester can access the ticket, and it's not possible to add others to see the ticket - No first-party SSO integration - we have to use a 3rd party plugin for SSO & SCIM which only syncs user attributes when they re-login - Agent permissions are not granular enough to allow us to lock down the number of admins as much as we want - WYSIWYG editor has quite a few quirks around new lines and styling
Alternatives Considered: ServiceNow
Reasons for Choosing Freshservice: - Jira Service Management requires significant building and configuration, and out-of-the-box Freshservice is pre-configured ready to go, and any configuration you do is a bonus, not a requirement. - Jira's user experience is very outdated and slow, wasting our agents' and requesters' time.
Switched From: JIRA Service Management
Reasons for Switching to Freshservice: - ServiceNow requires even more building and configuration than Jira, and requires programming using AngularJS, a now deprecated framework, and we would need to hire programmers who specialise in it and configuring ServiceNow - ServiceNow's user experience is also pretty outdated and slow compared to Freshservice
Great software, spotty support
Comments: I have had several tickets so far where the second level support team have sworn could not work or told me that the functionality is not possible, forcing me to push back on them. At this point they suddenly realise that the product can actually do what I have said all along it should, only a bug is in the way. On at least one occuration, they acknowledged a bug, spent weeks ignoring it, then when I asked for an update swore it wasn't a bug at all and I was just doing things wrong.... thus forcing me to escalate the case. In fact, on one occassion they submitted a set of incorrect repro steps, then blamed *me* for the mistake they made and told me there wasn't any problem!
FreshService is one of those frustrating products where the potential is so high and overall execution is done very well, but is let down by ridiculous bugs and even worse support. If Fresh could get to grips with this then I'd score them *very* highly. Unfortunately, they have not proven to be able to achieve this.
Reporting is dire. Bugs galore in modules you would not expect. Obvious features are missing, you try to work around them... and encounter a bug.
FreshService is Great but not consistent
Comments: It's amazing! it's just hard for me to hand over some of the responsibility due to the steep learning curve. Support could really do with arranging time to speak to you instead of email tennis, support can be slow but some agents are stella!
The way it can be used to report on bottlenecks and problem areas as well and programmed to tackle them is a game changer. It's great but you do have to know what changes impact others and I think it could be made more clear even for those with experience it wouldn't hurt and for those learning it would speed up the learning curve a lot.
Inconsistencies in user interface. Menus and options and ways of changing things differs on newer or older modules. Also the Employee Onboarding is great but a pain to adjust if you wish to change the Stakeholder order and initiators. Also linking to AD groups for requesters and agents would be ideal.
Alternatives Considered: ServiceNow
Reasons for Choosing Freshservice: KACE was old and lacked options. I had FreshDesk experience and suggested FreshDesk but we landed on FreshService which make FreshDesk look like BETA software.
Switched From: KACE
Reasons for Switching to Freshservice: Previous experience using FreshDesk and how it was beneficial to our needs.
Favorite ticketing solution so far
Comments: Overall I am very happy and don't have any plans to change the product
I have used several products before and Freshservice is by far the favorite because it has automation, integrates with many vendors and software that we currently use such as Dell and JAMF
The Admin setting section is hard to navigate through sometimes and hard to find settings I want
Alternatives Considered: Zendesk Suite
Reasons for Choosing Freshservice: Moved from an on-prem ticketing system to cloud. The previous product was not reliable and would crash often
Switched From: ManageEngine ServiceDesk Plus
Reasons for Switching to Freshservice: Better pricing and ticked all the requirements we were after
Freshservice is the best ITSM, our users love it!
Comments: After using several ITSM tools, Freshservie deployment was very easy and it fits 100% with our needs at an affordable price.
Ticket management is great by itself but if you uses it with workflow automation it's awesome. You can configure as many user portal as you want and it was a requirement. Inventory is also great module. Project management help us not only in the helpdesk team but also in other areas of the department.
The knowledge base could be better. You can't create more than two category levels and sometimes is not enough.
Reasons for Choosing Freshservice: OTRS was very difficult to configure and sometimes you couldn't find the way to configure it to fit with your requirements. Spiceworks is for little companys.
Reasons for Switching to Freshservice: It was the best option for us.
FreshService is great for IT ticketing, terrible for project management
Comments: I dislike this tool and am ready to find a new solution.
It has made our issue and service intake much cleaner and easier since we have a ticket users can submit requests through and it gets sent to our team members as required.
Our team has been using FreshService for over a year now, and while it has made our issue and service intake much cleaner and easier, it is awful to use for project management. It is not intuitive, we have to remember all sorts of details to ensure our message gets through to team mates' emails, the calendar is not helpful, and we waste time by using this tool.
Freshservice - Mid Tier, but power packed like enterprise IT ITSM tool
Comments: Love it. We utilize Freshservice for our corporate helpdesk ticketing system.
It is easy to create workflow and the navigation is easy to determine what you want to achieve / do. They have modernize the icons and look.
Integration with outlook is not there - .ics calendar, easy guide on whatsapp API business - omnichannel should be included by default from Garden plans onward
Reasons for Choosing Freshservice: Need to have a proper ITSM tool
Switched From: Microsoft SharePoint
Easy to use and flexible ticketing system
Integreting FreshService to our current processes has been really easy. The technicians find it easy to use, and the self-service portal has been easily adopted by the end user. We deployed it over 2 weeks, and are happy with its evolution since then.
It is not always easy to have appropriate support. We need to provide a lot of information for some bugs to be resolved, specifically when it is related to login issues.
Freshservice gives very accustomized service
Customer support is great, it is ease of use, and has very nice layouts in general.
For helpdesk customization some improvements are needed.
Good value and easy to implement and use
Comments: We have been happy with Freshservice and consider it a good value in comparison to some of the other Desks out there that provide similar service. We particular enjoy features like round robin ticket assignment, asset discovery and tracking, and providing a Knowledge Base for both Users (Requesters) and Agents.
We rely on the ticket system primarily to manage steps to resolution and archive past interactions and solutions. FreshService provides this functionality with little back-end effort on our part. Though somewhat limited, we do appreciate the ability to customize our portal.
Adding MSP's can be a confusing process. As it stands, you have to open a trial account then merge it into your main Desk. Last time we did this, FreshService failed to convert the account properly and we ended up being billed for the "trial" account. It took us several weeks to get the billing resolved. I recommend working with a live agent right off the bat to make this happen as smoothly as possible.
Reasons for Switching to Freshservice: Freshservice offered more features for less than comparable services. The Agent and Administrator online interface is also aesthetically appealing and easy to tailor to our needs.
A user-friendly all-in-one solution for the servicedesk
I am really happy I rolled out FreshService 2 months before Covid-19 forced all to work remote. We were able to support users from home ( IT was at home as well ) without issues.
FreshService contains a Solutions (knowledge-) base, users can request hard- and software like shopping online, very intuitive and user friendly
The ease to set it up : you can do it yourself without technical support. It comes with an app so it works on mobile devices as well, convenient if the laptop stops working.
You cannot change the webportal to your liking unless you have webdesign skills.
Alternatives Considered: ServiceNow Customer Service Management
Reasons for Choosing Freshservice: Costs
Switched From: TOPdesk
Reasons for Switching to Freshservice: Costs (yes, I'm Dutch..) the tool has it all and the ease of working with it.
FreshService Internal Ticket Management System for Gehan Homes
Comments: We enjoy FreshService for the simplistic ticket management and communication it provides. It is also a secondary database for our asset management to cross reference our main database. We would like to see more curated automated reports for both tickets and assets. We would also like to be able to levarage the change management database, but it does not appear user friendly nor intuitive; so we may need training on this but we do not use it because we dont understand it. We are actively looking for change management.
Easy to build requestors and submit tickets via email and communicate with the end users we support for our internal helpdesk. Easy to spot trends and ensure service level agreements for ticket response times are measured appropriately.
The inventory management system at first was very unreliable, sometimes search wouldnt pull up names or info. It seems to have been developed and works much better, but I believe the backend database or tool used could be of better quality. It has come a long way from the beginning and is markedly better.
Reasons for Choosing Freshservice: ManageEngine cost too much for what we were using it for and it was also on premises. We needed something simple and cloud based and cheaper.
Switched From: ManageEngine Endpoint Central
Reasons for Switching to Freshservice: Cost, ease of use, and provided the greatest benefit for a simple ticket and asset tracking system with the "possibility" of future developments in other areas of the system. We know FreshService was and is a growing company so we bet our money on the growth, we have not been disappointed, but of course would like to see more development in the areas of change management and maybe some more asset tracking features. Also, the customer service and support is STELLAR, I would say better than any vendor or product we use previously or currently. Bravo on the customer support, please never change how great that is, its more important than people might think.
Comments: I've really enjoyed having Frehservice in our organization. It has made my job as a manager much easier in that I can easily review team performance, post announcements for the organization, and identify trends in issues or requests.
Freshservice has been a game-changer for our organization. The service catalog and user-friendly interface has allowed our employees to improve their productivity over the past 2+ years we have had the system implemented. The customizable forms and workflow has allowed our IT department to streamline processes and improve efficiency.
I wish the reporting capabilities were more customizable. There have been a few situations where I reached out to Frehservice for support on reports I needed but found the reports were not possible. The freshservice support team told me my reporting needs would be added to the list of potential "future enhancements'.
Reasons for Choosing Freshservice: Our previous product did not have a customizable system and did not provide our employees with a way to track their tickets once created. It also lacked any type of reporting capabilities.
Switched From: Cerb
Reasons for Switching to Freshservice: Cost and ease of customization
Everything You Need In A Great Ticketing System
Comments: Excellent, see the Pro section. I wished I could paraphrase everything I wrote in that section to garnish this one, but time is limited.
There are multiple things that I like about the Freshservice platform. To start, the ticketing system that they provide is an amazing tool to keep track of issues and resolutions. You can easily search for similar issues and select a wide variety of categorizations to organize your problems and resolutions. I love the private note feature as well, we can suggest solutions to specialists working on solving an issue before it is escalated. Something else I liked about FS is their asset management utility. The Freshservice agent that is installed on the computers make it easier for admins to see who is the last person who signed in to a computer. This helpful in occasions where we have to rule out what computer is assigned to someone when we forget to update the asset. Overall, the Freshservice inventory system is the best I've used in my professional career. Now let's talk about my favorite feature - the API. I was surprised to learn that FS had an API. I was able to thoroughly test their API and develop our own apps. Very pleased with this aspect. I also enjoyed using their admin tools to create workflows, notifications, scenarios to automate and make the ticketing solution more effective. Being able to document things here is also very easy. You can add images, create tags, and alter publications from their editor. Never had any gripes with this. Lots to like here!
There are actually very few cons. If there is anything bad to say is that I wished the API returned some more relevant results for what I was looking for. For example, I had to jump through a few more requests that I wanted to convert some values to get something else I needed. Yes, seriously, that's all the bad I can say; we are nerds here at Royal. I was able to code very cool apps with the API.
Implementation and Management
Comments: I had used FreshService in the past at different places of employment and had enjoyed it. This was the first time I was tasked with picking a ticketing system for a company. The fact that you get a trial based on the level you want to pay for, can basically have it customized during the trial to see if it's the right fit, extremely helpful and responsive customer service, and its easy to use for all levels of tech comfortability were the big reasons we chose FreshService. Every time I check in with our team of Agents, everyone is extremely happy with the switch and, overall, I am looking forward to the positive changes this is bringing our teams.
There are several reasons I pushed to choose FreshService over other products. The value of the features I was getting with the ease of set up. Within the trial period, I had most of the set up done before I presented to my department head. The ease of switching from the previous (and archaic) system to FS for our end users was, overall, seamless. The ability to customize the product with minimal knowledge makes it easy to manage and make changes. After reviewing a dozen other ticketing systems, FreshService provided the ease of implementation and change that we were looking for.
I love Freddy and want to use it however it's limited features over the traditional portal are frustrating. I understand it's a new feature and it's in a state of constant improvement but I wanted to launch with it and was unable to because key features that we needed specifically for our company would not show up. The reports aren't quite what I thought they would be either and I will probably have to do some work with powershell to get the information I really need.
Reasons for Choosing Freshservice: The system we had was a basic portal for entering the request and then it would email it out to everyone. There was no way to properly manage, track, or pull reports on the work being done and tickets were falling through the cracks. It was making everyone's job harder than it needed to be.
Reasons for Switching to Freshservice: This list is only a partial list of all the systems I looked at but I had issues with identifying what features each level had, lack of trials, unresponsive or slow customer service were some of the few issues I ran into.
Freshservice Review from a daily user and admin
Comments: My overall experience with Freshservice has been really good (despite the cons I listed). The interface from Agent point of view is easy to navigate, the ticket/problem/change management is clear. From an admin point of view, everything is well group under the admin section and even if you don't have experience with Freshservice you will find yourself picking everything up pretty quickly. The mobile app, while clunky, is still a good way to get notified about tickets coming in (especially urgent ones), and checking for replies and approvals. Bonus points for providing single sign on options (SSO). Customization is solid and allows you to integrate your company branding quite well. Good, and easy to create, manage, edit knowledge base system. Requesters have a very easy time creating a ticket in case of an incident. While it can feel frustrating to have to contact Freshservice support for some things, I can say that my overall experience has been very solid with their support and they have even taken and implement a number of our feature requests. I would most certainly recommend this product.
- Easy to use - Good platform to manage incidents/problems/changes/releases as well as requests - Good CMDB for managing company assets - Pretty simple to perform administrative tasks - Good customization - Has mobile app that will notify you when someone performs an action on any of your items (Such as assignment of a ticket, replies, approvals, etc.) - Had good experience from Freshservice support staff - Has the ability to integrate into your domain account via Single Sing-On (SSO) - Good solution for storing your IT Support based knowledge base
- Customization could be better in some areas - Some changes require you to contact Freshservice support directly - Digital asset management is a bit clunky - Mobile app is not as intuitive as desktop experience and can feel difficult to navigate for some users - Noticed that at times, usually in the morning hours of EST time zone, Freshservice access cuts out for 5 minutes
Feature packed ITSM which has room for improvement.
Comments: Moving from a shared mailbox it has been a lot easier to manage incoming incidents and track who is working on which ticket. Being an ITIL based ITSM we can now properly track system changes and gain approval across the business based on our business processes.
Simple to use - one of the main reasons we went with FreshService was that during a trial of many other systems FreshService was by far the easiest to setup and configure. This means more time doing other projects rather than administering the helpdesk system. Powerful Automations - my trial version had the new Smart Workflow addon which made creating complex workflows very easy and simple. There is still room for improvement and some fields cannot be used in automations e.g. Impact or Urgency. Self service catlog - its a nice to have and allows easy segregation of Service Requests compared to Incidents, the custom forms are nice although would be better to dynamic i.e. drop down of all requesters for example. Branding - nice branding options and easy to use giving full access to CSS / HTML although not as easy to manipulate as ZenDesk. Self Service Portal - We haven't rolled this out to end users yet but the portal is easy to use and with the branding options can be customised. The embedded widget is also useful and can be embedded into SharePoint.
Feature-rich and intuitive
Comments: We are back "with the times" compared to our previous ticket system.
The FreshService interface is pleasant and pretty intuitive to work with. We had been using a different ticket system for more than a decade. Nonetheless, the switch to FreshService was relatively smooth for the whole team. I think the major reason is that the interface feels rather natural or comfortable to work with. The same kind of intuitiveness is also seen under the hood (Admin panel), which is where a lot of other systems fall short. Even though Fresh Service packs a ton of features under the hood, you are not battling against a maze of intertwined difficult-to-manage configurations. I personally don't need to do a lot of changes in the configuration (I'm rather the "backup" for those kind of things), but when I do, it doesn't take me too long to find out where I need to adapt what setting. I had to contact Fresh Service support a few times and so far always got a satisfactory reply in a decent reply time.
With all of the above said, it also lacks some features you could see as "basic" or "take for granted" here and there. Agents can't configure an "out-of-office" period themselves. There's no possibility to set up a custom dashboard per agent. My major pet peeve is the text editor, which options are very limited (can't send a reply with a paragraph in fixed with font, can't edit the source ...) and which sometimes behaves unexpectedly (some odd behaviour with linebreaks, weird cursor position when pasting text ...) And finally, while there is integration with Jira, I have the feeling it tends to break quite easily. We've probably had it more half- or not-working-at-all than working as it should. This makes it unreliable, requires manual effort and follow-up and really undoes the usefulness of having integration at all.
Freshservice Helpdesk/Asset Management Review
Comments: Overall experience has been great. The product continues to evolve as well.
This software is easy to integrate with other 3rd party applications. It allows for ticket/service automations that can streamline workflows. Asset Management is extremely useful and easy to setup as well.
Wish you could get more granular with group/user permissions. In some cases, it's all or nothing.
Alternatives Considered: ServiceNow Customer Service Management
Reasons for Choosing Freshservice: Freshservice had many more features available. It was the right choice to fit our growing business.
Switched From: Spiceworks
Reasons for Switching to Freshservice: Functionality and Price
Easily worth the price compared to other ticket systems.
After following a demo given by enthusiastic and cooperative Freshservice employees, we were sure of our choice. The tooling is intuitive, user-friendly, responds quickly and very easy to set up. There are plenty of things that can be adapted to the needs of the company. There are a number of options within the tooling that have certainly increased the efficiency of our employees and in the way customers create their own tickets. The support and technical staff are excellent and an example for other companies!
The change module may be further expanded. A feature request has been created for this and the latest information shows that a number of improvements will be made this year.
Reasons for Switching to Freshservice: Before Freshservice, we used a tooling that was almost unusable, slow and cumbersome to use. No more innovations were made. The switch to Freshservice was a relief for our users, but certainly for our customers. Where we regularly received complaints about our ticket system before using Freshservice, we no longer receive any complaints.
Good, but not quite great
Comments: FreshService is definitely an improvement over our previous system, and we like it, but it's not all it could be. That said, they make frequent updates and are noticeably trying hard. It's a good solution for the money, but if you have the budget and want robust project management, change management, knowledge base, asset tracking inventory features, there are likely better solutions
The FreshService implementation team was very easy to work with and provided excellent customer support. They did a great job of keeping us on the timeline we had set. General tech support is very good as well. I always get a response within a day. I've also enjoyed working with their robust API so that I can make customizations. The ticketing system, which is by far the most commonly used feature, is excellent.
A review about fresh service
Comments: A solid product with excellent qualities that can help transform how teams work
Good tool for team collaboration. It is possible to configure workflows for each of them, projects, queues, etc. It is possible to greatly customize the fields and apply them to workflows, meeting specific needs.
Graphing is a bit confusing, and you need to buy higher planes to use the best tools.
Alternatives Considered: Zendesk Suite
Reasons for Choosing Freshservice: Several limitations on the platform that did not allow workflows to be created as desired.
Switched From: Jira
Reasons for Switching to Freshservice: We were very interested in other tools that perfectly met our need, however, its high cost made us choose Fresh.
The best helpdesk software I have used
Comments: Built-in approvals and automation were our most important needs, following that we wanted a system that integrated well with our asset management system or was capable of outright replacing it (which is pretty much what happened).
I love the automation and customization that is possible.
The only cons are that there is some minor missing functionality with automation (for instance, automatically creating a new ticket based on the properties of an existing ticket). I would still say it meets 99% of our needs though, so my only complaints are just nitpicks.
Reasons for Choosing Freshservice: We needed more robust functionality and the on-prem version of Spiceworks was no longer being supported. With our desire for automation and approvals workflows, Freshservice was an obvious step up.
Switched From: Spiceworks