Freshdesk Reviews

We are a health insurance company that uses the solution to communicate with our customers through chat, as well as health providers and other prospects. We use it according to teams; the customer success team is divided into three teams: those who attend to voice only, those who attend to emails only, and those who attend to chats only.

For every request that comes in via any of these channels, the agents in these channels take charge there.

We currently don't use calls for Freshworks because of our IT provider in Nigeria. However, we use email and chat, and they both work well. Some new features that they recently released will give the chat, Freshchat, more functionality than Freshdesk. We were using Freshdesk before, but we are right now on Freshchat.

The UI is also easy to use.

Currently, they have Freshchat as the central platform. But for email, I would still like to have assistance around how our agents can assist our customers, such as on-the-go translation; as we are expanding to the emerging market, we would not be able to hire and pay customer support agents in those areas immediately, so we won't be able to attend to their conversation if we do not speak the same language. That is something similar platforms have, which I would like to have included in Freshdesk.

We have been using Freshdesk for over three years.

I rate Freshdesk's stability as eight out of ten. There is room for improvement with the chatbots.

It is scalable. We currently have about 16,000 chatbot sessions monthly, which keeps growing every month.

Support is very knowledgeable, so they know their products very well. They can almost always resolve your problem immediately.

The initial setup was relatively easy.

One of the issues we are looking into is the cost. As we keep on expanding, it means that we will need more licenses. Currently, that would blow our budget. That's the main concern right now because the cost is very expensive.

Aside from the license, we have chatbot conversation costs.

One should go for the solution if cost is not a problem or if they will not expand to major markets and require many licenses. There is still room for improvement, but the UI is easy to use, compared to some other platforms. I rate Freshdesk a seven out of ten.

We are using the product for communication with the clients. We use it for opening tickets and communicating.

It is very easy to make reports. There are a lot of tags on every ticket. As a supervisor or as a head of a certain department, you can easily make reports for every agent on your team. 

The solution is stable.

It's scalable and is able to handle big workloads. 

Having so many tags makes everyday work a lot more complicated, and a lot more time-consuming.

If I'm going to contact a client, then I have to put all of these tags, and that ticket is closed as the ticket has been sent. It's similar to when you send an email. That ticket has now been sent and therefore it's closed. If the client responds, the ticket will come back as open. However, if we send a ticket to a different department, let's say, then we have to put the ticket on as open to the different department and I'm not going to be able to see it unless the other department sends it and replies, and puts it back on my name as open. The ticketing feature is a bit complicated. 

In order to send a simple email to a client, I need three minutes. And due to the fact that we send a lot of emails, that amount of time required is time-consuming for us.

Freshdesk has a feature called Freshchat. I would like to have translation services inside the chat. We get a lot of clients from different countries speaking different languages.

I've used the solution for five to six months.

The stability is good. There are no bugs or glitches. It doesn't crash or freeze. Its performance is reliable.

The product is scalable. We handle quite sizable workloads and it is able to work well regardless.

While we have 100 users, not everyone uses this solution. We use it for customer support, finance, the operations department, and the partner's department, which may be up to 15 people. We do use it on a daily basis. We do not plan to increase usage until we hire more people. 

Prior to this solution, we were using Zendesk. 

For us, the difference is you can see all of the tickets in Zendesk. That's really important, as you can also see tickets from a different department. You can see how a certain specific case is being handled. Is it being handled well? What are the updates? 

With Freshdesk, the tags are really time-consuming. You have to check with different departments and ask "Hey, have you checked this ticket, this ticket number?" You have to save the ticket number so you will be able to actually ask them. 

I'm not responsible for the setup. That said, it's my understanding that we did have a couple of issues when it comes to workflow. For example, certain tickets should come to a certain department, and we have issues with that. 

The company handled the initial setup in-house. 

I'm not familiar with the pricing aspect of the product.

I would recommend Zendesk. I prefer Zendesk and would recommend it to everyone. Freshdesk I do not like as much. It's much more time-consuming. It's much more complicated. If you have a big workload, then that can get in the way of actually getting work done.

I'd rate the solution seven out of ten. We've gotten used to it, however, it's too time-consuming. Choosing this solution was a management decision. It's not ours. It's not an ideal ticketing system.

