Freshservice Reviews

It's a major lead to work with the IT architecture.

The admin feature is the UI, so it's very clean. The asset management and its model are valuable as well.

Day by day, they keep on adding more features which are making the application very slow. We're we're facing some slowness. For example, the analytics part takes a very long time to load.

The chat portal is not that great. It would be good if they could enhance the chat portal, and give us some options to customize it. 

I have been using Freshservice for three years.

We have faced some stability issues, which were fixed by the actual service team pretty quickly. I rate the stability a seven out of ten. 

It is a scalable solution. Presently, twenty thousand users are using the solution. 

The technical support team is very good. 

Positive

We were using Zendesk, then we evaluated other service desk applications. Freshservice is really easy to use, and it has some of the code features that we wanted, and that is why we chose it.

The initial setup is straightforward. Our main implementation strategy was to kind of move our existing agents and existing users as well as migrate almost four hundred thousand tickets to the platform. First, we created all the different fields. We imported all the users and mapped them to the correct queue. I provided access to the agents in different groups. After that, we migrated our tickets. It took almost two weeks to migrate everything and set up.

The integration was done in-house. 

We have seen a return on investment.

The pricing is reasonable.

I recommend the solution. I rate the overall solution an eight out of ten. 

We're using the product for an HR service center.

We had a historical kind of email-based contact center. What it's allowed us to do is bring everyone in our department into the journey of customer experience and customer service. When you're just dealing with Outlook and mailboxes, those are typically only limited to certain teams. This allows us to scale. It allows us to scale and engage other people that may be required to help support a ticket. We may need a certain level of expertise or help from a subsidiary area, allowing us to bring them into the conversation much more quickly without losing sight of the ticket or the customer. You don't get lost in multiple emails. You can, essentially, manage everything off an initial inquiry.

We really like the Freshchat widget that allows people to engage with our FAQs on any kind of webpage or web property. We really like that. 

We really like the auto-routing. 

The rules-based automation that they've got built into auto triage and auto disseminate to the right groups. 

We really like the auto-responses, as well. 

Their dashboard and their ability to follow the history of the ticket to see who's all engaged is very useful. It allows us to see who's engaged with it.

Their analytics need improvement.

Some of their integration could be better as well. 

Maybe this might be new in some of their newer versions. However, the chat should be an inherent part and shouldn't be a separate module.

The way they run their service portal, it would be nice if you didn't require users to log in. If they could go to a login agnostic model and be able to, using AI, auto triage and recognize if somebody submitted a ticket before, they should be able to do that in an automated fashion. They shouldn't force users to log in anymore.

I've been using the solution for about two years. 

We've had no issues with stability or downtime at all.

The solution can scale well. 

We have a couple of different deployments. In our specific deployment that I'm attached to, we would have about 40 users.

We have seen growth inside of our organization. We're not the only team that uses it. There's a second team, and they're much larger. They have about 150 users.

We've seen other scaled deployments for other purposes because of the success we've seen with Fresh. Will we see more growth in our specific HR area? Probably not. We're a small HR shop.

They're not very good at technical support.

Neutral

I've used some of the Oracle products, like RightNow. I've had some ServiceNow utilization, as well.

The initial setup wasn't easy or difficult. It was kind of in the middle. There's a lot of configuration you can do on your own. There is some stuff where you've got to involve your IT department. Overall,  that's what I like about Fresh compared to something like ServiceNow. It's pretty lightweight. It's pretty scalable and has a much simpler ease of implementation.

It requires very little maintenance. Maybe we had one person attached to it. However, it wasn't a full-time job for them. We don't have to have an in-house Fresh technical expert. It's pretty easy to figure out.

We did it in-house with some of the initial onboarding direct from Fresh.

We have seen an ROI.

I'm not sure of the exact cost. I recall it being pretty small. 

When considering options,  I looked at Oracle again. We were looking at ServiceNow and Fresh, and we decided to go with Fresh, at least for short to medium term.

I don't know what version we are using, however, in terms of what modules we're using, we're using Freshservice and Freshchat.

Like anything, the tool doesn't fix your service issues. It can help, however, you got to have the right philosophical mindset and your process fundamentals in place because the tool isn't always your silver bullet. 

