Freshservice Reviews

FreshService is a simple to use system that has allowed us to manage IT issues, assets, and changes within a quickly growing company. Prior to the implementation of FreshService we were unable to appropriately identify our staffing needs or areas of concern due to the lack of ability to track issues across the entire organization. With FreshService implemented we're now able to put metrics to the volume of support our team provides to the company. We're tracking assets across multiple states. And we're tracking changes within our environment for SOC II compliance.

I wish there were some built-in features which made viewing issues by Location easier. Currently, it appears that Locations can be linked to Requesters which implies issues by Location. However, it would be ideal to be able to quickly see and change the Location the issue is occurring. This would lead to reporting mechanisms that would allow us to see which Locations have the highest number of issues.

The best thing about Freshservice is how simple and straightforward it is to use, both for end users and for the system administrator. Even first-time users will have no trouble grasping and implementing workflows because to the intuitive nature of the UI.

Since I use Freshservice on a daily basis for both my job and my company, and since it is so intuitive and simple to operate, I really can't think of anything bad to say about it.

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.

The ticketing system is really easy to use, with lots of options for workflow automations and ticket management. The app marketplace is great for extending the functionality.

FreshService seems more like a new branching out for the company, with a complete set of tools, but lacking refinement in a lot of places. There are also odd quirks like Discuss feature button being available, even though the Discuss feature doesn't work on FreshService yet.The mobile app is a bit of a let down, as it doesn't have a dashboard like the main site which makes it much more tedious to lookup ticket queues.The Notification spam through the app is terrible, pinging each notification one at a time to the phone, which is especially annoying when it sends over 30 notifications and doesn't group them.The system has some other weird quirks, like sorting a list can only be saved when you also make a change to the filter for the list. Another issue is that there is a blur effect on the title text that doesn't always go away when scrolling back to the top of the page, resulting in some text looking very soft and fuzzy

Collobration of tickets and task in incidents and tickets

Transferring of tickets from one instance to another instance

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.

Incident and Service requests is the module I like the most, specially because IT support can

Inventory and Software management.

The agent installed in workstations sporadically stops working and IT support must install the manually for it to continue reporting on the asset. When deploying hundreds of assets, this becomes very tedious.

Also, the Probe used to scan network and synchronize AD with Fresh lack a lot of functionality and it doesn't provide enough information about a multitude of non-workstation assets after scanning.

We use it for tickets and issue resolution mostly. The software offers contract management, project management, asset management and other features at a very basic state.

We tried asset management for a while and it felt extremely short so we had to switch to a different product. Project management we did not even try because it is extremely basic. Maybe they should stick with the core of their product which is tickets and issue resolution.

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.

Makes managing support very easy, love working with Fresh Service and the link to Jira works brilliantly

The searches could be a bit better if additional filtering options were added to narrow down the search when looking for historical tickets

Fresh Service is a breeze to get off the ground. The sandbox functionality is cute, but leaves a lot to be desired in terms of what is managed by the testing/deploying of the sandbox to production.

SSO User Provisioning is awful. We currently SCIM requesters into Fresh Service from Okta. It uses a third-party integration written by Effy? Why is user and group provisioning such a foreign concept in an already fleshed out application?