Freshservice

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

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

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

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

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

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