Our primary use case is support emails. When customers wanted to reach out to us, we had a help desk linked to the support email. When we receive tickets, all of them are classified by region and the assigned relationship manager. Then we divert them for resolution. 

One of the main benefits is user engagement. The interface is so fantastic that the learning curve for any user on the platform is maybe an hour. It's such a simple tool and very intuitive, so we can train a user and get them onto the platform within no time. If a user is aware of the business, using this tool is no hassle. The training time is so short on this platform for users at the associate level. 

The user experience on the platform itself is fantastic. The UI is clean and uncluttered, so it's easy to find any information about your customer or the issue at hand. You can find out the person responsible for that particular issue, what the problem is, who the stakeholders are, and how to resolve it. There are lots of tools that will help you do that as well.

When we ask them for changes or features, they usually provide a workaround or a feature. They stay on top of the latest technologies. The most significant feature they've added recently was two years ago. It was an AI chatbot, which is very important for business.

They've gotten all the features at the right time and integrated them into the platform. There aren't any features that we want to enhance, but we need to mature in our usage of some of them. I can't say any feature is missing or needs improvement, but a tool's built-in features need to evolve customer feedback. We have a dialogue set up for that kind of feedback. 

I've used Freshdesk as an admin for at least 4.5 years now, so I've been engaged with the tool day in and day out.

I've never seen Freshservice go down in the past 4.5 years that I've worked on that platform. I haven't had issues with usage or downtime. If there is downtime, we're told about it. We don't have trouble with connectivity because it's an SaaS tool, so there are no problems serving our customers. 

It's absolutely easy to scale. I'm sure this can handle any number of users or any volume of issues. We have 2,500 users at the moment. 

Freshdesk support is great. If we ever had minor performance issues, it would just take an email or call to the support center, and they would fix it immediately.

It's very straightforward. The initial implementation didn't take long, but I wasn't there at the time. When I became an admin, somebody else had already implemented it, so I'm unaware of the details. However, we did more implementations after that, but it was plug-and-play because we already had everything in place. There were no hassles. There's no maintenance on our side, either, because that's taken care of by Freshdesk.

I would say Freshdesk is competitive compared to other products on the market. 

I rate Freshdesk 10 out of 10. I recommend it because I think anybody who tries Freshdesk will be convinced that this is one of the best tools they could use for their organization. I see that all the leading organizations in the market use Freshdesk today for the support system.

It's more than a support tool because it has a lot of integrations that you can work with. You need to work with the team and let them know its use cases. They have a solution for all the issues with customers that we face as an organization. I don't think they've ignored anything from a customer experience perspective. I would say that any company wanting to implement this particular tool should try it because I'm sure they will like it.

It's a simple application for trouble tickets.

The solution is very easy to configure. It will not take a lot of time to configure.

It's a product that is very easy to use and very user-friendly. 

It's free of charge for us. For our scale of business, it's very important. We don't have a lot of tickets. Right now, we are in a big development stage with our business. 

The solution is very stable.

The scalability is good.

While it's good for a small number of tickets, definitely in the future, we will require something more powerful.

I would prefer to have a lot more functionality. There's a bit of a trade-off between the price and the functionality. When we do choose the new solution, we will have costs go up. 

I've been using the solution in this company for about a year. 

The stability is good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

The solution can scale. 

We have 100 users on the product currently.

As we grow and get more tickets, however, we likely will need a bigger product and will move away from this one. 

The solution has been great. We haven't needed technical support. 

As a cloud-based solution, the initial setup is very easy and very straightforward. It's not overly complex or difficult. 

For us, the solution is free to use. We do not need to pay for something bigger. If we want more functionality, it will cost us more. 

We did look at other solutions, however, I cannot recall their names. We chose this solution as it was free to use and fit our requirements. 

I'm a customer and an end-user.

I'd rate the solution at an eight out of ten. I'm pretty happy with its capabilities. 

While it does depend on the company's requirements, I would recommend this product to other organizations. 

It is mainly used for customer support via email or chat.

I am able to use more analytics to track the performance. I also noticed that the overall speed of the platform is improved compared to our last CRM tool provider.

The feature that I have found most valuable is the way that it connects to various folders especially because we use it as a CRM tool. We can connect it with our phones and our chat, and also with the API and have it as an email service. Freshdesk just makes our life easier.

