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
Respond.io
Score 9.0 out of 10
N/A
Respond.io is a business messaging platform from the Hong Kong based company of the same name, that connects customers from any channel to every team. As consumers grow to demand personal communication on a wide variety of channels, businesses are looking to their software vendors and partners to innovate and deliver these customer experiences. Respond.io is designed to meet this challenge, simply.
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
If you're looking to implement the WhatsApp business api for your official number in your product Respond.io is the solution to go because the truth is that there is no easy way and most of the providers will assume that you have developers in order to create your own implementation and many of the other solutions our there are not even close to Respond.io and they are usually expensive. Also, most of the Customer Service software out there will offer you the typical channel but will skip Whatsapp while Respond.io does the opposite (check it out for the free tier if you're not convinced).
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.
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).
You have to be patient with Respond.io since many features are still in development I wish they can make features faster
In order to use WhatsApp business api you need a number that is provided by Twilio they also have implemented other number providers but it will be nice that they add more WhatsApp business number providers (since we have a US number instead of a Mexican number)
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
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"
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.
When we were implementing WhatsApp business api number in Bussi. We had 2 options the first Zendesk smooch.io and the second one a Twilio WhatsApp number. In the beginning, it seemed that Zendesk smooch.io was the option to go but the conversation was quite slow also the integration was easy but you needed to manage this conversation from zendesk which we were not completely sure about since it's more like a ticketing platform. Fortunately, we were looking and testing solutions until we found Respond.io, and even if they didn't have at the time the broadcast feature they let us know that feature was already in development so we felt that they were building a solution we were looking for so we decided to give them a few months and in those few months they built this feature and is a more dynamic way to answer customers than tickets so we decided to go with them.
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.
Most options we saw before Respond.io needed a minimum number of messages, contracts, or costly integrations from the side of the vendor while Respond.io is actually helping you to integrate the product with no extra cost.
Our users choose the communication channel they want so before we were losing leads and money because we were not able to attend this channel.
It requires a $0 investment to implement or maintain from the side of the developer area so we use our technical resources to develop our main core product not a WhatsApp chat integration feature.
