Freshservice

Best product for ITSM

Kommentit: Great experience

Hyvät puolet:

Easy to use for complaints, issues track, asset management, inventory purposes

Huonot puolet:

Nothing to dislike for this product from my end

Freshservice Review

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

Hyvät puolet:

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.

Huonot puolet:

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

Huomioon otetut vaihtoehdot: ServiceNow Customer Service Management, ManageEngine ServiceDesk Plus ja Zendesk

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

Vaihdettu kohteesta: Cerb

Perusteet vaihtaa tuotteeseen Freshservice: Cost and ease of customization

La calidad es excelente

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

Hyvät puolet:

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.

Huonot puolet:

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

Hyvät puolet:

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.

Huonot puolet:

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.

Implementation and Management

Kommentit: I had used FreshService in the past at different places of employment and had enjoyed it. This was the first time I was tasked with picking a ticketing system for a company. The fact that you get a trial based on the level you want to pay for, can basically have it customized during the trial to see if it's the right fit, extremely helpful and responsive customer service, and its easy to use for all levels of tech comfortability were the big reasons we chose FreshService. Every time I check in with our team of Agents, everyone is extremely happy with the switch and, overall, I am looking forward to the positive changes this is bringing our teams.

Hyvät puolet:

There are several reasons I pushed to choose FreshService over other products. The value of the features I was getting with the ease of set up. Within the trial period, I had most of the set up done before I presented to my department head. The ease of switching from the previous (and archaic) system to FS for our end users was, overall, seamless. The ability to customize the product with minimal knowledge makes it easy to manage and make changes. After reviewing a dozen other ticketing systems, FreshService provided the ease of implementation and change that we were looking for.

Huonot puolet:

I love Freddy and want to use it however it's limited features over the traditional portal are frustrating. I understand it's a new feature and it's in a state of constant improvement but I wanted to launch with it and was unable to because key features that we needed specifically for our company would not show up. The reports aren't quite what I thought they would be either and I will probably have to do some work with powershell to get the information I really need.

Huomioon otetut vaihtoehdot: HappyFox Help Desk, Jitbit Helpdesk, Zoho Desk, JIRA Service Management, ServiceNow, Kayako ja Zendesk

Perusteet valita Freshservice: The system we had was a basic portal for entering the request and then it would email it out to everyone. There was no way to properly manage, track, or pull reports on the work being done and tickets were falling through the cracks. It was making everyone's job harder than it needed to be.

Perusteet vaihtaa tuotteeseen Freshservice: This list is only a partial list of all the systems I looked at but I had issues with identifying what features each level had, lack of trials, unresponsive or slow customer service were some of the few issues I ran into.