Freshservice is a cloud-based service desk and IT service management (ITSM) solution that currently serves more than 10,000 SMB, mid-market, and enterprise customers worldwide.
$19
Per Month Per User
Microsoft Parature (Discontinued)
Score 5.0 out of 10
N/A
Parature was a self-service customer support platform providing a self-service knowledge base to connect with customers across multiple channels, including email, the web, chat or social media. The company was acquired by Microsoft in January 2014 and reached EOL in 2017. Former users are encouraged to migrate to Microsoft Dynamics 365 Customer Service.
Freshservice is a complete ITSM solution. I have used some others over the years and moved away from them to Freshservice. I have implemented Freshservice in 2 new roles over the years, and everyone has loved it. The functionality that it incorporates, enabling IT teams to become ITIL compliant is truly useful. Compared to 5 other ITSM tools that I have used over the last 10 years, Freshservice is far better.
The single element of Parature I've not seen in any other system of this kind is the Download Module. You can post files in the open, or protect them by any number of entitlement methods. The solution is also appealing to those who don't want to manage the back-end/IT needs as it is a hosted solution and has proven to be very reliable.
Clean/Friendly UI. It was extremely easy to navigate around Parature's menus at a high level, and you could take advantage of the more robust features as you became more comfortable and familiar with how Parature operates!
Strong Knowledge Base. Writing KB articles or ticket summaries and making use of the search function within Parature allows for expedient recovery of past ticket information. Being able to search for a fix action, or at least a troubleshooting article that can guide you towards a resolution is extremely valuable.
Enhanced Notation Capability. Being able to send/post internal or external updates to a ticket is great! You can leave the wordy technical details for other employees while making sure to communicate the high-points and fix action to the end-user.
Change Management - Current system is geared towards full software or system change management. It would be great to have a simple Yes/No approval without having to utilize their workflow tools.
Data selection filters - Overall, their data filters are very good, but it would be useful to have "Last Week" and "Last Month" in the date selectors.
Reporting is barebones at best. If you need special reports, we had to go through Parature to have them built.
The use of frames on a website is very 1990s. It actually impacts usability of the product, especially when combined with how Parature handled sessions. An engineer could only work one ticket at a time which, honestly, isn't very realistic for a busy support team that is working on several issues at a time.
Support was often unresponsive when contacted for unplanned problems.
The knowledge base was not very friendly for clients and it provided no real encouragement for it to be used.
It took several clicks to do something as simple as edit and assign a ticket or to close a ticket.
On the I.T. side, the time to ramp up and understand how FreshService operates only took a few hours. After that, it was off to the races with configuration and customization. From the start, with minimal assistance, our end users found FreshService to be incredibly intuitive. At launch, we expected most to submit tickets via email, however, our analytics has shown that end-users actually prefer the portal for managing their I.T. tickets.
It was bulky, cumbersome, and didn't allow us to handle the volume of cases we received on a daily basis. Many of our issues were highly technical in nature and we would often need to work on 2 or 3 at once. The poor design choices prevented this, which was unfortunate.
They recently had one very extended outage. It was a data center issue - but they were not diversified enough so in the end the system was down for almost 8 hours. There are also periods of time where for no reason the system simply doesn't respond. This small outages are usually short (just a few minutes), and have in fact been occurring less often, so it appears some corrective actions have been taken.
I contacted support once and the person handling the request was very helpful. The staff is very competent. In my opinion communication could be improved as the level of spoken English is very high. I was unable to understand some words, in fact two people participated in the second meeting.
think of what you want to do with FreshService : a clean start or a migration. Migration can be done with csv files, it's easy to do but you need to test it first.
I've used monday.com for ticketing, but Freshservice is made for it and the asset management feature adds value. NinjaOne's ticketing is not built out so we only use it for its RMM features. Atera has a nice ticketing platform and looks similar to Freshservice but they do not have an onboarding feature and other integrations that Freshservice has
Freshservice has allowed our organization to better track the amount of tickets that come in for a particular individual. This allows us to better support a user that is having multiple of the same issue over an extended period.
The communication to the user has greatly increased due to the automated messages that Freshservice has built in.
