Freshservice

La calidad es excelente

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

Puntos a favor:

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.

Puntos en contra:

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

Probably the best tool for Help Desk Management

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

Puntos a favor:

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.

Puntos en contra:

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.

You can do a lot of great things with Freshservice

Comentarios: Complete platform for IT service management and reporting on client needs. It gives me the ability to develop material that can be provided as assistance to customers, as well as report back internally to the team and to top board management.

Puntos a favor:

I appreciate that it is not only affordable, but also demonstrates a lot of value due to the fact that it comes with a lot of features considering how much it costs. FreshService is capable of competing with ServiceNow in terms of IT service management, and I am accustomed to utilizing ServiceNow.

Puntos en contra:

The constraints placed on portal design, in addition to the requirement of having HTML coding skills. I have not been able to determine whether or not it is possible for us to have parent portal sites that include kid pages, and the process of developing these pages will require experience in coding.

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

Puntos a favor:

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.

Puntos en contra:

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.

A review about fresh service

Comentarios: A solid product with excellent qualities that can help transform how teams work

Puntos a favor:

Good tool for team collaboration. It is possible to configure workflows for each of them, projects, queues, etc. It is possible to greatly customize the fields and apply them to workflows, meeting specific needs.

Puntos en contra:

Graphing is a bit confusing, and you need to buy higher planes to use the best tools.

Alternativas consideradas: Zendesk

Razones para elegir Freshservice: Several limitations on the platform that did not allow workflows to be created as desired.

Software anterior: Jira

Razones para cambiar a Freshservice: We were very interested in other tools that perfectly met our need, however, its high cost made us choose Fresh.