Freshservice

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)