In terms of your process and your philosophy, I find doing an implementation like Fresh should get you in that mindset. The other piece of advice I would give people contemplating this is, for example, where I love dashboards and data, and Fresh doesn't do the best job in this space. It's not implementation and done. There's always fine-tuning required, and there's always room for improvement. That's where it's important to look at your data, look at your utilization, and always go back and challenge some of your concepts once it's implemented.

I'd rate the solution eight out of ten.

You can connect the system to an IDR when you receive a call. That was an easy use case to implement. Also, you can use a ticketing system for internal tech support issues within the company. It was oriented toward both the end customer and the internal customer.

It improved the organization's workflow by making managing all the information and tickets in a single system much easier.

One of the things I liked about Freshservice was how easy it was to implement. While it doesn't have extensive customization capabilities, the available options are sufficient for certain sizes of companies. You don't need to customize your ticketing system much. Freshservice is a great solution because you can implement it very quickly. You can upload your catalog, and you're done in maybe a week or two.

I think it would be great if the tool had another version that is more customizable. From what I remember, there were some limitations regarding the number of assets you could track. In a more robust version, the number of assets increases, but I think it would be better to have something more customizable for all versions, especially the most robust version. This would be great for larger customers.

I rate Freshservice's stability as ten out of ten. 

I rate the solution's scalability a seven out of ten. 

I have contacted technical support. It wasn't very easy. Even as a retailer partner, sometimes it was difficult to get someone from tech support to address an issue, especially if it involved changing labels or fields. Getting support for these kinds of issues was challenging.

Neutral

The tool's deployment is easy. I rate it a ten out of ten.

A customer can do it themselves. 

In the Latin American market, companies may not generate the same revenue as American companies of similar size. Therefore, while the return on investment could be good for an American company, it might not be as significant for a Latin American company.

I don't think it's expensive for the US or some European markets. Still, when I used Freshservice in Mexico, some customers found it a bit pricey, especially considering the platform's features. I think the pricing is fair for use in the European market, but it might be perceived differently in Latin America.

I rate the overall product an eight out of ten. 

I implemented the solution for a client, and it's used in the typical service management processes, including incident, problem, and change management. It's also used for fleet and facilities management. It has a built-in project management functionality, but that isn't used at the moment. Generally speaking, the out-of-the-box modules are used, with customisation.

It has allowed the client to implement service management processes that didn't previously exist in the business and to have more visibility and control of process tickets.

The most valuable feature is the sandbox, which allows the testing of new configurations, automations, and workflows before puting them live on the production system.

The most significant area for improvement is consistency across the different modules, as they are not intuitive. It makes me think the modules have different development teams with no consistent approach. From an end-user perspective, I can do certain operations in one module, such as incident management, but not in problem management, for example, and I don't see why that should be the case. An example would be the way that bulk actions has been implemented. It would be good to see more consistency in the development process. 

An additional feature could be a new module for test management; it would be good to see a module enabling the creation and management of test scenarios, test scripts, test requirements, and scenarios. The solution doesn't do that out of the box, and though it may be possible to do that with a lot of configuration and workflow customisation, it would be great to see a dedicated test management module.  

I have been using Freshservice for just over a year. 

The tool is highly stable; we've never had any outages or downtime. Freshworks employs a continuous delivery method with Freshservice, so new releases and updates are integrated seamlessly as they are released. There is no impact on the end-users or the agents, so the solution is very stable.

The product is highly scalable. The only barrier is the cost. The more agents, the higher the price, although the more we buy, the cheaper the agents become. As the solution is cloud-based, users access it via URL, which helps make it very scalable.

We have 800 to 900 end-users in total, with 20 or 25 admins.

I've contacted customer support on multiple occasions and there are two main considerations; response time, and quality of the response, with their ability to understand the issue being an important factor in the latter.

The response time is pretty good, as the support system is a live chat. Email is available, but live chat is much easier as it offers a more immediate response. I found their ability to understand the issues quite poor; it took a lot of back and forth. Generally, they couldn't solve the problem and had to take it further to the developers, and I think part of that is that the work I was doing was very detailed and in-depth. I encountered many bugs that an average end-user wouldn't, and many of the issues turned out to be bugs, so the resolution took a long time.

Neutral

The client previously used SysAid and the switch was made because SysAid wasn't flexible enough for the new business processes that were to be implemented.

The initial setup is very straightforward, especially the out-of-the-box configuration. Freshworks provided what they call a transition support specialist to assist us, so the setup was simple.

