Freshservice

Commentaires: My overall experience with Freshservice has been really good (despite the cons I listed). The interface from Agent point of view is easy to navigate, the ticket/problem/change management is clear. From an admin point of view, everything is well group under the admin section and even if you don't have experience with Freshservice you will find yourself picking everything up pretty quickly. The mobile app, while clunky, is still a good way to get notified about tickets coming in (especially urgent ones), and checking for replies and approvals. Bonus points for providing single sign on options (SSO). Customization is solid and allows you to integrate your company branding quite well. Good, and easy to create, manage, edit knowledge base system. Requesters have a very easy time creating a ticket in case of an incident. While it can feel frustrating to have to contact Freshservice support for some things, I can say that my overall experience has been very solid with their support and they have even taken and implement a number of our feature requests. I would most certainly recommend this product.

Avantages: - Easy to use
- Good platform to manage incidents/problems/changes/releases as well as requests
- Good CMDB for managing company assets
- Pretty simple to perform administrative tasks
- Good customization
- Has mobile app that will notify you when someone performs an action on any of your items (Such as assignment of a ticket, replies, approvals, etc.)
- Had good experience from Freshservice support staff
- Has the ability to integrate into your domain account via Single Sing-On (SSO)
- Good solution for storing your IT Support based knowledge base

Inconvénients: - Customization could be better in some areas
- Some changes require you to contact Freshservice support directly
- Digital asset management is a bit clunky
- Mobile app is not as intuitive as desktop experience and can feel difficult to navigate for some users
- Noticed that at times, usually in the morning hours of EST time zone, Freshservice access cuts out for 5 minutes

Commentaires: Moving from a shared mailbox it has been a lot easier to manage incoming incidents and track who is working on which ticket. Being an ITIL based ITSM we can now properly track system changes and gain approval across the business based on our business processes.

Avantages: Simple to use - one of the main reasons we went with FreshService was that during a trial of many other systems FreshService was by far the easiest to setup and configure. This means more time doing other projects rather than administering the helpdesk system. Powerful Automations - my trial version had the new Smart Workflow addon which made creating complex workflows very easy and simple. There is still room for improvement and some fields cannot be used in automations e.g. Impact or Urgency. Self service catlog - its a nice to have and allows easy segregation of Service Requests compared to Incidents, the custom forms are nice although would be better to dynamic i.e. drop down of all requesters for example. Branding - nice branding options and easy to use giving full access to CSS / HTML although not as easy to manipulate as ZenDesk. Self Service Portal - We haven't rolled this out to end users yet but the portal is easy to use and with the branding options can be customised. The embedded widget is also useful and can be embedded into SharePoint.

Inconvénients: Reporting - very limited compared to some systems although improvements are on the road map. Software Assets - confusing to use as you have to track each software item as an asset, cannot easily search on what is installed on computers across the database. Again improvements coming on the road map. Dashboard is useless - current implementation of the system gives a very basic overview of the system and an activity log. We don't use it as it doesn't provide any useful information. Certain Form Fields - you cannot change the default fields or even hide them without using JavaScript, this means I have had to create custom fields to tell my agents to ignore certain fields which isn't ideal. Also the categories list is shared among tickets, our change requests differ from our incidents. SLA breaches - compared to ZenDesk it isn't as easy to see when a ticket is due to breach SLA. Currently the ticket interface only shows Resolve Due date and not response due date, the response due just appears in the main ticket view when its close to expiry. Not ideal but workable.

Commentaires: We are back "with the times" compared to our previous ticket system.

Avantages: The FreshService interface is pleasant and pretty intuitive to work with. We had been using a different ticket system for more than a decade. Nonetheless, the switch to FreshService was relatively smooth for the whole team. I think the major reason is that the interface feels rather natural or comfortable to work with. The same kind of intuitiveness is also seen under the hood (Admin panel), which is where a lot of other systems fall short. Even though Fresh Service packs a ton of features under the hood, you are not battling against a maze of intertwined difficult-to-manage configurations. I personally don't need to do a lot of changes in the configuration (I'm rather the "backup" for those kind of things), but when I do, it doesn't take me too long to find out where I need to adapt what setting. I had to contact Fresh Service support a few times and so far always got a satisfactory reply in a decent reply time.

Inconvénients: With all of the above said, it also lacks some features you could see as "basic" or "take for granted" here and there. Agents can't configure an "out-of-office" period themselves.
There's no possibility to set up a custom dashboard per agent.
My major pet peeve is the text editor, which options are very limited (can't send a reply with a paragraph in fixed with font, can't edit the source ...) and which sometimes behaves unexpectedly (some odd behaviour with linebreaks, weird cursor position when pasting text ...) And finally, while there is integration with Jira, I have the feeling it tends to break quite easily. We've probably had it more half- or not-working-at-all than working as it should. This makes it unreliable, requires manual effort and follow-up and really undoes the usefulness of having integration at all.

Commentaires: The rapid deployment! Being Cloud, we were ready to start almost from day zero. The learning curve is quite smooth, and it was fairly easy to perform basic to moderate customizations on the portal and forms. Also the automation options were quite easy to follow (we basically used templates of the predefined ones) and one key for more novice users is that Freshservice has tutorials all around the solutions.

Avantages: It's literally "pay and use". Zero footprint in your current IT architecture, everything is habdled via any compatible web browser. And yet it includes advanced ITSM functionalities such as asset management and CMDB, in which you mdeploy Probes and Agents to Windows, Linux and Mac devices to scan and inventory hardware and software. And like every other Freshworks solution, it's very customizable interms of UI, automation and notifications, as well as integrations with third-party solutions and via API for developers.

Inconvénients: Perhaps adding new modules. Freshservice deals with this by integrations and automations, but out of the included modules (Tickets, Problems, Changes, Releases, CMDB, Projects, Solutions and Reports) you can't, at the moment, add a new one, such as Facilities or HR for example. However, provided that the included modules cover most, if not all, or ITSM's basic needs, and that the mnost generic modules (such as Tickets) are easily adaptable and customizable, that's not much of a problem.

Commentaires: The pricing for this product is very competitive which is great for the IT budget and value for dollar represent a good deal. I find the Support team is very helpful and responsive. This is not a complex product to set up but does take a little time to figure out how things work within Freshservice. I am very please overall.

Avantages: SaaS based product so no on premises hardware or software. Setup is more than 10 minutes that some of the marketing indicates, but definitely not a complex setup. Once you understand the workflow things become fairly intuitive in setting up the software. The ability to process tickets from one screen, enabling you to reply, enter case notes and disposition the ticket from one screen is very good. Like anything there is a learning curve involved, but it becomes very straightforward to Administer. This is very important as I am handling issues, closing tickets and assisting end users so I do not have the time to spent an hour a day doing routine maintenance tasks. The technical support team is also very helpful.

Inconvénients: Most of the issues have not been with things that do not work as much as do not conform to our individual work flows and processes. A few things that are challenges include that pasting into tickets using the portal does not work. Any screen shots or images depicting issues and end user is facing need to be added as attachments. By default you are given a long and not intuitive URL for your Portal. While you can create a custom URL it requires purchasing an SSL certificate or the connection is not secure. If a User submits a ticket via email and at a later time tries to create an account on the Portal it will advise them that the email is in use. To resolve this they just need to request a password reset, but it is not intuitive to the User, they think something is wrong.