Freshservice

Probably the best tool for Help Desk Management

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

Zalety:

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.

Wady:

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.

Freshservice Review

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

Zalety:

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.

Wady:

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

Rozważane rozwiązania alternatywne: ServiceNow Customer Service Management, ManageEngine ServiceDesk Plus i Zendesk

Powody wybrania produktu: 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.

Przejście z: Cerb

Powody przejścia na produkt: Freshservice: Cost and ease of customization

La calidad es excelente

Komentarze: Nuestro producto anterior no contaba con un sistema personalizable y no proporcionaba a nuestros empleados una forma de seguir sus tickets una vez creados. También carecía de cualquier tipo de capacidad de elaboración de informes.

Zalety:

Me ha gustado mucho tener Frehservice en nuestra organización. Ha facilitado mucho mi trabajo como gerente, ya que puedo revisar fácilmente el rendimiento del equipo, publicar anuncios para la organización e identificar las tendencias de los problemas o las solicitudes.

Wady:

Desearía que las capacidades de informe fueran más personalizables. Ha habido algunas situaciones en las que me he puesto en contacto con Frehservice para pedir ayuda sobre los informes que necesitaba, pero me he encontrado con que los informes no eran posibles. El equipo de soporte de freshservice me dijo que mis necesidades de informes se añadirían a la lista de posibles "mejoras futuras".

No bang for the buck, an overpriced form submission tool that disappoints in reporting and integration

Zalety:

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.

Wady:

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.

FreshStatus Review

Komentarze: Good

Zalety:

GUI for users and technicians is easy to navigate.

Wady:

We use some other FreshWorks products, like FreshChat, and the switching between the 2 can be tricky.