We were previously using OTRS on the on-premise server and there was limited space for us. With Freshdesk, we don't have to worry about that because they actually have a cloud version where you can store more information. Also, the analytics of Freshdesk, for me as a manager, make my life easier tracking the performance of the customer support team.

There are some features I would like to improve. For example, I would like to be able to change the subject in emails for ourselves. We use a lot of third parties. So if we want to handle an email from one of our suppliers or one of our clients, we have to have two tickets, and it would be easier if we could only have one ticket to handle everything. With Freshdesk, that's very difficult because we can't change subjects. So, if we could have the option to do that, it would improve our speed and the overall cleanliness of the CRM.

I have been using Freshdesk for about a year and a half.

The stability is fairly good. We have had some small issues with system crashing but it was resolved quickly by the Freshdesk support.

We had one issue that we had to escalate to the technical support. It crashed and we had to have their help to fix it. Their support wasn't the best, it took a little bit for the person to understand what I was trying to say. And they seem to have a lot of layers between the customer support and their tech team. But once it reached the tech team, they were very fast to solve it.

The initial setup was fairly simple. We had about a month of trial and then it was fairly simple when we launched. We had an onboarding person that gave us overall training for it, and then they have the Freshdesk Academy, where they have training videos on their platform that I could use. It would just direct my team to see it as well, so it's fairly simple. It didn't take too long.

There were five people involved and it took about a month and a half.

I think the pricing is fair. I don't think it's cheap, but I also don't think it's too expensive. It was one of the best values for your money that we found when we were checking the possibilities of substituting the old CRM tool.

I think there is also a monthly fee, and if we want to have more features, we would have to also scale up the license.

We switched to Freshdesk to have the possibility of having everything on the cloud. We used to have a physical server in our office and it just didn't make sense anymore.

My advice to anyone thinking about Freshdesk is to test it a lot. There are some features that are very different from other tools. And make sure that you understand everything that you need. Also to talk with the sales personnel at Freshdesk to understand what they can offer. In our case, there were a couple of things that we had to adapt because I wasn't very clear with our needs on the onboard process. So, it was more of my fault than theirs but then we had to adapt it because Freshdesk just didn't have some options. For example, with their ticketing process.

On a scale of one to ten, I would rate Freshdesk about a seven.

We are using it for IT support, desktop support, and any issues with any of our applications. We use it pretty extensively. It is the portal that we use for any requests, work being done, questions, bug fixes, and third-party software bug fixes. We even use it for tracking small projects.

It is a SaaS solution, so we have its current version.

We had over-customized HEAT to the point where it was just not very useful for a company of our size. Getting Freshdesk was like a breath of fresh air because it was simple to use. It required zero or negligible training effort on the part of my team. We just started creating tickets. We integrated it with our email so that we can auto-generate tickets. It wasn't too bad as a technical challenge, and it just worked.

Its simplicity is most valuable. It is easy and simple, and it requires negligible training effort. I don't spend all my time goofing around trying to find stuff in the ticketing system.

We have many cases where a ticket comes in, and it ends up having multiple team members working on it. It would be really nice to be able to assign a single ticket to multiple people, rather than having to create the parent-child hierarchy that they have set up. It generates a proliferation of tickets that I really don't want to have. Having to jump from a parent to one child and then to another child makes it harder for me to be able to see the entire case from end to end. A simple example is our new hire process or our termination process. We have people who leave. We also have people who come on board. We have got multiple people participating and doing things related to the leaving or onboarding process. Currently, I have to go to different tickets to be able to see whether all tasks are really done or not. If I could assign lots of people to one ticket, it would be really nice.

I have been using this solution for a year and a half.

We might've had one outage a long time ago. It was down for a fairly brief time. Other than that, it has been solid.

We don't have a huge company, so it is kind of hard to tell, but certainly, I've had zero problems with performance and being able to look at lots of tickets versus a small set of tickets. It should be fine in terms of scalability.

We have eight people in IT who are actively using it. Overall, we have 135 people in the company. They're the ones submitting tickets to us by email or by calling in, and then we create the ticket manually.

In terms of usage, I don't see it going outside of IT to the rest of the company. We use it for basically 100% of our IT work. We're pretty all in.

