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
Kayako
Score 1.9 out of 10
N/A
Kayako is a help desk / ticketing product and is available is both SaaS and on-premise configurations. Is is built in PHP and uses my SQL. The product competes with HelpSpot, ZohoSupport, Freshdesk and Zendesk.
The Kayako Engage edition may be deployed as a live chat system without ticketing at a reduced cost, featuring click-to-call and site visitor monitoring for customer targeting and engagement.
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.
When it works, It's without a doubt a great help desk solution. It is perfect for our usage, and have rolled it out company-wide. It's great if you have multiple departments. We have it set up so most items come through a single desk that then hands out tickets to their proper department. There may be cheaper options for smaller organizations but for one that is as service-driven as ours, we really think Kayako is a great fit.
Gives a very good report on an individual level of what is being done for a customer or corporate issue.
Easy to understand who has what, what the tickets are about, how long they have been opened and how many times the customer/employee have gone back and forth with each other.
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.
Departments need a bit of work. Even though you can have multiple departments, the only changes that can be made are globally. If you want independent queues within the departments, you have to do a lot of work that can be very confusing.
Survey system is not up to speed. Kayako really needs to add Net Promoter Score into their system. Also, if a staff user removes their name from an incident ticket, it removes them from the survey so you really can't even get a good estimate of how well your staff is in the eyes of the customer.
Very difficult to implement when you already have a customer base. Setting them up in organizations is difficult. Also, the sign-up for new customers is quirky. If you send an email to Kayako, it will say you are not an authorized user, however, it will store your email address. If you try to send an email a second time, it will go through. This is one of many reasons why we decided to move from Kayako to Oracle Service Cloud.
We are grandfathered in on their old Software-assurance pricing and our continued use costs us only a few hundred dollars a year (excluding hosting expenses)
Our team's processes are now heavily ingrained in the system
We have not been shown a more compelling option that is more cost-effective while still offering all the features we've come to expect
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.
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.
Three years in we are about as happy with Kayako as we could be. We've had several employee's leave and on-boarding new hires was easier than it has ever been as things are uniform and consistent across the entire application.
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
We were using Spiceworks for a few years before switching to Kayako but found that it wasn't as customizable or as user friendly for our customers. The SNMP scanning and inventory features with Spiceworks was nice but we needed more of a Help Desk that would allow us to scale our services to more companies.
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.
Tickets were definitely responded to faster once we implemented the audible alarm that would go off when new tickets came into the queue. This was possible because of the API.
Since the system was email based we could set our monitoring software up to generate tickets automatically via email for customers when it found something out of the ordinary.
