Freshservice Erfahrungen

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.

Friendly user interface.
Copy screenshots directly into the form (although there's a bug for the last 3 months that screenshots are displayed double in edit mode.)
Plenty of fields to configure for more complex workflows.

Default categories and labels with awkward naming (synonymous use of "Tickets" and "Incidents" for "Issues", "Change" for "Change Request", "Problem" for "Bugs")
No possibility to convert issues to change requests. Agent needs to recreate the entire case in the back resulting in significant adminstrative overhead.
Reporting is practically inexistent.
REST API not covering many functions and object attributes. (You cannot substitute reporting externally.)
HTML editor limited and bugged. (CSS code in support articles not supported, Bootstrap not supported, code gets changed or reformatted upon saving articles)
No access to the file and image repository.

Frankly, with every new cosmetic change and "functionality no can do" message from the Team, I am growing more and more wary of this application. At this point, I am thinking of it as an overpriced form tool with practically no reporting, a gimped Knowledge Management base, and an asset list functionality that quickly drains your wallet.
I am spending significant time rewriting issues as change requests in order to subsequently manually attach them to the original issue ticket and explain to the user why I would want to close his ticket after all. Writing knowledge articles is best done in a separate HTML editor. The Text Editor lacks basic functionality, removes formatting and images in unpredictable ways with undoing, and stores images and files in a central repository you have no access to.
You might as well do that with a forms tool readily available on the internet.

Freshservice contained the features and ability to meet our help desk, ticketing, and purchasing needs.

Time Tracking and Interface to Billing System(s)

Ticket System workflow is the best to use.

it is a learning curve to use the workflow

easy way to customize for our needs, All needed functions are in place, easy to handle

a good an helpfull too in my role as a service desk Teamleader.

Easy UI. It is intuitive for first time users. Creation of Projects and umbrella ticket is another feature I like a lot.

Notification can be improved. So far emails are the only way I get notified. If we can add a ping to MS Teams it would great.

Feature to create ticket for a problem in the system and overall check with all the customers.Customers can create ticket for us to attend easily and help them.

All the features that i would want in a help desk app is available with Fresh Service.

Fresh Service is neat and easy to navigate. When it comes to the ticketing system, you have various options to work with and can link it to other modules.

We could not create a custom place holder that we can use on canned responses, workflow, etc.

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 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.

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

Freshservice has most of the features you need. It's customisable and expensible to a point which allows for other features to be added.

Some of the UX can be frustrating. The search is very lacking and often doesn't find the results you need. The "Solutions" feature for knowledge management is quite basic and can be frustrating to use.