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

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

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

Reasons for Switching to Freshservice: SysAid performance was not good. The technical support is not good either.

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

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

Pros: 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!

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

Alternatives Considered: Kaseya VSA, Zendesk, TOPdesk and Jira

Reasons for Choosing 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.