Freshdesk is a cloud-based customer service software that helps businesses of all sizes to deliver customer support.
Freshdesk converts requests coming in via email, web, phone, chat, and social into tickets, and unifies ticket resolution across channels. Additionally, Freshdesk lets the user automate workflows, provide self-service, manage SLAs, and measure metrics, to stay on top of customer support. Freshdesk also offers out-of-the-box features like an AI-powered support chatbot,…
$0
Up to 10 agents per user
Kayako
Score 2.0 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.
Using a collection of Skill Based Ticket Assignment, Ticket Allocation, and alerts, we’ve been able to bring our average resolution time to under half our previous time. This is done by making sure the right tickets get to the right agents, and by ensuring agents are followed up on to ensure they do not forget deadlines on tickets in their queue. Furthermore, tickets which would be open for weeks due to lack of a client response are now closed automatically following a prompt email to the end-user
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.
Follow up on all conversations that enter and are easy to use by the employee and save responses ready for use.
Find out the average rate of the number of conversations that occur in the company and conduct the analysis.
There is a feature it allows one to take a permit in the name of the employee who responds to the conversation and to know the problem faced by the customer and the solution.
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.
Ticket templates and canned responses should be able to be used interchangeably. We frequently have the same response in both fields.
The spam filter can be a little too aggressive. We have had issues with tickets being accidentally marked as spam then filtering incorrectly for weeks at a time.
Freshdesk doesn't quite have the right integrations with our other providers (Vonage, and Avochato, to name a few).
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 extremely happy with Freshdesk and can foresee using it for the next year. We might only consider using a different platform if our average daily ticket volume reaches four digits and its AI isn’t enough to handle our needs by then. While we haven’t tested this yet, we have read reviews that it’s AI capabilities are lacking
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
I gave it a rating of 9 out of 10 because they delivered on everything we asked them to do. Easy to setup, easy to deploy to end users, easy to customize, easy to enter tickets and so much more. Our experience with their support is top notch! After opening a ticket for support they call use back within 10 minutes every time!
I have encountered a lot of errors in the Freshdesk, however, they tend to resolve it on priority or at least they will share the timeline by when this can be resolved. Most of the time the issue has been from the other partner's end. They take time to resolve their vendor issues and they don't have any timelines in case of developed app errors.
The reports take a lot of time to download if the time period is large. Also, the tickets take their sweet time to open and load. It is not fast as Zendesk. Only 30 tickets are visible in a single go and there isn't any option to select all. If we need to change the pages and dashboards it takes a lot of time to open.
The main thing about Freshdesk user service is that once a request has been made for information about a feature of the platform, the support team responds to tickets quickly, within a day of writing and submitting them, with information that is concise enough so that there is no need to ask for help on the same topic again.
In-person training is provided to all the agents and it is very easy to learn the basics of the Freshdesk interface. Solving tickets via dashboards, replying to the guest queries in bulk via Freshdesk. The training which is a bit hard is creating the logic according to the ticket flow and intergeration.
This tool is no doubt easy to learn but in-person training is a lot better than online training. It takes time to grasp things in the online training, however, in pandemic we have done all the training online. Apart from a bit more time we haven't faced any issues with online training.
Not applicable. I have never used a support desk system before and FreshDesk had already been implemented at my company before I joined. I am not involved in financial decisions and I have no opinion on buzzwords like "time to productivity" and "time to value"
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.
FreshDesk was the best combination of ease of use and price. While inexpensive, even the lowest tier offered more functionality than the other guys, and the learning curve is almost nonexistent so it's easy to add new agents and get them up to speed quickly instead of having them spend days getting use to the UI.
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.
The pricing we had taken is on yearly basis but the subscription and billing frequency that we have is on monthly basis. I would not want to make any changes to it, it is a seamless process with all the contract terms and we both agreed on it. It should be as per the customer's need.
The product they have developed is amazing. They have made different products for emails, tickets, chats & calls as well. It is flexible according to multiple departments. The finance team can use it, the Customer support team is using it, we can use it in call centres, emails etc. We can use these tickets internally as well to create child tickets and assign them to different departments for query resolution.
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.