The deployment was relatively seamless; we configured the solution in an offline state which took about a week and deployed it from there. We shared the URL within the company, and end users accessed it using that. In total, it took one to two weeks for the setup and basic configuration. We did a lot of customisation, workflows, and automation, which took much longer than two weeks.

As the solution is SaaS, it's very light in terms of maintenance; we have two staff with global access to monitor it. One staff member could do that, but we use two for resiliency.

I implemented the solution as a consultant for one of my clients, so it was a mixture of in-house IT resources and vendor assistance.

We see an ROI from the product.

I can't recall exactly how much the licences are, but it is somewhere in the middle compared to the rest of the market. The more licences that are purchased, the cheaper it becomes, and I think the solution offers good value for money.

We ran a procurement exercise that began with online research using review and comparison sites like PeerSpot and Capterra, looking into all the major service management tools against a defined set of business requirements.  Based on our requirements, we shortlisted down to six companies - SysAid, Solarwinds, Freshworks, Hornbill, Halo, and TOPDesk.  We then sent out RFI documentation to the six companies.

For the next stage, we had demos from five of the companies, during which the functionality of each tool was tracked, measured, and scored. We had in-depth discussions regarding the scoring and then we ran trials of Freshservice and Hornbill Service Manager.  Further scoring after the trials resulted in Freshservice scoring the highest, so that's the one we went with.

I would rate the solution a seven out of ten.

The product is excellent out of the box, but there are inconsistencies in how Freshworks implements it. It works great for organisations that don't want to customise and create their own processes. The out-of-the-box processes with minor tweaks will suit most organisations, but it becomes more difficult for those who wish to adapt their own specific business rules and processes. In hindsight, Freshservice isn't the solution we should have chosen, as it's just not customisable enough.

There is plenty of help available for Freshservice; there's a user forum where you can post questions and get responses from other users. There's also a great deal of online documentation, the links provided by Freshworks, which connect you to their knowledge base.  Additionally, there is an immediate customer chat function, so a great deal of support is available for any issues that may arise. I would advise other users to use the resources and do the required reading.

We are using Freshservice for IT service management.

The workflow and the change management process are valuable.

Freshservice automation capabilities are improving the way we respond to a few customers. There is a bit of delay when we must respond to the customer.

I have been using Freshservice for five to six years.

The product is stable. I rate it a nine out of ten.

500-1000 users are using this solution. I rate the solution's scalability a nine out of ten.

Support is quite good.

The initial setup is easy and takes two months to complete. I rate it a ten out of ten.

We have achieved ROI in 12 months.

The solution's pricing is reasonable.

There are different tiers or plans for product selection, so we can simply choose from a list of suitable products. This way, we avoid bundling features we do not necessarily need and do not have to pay for features we will not use.

Freshservice is feasible to implement. A third-party consultant is not necessarily required. The customer service is also quite intuitive and easy to set up. Upon onboarding, the team's productivity increases within three months.

Overall, I rate the solution a nine out of ten.

We use the solution primarily for ITSM, but also in the capacity of ESM. It incorporates ITIL elements such as changes, problems, asset management, and ticketing, which is the main concept in use.

The solution facilitates a transition from an organizational structure that is function-based to a process-oriented approach. This improves efficiency in ticket routing and eliminates the need for extensive triage.

The most valuable features include ticket routing, automation in triage, data control, and flat licensing. It allows for customization and offers a broad feature set.

I experienced some delay in response time for non-function critical queries. Moreover, there's limited experience with the CMDB or asset management features.

We implemented the solution approximately four years ago.

I have not had any real experience scaling with this solution.

The customer service is satisfactory, though there might be delays in response for non-critical issues.

Neutral

We compared this solution with others in terms of feature comparison, licensing, and scalability.

The initial setup is very easy, especially if the external components and organizational structure are pre-defined.

The solution offers flat licensing and appears to be cost-effective.

We evaluated Halo and compared it for feature capabilities and customization.

None of my personal information should be published, and my comments should remain anonymous under GDPR regulations.

I'd rate the solution eight out of ten.

We primarily use Freshservice for ticketing, contract management, and asset management.

The solution has been very helpful engineering insights into the client's environment. We have been able to manage calls and incidents very efficiently which provides us with a clear understanding of the system warranty and the actions that we might need to take in terms of insights. The system is very dynamic and prevents any kind of oversights which ensures that there is smooth contract management. 