They were decent. I was CC'd on a couple of emails when we were setting it up initially. There was some stuff about the email integration that was probably the hardest thing we did, and we needed a little bit of technical help on that, and they were timely. We didn't have 14 different back-and-forth exchanges where you felt like they're just answering from a book rather than really listening to the problem that you have and trying to address it.

We were using HEAT. We switched because of the frustration amongst the whole team about how complex our system was. We had over-customized HEAT to the point where it was just not very useful for a company of our size. We needed something easier.

I didn't do it. It was someone from my team. He did it in three or four days in the midst of everything else he was doing. It was simple. You just add in our users. He was able to import the names of everybody from the active directory, so we got all the employees there.

We had to sit down and have a meeting to decide the lists, categories, and groupings, and then he just did it. A couple of days later, I started to use it in the pilot form, and we cut over to it fast.

We implemented it ourselves. You don't need to have anybody else do it.

In terms of maintenance, the only thing that we have to do to maintain it is just to add a new call type or something like that, but any of us can do that. It is very intuitive.

We have absolutely seen an ROI.

It was definitely not expensive. It was two grand or maybe three grand total for a year.

It has just straight and simple standard licensing fees. There is no additional fee.

If somebody is implementing a new IT service desk ticketing system, they should definitely look at Freshdesk. If they just want a lean and mean system, it is really a great option. If you need a lot of ITIL complexity and have a very large team, and there is a lot of back-and-forth with tickets and heavy approval process and stuff, it may not be suitable. We have only one of their products. They may have other products that bolt onto it and add that in. We are using the simple version, and it doesn't necessarily have all those controls, but in our case, we didn't need all that.

I would rate Freshdesk a nine out of ten. I am very happy with it.

We use this solution to manage our technical support tickets from our customers.

The reporting, analysis modules and insights capabilities for this solution could be improved. It is essential for us to know how many tickets are open on different business domains or open for specific teams. These insights drive decisions that happen in the technical support area. 

We have been using this solution for two years. 

This is a stable solution. 

This is a scalable solution. 

We have made use of the training academy and the technical support team from Freshdesk. Both have been very good resources. 

Positive

The initial setup was not that straightforward.

I was part of the team that selected this solution. We considered other options such as Zoho. Freshdesk was the best solution with the best price. It was cost efficient and included all the features that we needed.

I would recommend that those implementing this solution first complete the academy to receive video training on the administration port to be able to configure the tool. I would also suggest that agents get familar with the workflow of the tickets to understand Freshdesk.

I would rate this solution an eight out of ten.

We use Freshdesk, in our asset financing company, to handle customer complaints, issue tickets to available agents, and effectively manage escalations. We make use of the reports related to each of these different stages of the customer journey. 

Our agents use Freshdesk to reach out to new and existing customers and work off the database we have in Freshdesk to retrieve the lists of our customers. 

We use it as a customer relationship management tool and it serves this purpose well. The key objective was being able to connect to a database of our customers in Freshdesk and to show information such as their names, credit status, and the last time we spoke to them. 

One of the most valuable features is the multi-agent system, although this is possible with most CRMs. There is the option to create different roles for specific users. We make use of groups for each customer service team which has been very effective. We are able to apply different sets of rules for each group which determines how they interact with customers and escalate issues. 

Freshdesk also provides useful data for the tracking of tickets and their statuses using time stamps. We have been able to implement different interventions for such as calling a customer when certain timestamps are made.

There are a number of different statuses for tickets that agents can apply. There were times when the customer service agents got confused as to how to use these statuses. This could have possibly been something we could have streamlined and improved manually, in retrospect. 

The dashboards are useful but could be so much better. As product managers and data scientists, we couldn't use the dashboard for analytics and had to move the data in Power BI.

I have used this solution for more than one year. 

Based on our experience, this solution was reliable and performed well.

This solution is scalable. 

The initial setup was easy for the average user. However, we did have instances where new features took a couple of days to implement properly.

Deployment was a combination of both a vendor and an in-house team. 

Deployment took two months. 

I enjoyed the experience, as a product manager, using and implementing Freshdesk for customer service. Overall, this is a good and robust solution that offers an extensive number of features that we have not yet used. 

Before making the decision to use Freshdesk, I would recommend working out your use case thoroughly using wireframing or a mock-up. This will determine exactly how you would use the product and help you build a better customer management system. This type of planning will also allow you to deliver value much quicker. 

Overall, I would rate this solution a nine out of ten.