We can also easily uphold SLAs and deliver enhanced services without breaching any agreements.

I would suggest that Freshservice enhance its technical capabilities, particularly when it comes to ICT network discovery. This will make a significant improvement in their software and these features match SolarWinds. It would include discovering infrastructure elements like switches and wireless devices. This would consolidate functionalities and eliminate the need for additional software and streamline the management process, making Freshservice an all-encompassing solution for both technical and contractual aspects.

I have been using Freshservice officially for almost 4 months due to a management contract. But my acquaintance with the software goes back over a year because my technical team has been using it on the recommendation of my technical manager.

The product is stable as it has not crashed.

The scalability is really appreciated as it has helped us to onboard all our clients in a single platform and manage their cause by streamlining the invoicing processes. It is serving as a valuable tool for generating revenue. The scalability can be rated as a 9 out of 10 because it is always room for improvement. 

The initial setup was a very easy task. You just need to click around a few times and everything will fall into place. The UI is very friendly and it is not at all complicated with the preconfigured settings, making the setup more forward and requiring minimal input. It is a very easy and smooth process. The exact time frame of the deployment is not very sure but according to my technical manager, it does not take very long to set it up. After discussion, he proceeded with the setup in a day which was further configured and customised.

The cost at the current timing is very reasonable but as the product gains popularity, I anticipate it might become expensive. Fortunately my customers have been offered a generous discount making it more affordable for me and satisfying both my needs and customers requirement. 

My advice is for users to clearly understand their requirements before making a purchase, as Freshservice has numerous features, and buying unnecessary ones can be akin to wanting a Ferrari when a regular car would suffice. It's essential to know what is truly needed, given the extensive offerings of Freshservice. As for my overall rating, I'd give it a nine out of ten.

Our company uses the solution to provide service desk assistance to clients. 

One use case is with a client in the insurance industry. Customers who have issues with their insurance send emails for assistance that are routed to us through the solution. We created five support group classifications to address particular insurance issues.

We currently use Azure servers only for connection and to authenticate Office 365 mailboxes. For now, we do not link the solution with Azure's products.

Our company's productivity has improved. 

The solution is very responsive with a 97% success rate in funneling customer tickets. 

A chat bot needs to be added to the portal.

Only one channel is available on the portal for service tickets. We would prefer one channel for tickets and one channel for chat support via a popup that is accessed from smartphones. Other products such as ServiceNow allow two channels. 

The solution has bugs with language translations. For example, our company translated the portal to French but some items remained in English.

I have been using the solution for one year. 

The solution is stable. 

The solution is scalable for users. We currently have 2,000 users and 150 agents who provide service. We utilize PowerShell when creating users and groups because it simplifies the task. 

Scaling to unlock cross-group or other features requires a pack upgrade. 

The technical support staff are responsive and reactive. 

We contacted support when we were having issues with language translation to French. They responded quickly and corrected the bug that was causing some phrases to remain in English. 

I rate support an eight out of ten. 

Positive

We previously used Microsoft's SCSM that is the part of SCCM used for managing tickets. After we were attacked by ransomware, we decided to migrate to the solution. 

The initial setup and implementation are easy. 

It took us a month to create various catalogs of service for our client and fully deploy. 

I installed the solution with assistance from a coworker. 

A team of seven technicians provide ongoing maintenance such as adding users or groups. 

The solution has an annual licensing model.

The standard pack is currently orchestrating 2% of our tenants. Our goal is to use the solution to manage all orchestrations but that requires a bigger budget. 

We also have to upgrade to gain access to cross-group or other features.

Pricing is rated a six out of ten. 

We evaluated the solution, ServiceNow, and a third product. After meeting with a manager at Freshservice, we decided it was the best solution for our needs. 

We purchased the solution's standard pack but it does have limitations. For example, we created five groups to match particular service levels. But, users in group one cannot see group two's tickets unless they are a member of group two. 

This is problematic for our insurance client because tickets for children need to be linked to tickets for parents, even though they are are not in the same service group as individuals. Cross-group features are not available unless we upgrade from the standard pack. 

Environments that require two cloud channels might fare better with ServiceNow. 

The solution is easy to deploy even with no prior experience. The portal is simple to use and customize.

The standard pack provides a good starting place for managing client services. 

I rate the solution a seven out of ten.