Works for small companies
Updated June 24, 2025

Works for small companies

Kaley White | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Software Version

Garden

Overall Satisfaction with Freshdesk

As customer support for a healthcare SaaS product, I used Freshdesk to manage customer tickets, make knowledgebase articles available to customers, and moderate user forums. Freshdesk made ticket handling so much easier than just using a support email address. I used the Growth and then Pro plans, but even with the higher plans, in my opinion, Freshdesk is only suitable for smaller organizations. For example, attempting to add CRM functionality to our Freshdesk instance wasn't very successful.

Pros

  • The price is great for small startups just large enough to need a support ticketing system.
  • This may seem minor, but many tools don't have this: the ability to link a contact to multiple companies/accounts.
  • Agent collision detection is great for making sure agents don't duplicate each others' work!

Cons

  • Freshdesk is buggy, full stop. I don't know how many support tickets I submitted related to user login.
  • There can be a language barrier with support and sales.
  • There were a couple of hours-long outages that significantly impacted my company's customer experience.
  • Increased support efficiency
  • Self-service articles reduced duplicate support requests
  • Better connected distributors and sales to their users' support cases
My company first implemented Freshdesk before I was brought on, but from what I heard, implementation was easy and didn't require Freshdesk customer support. I implemented several additional customizations, such as automation and custom objects, and there was generally enough Freshdesk support documentation for me to figure things out. Freshdesk support and sales were generally helpful with troubleshooting and exploring features available on higher plans, but I felt that my company's specific needs were sometimes deprioritized.
Engaged customers raved about our knowledgebase articles, but it was nevertheless difficult to get customers to try the portal, largely because the account creation and login process is so cumbersome. However, the article suggestion feature is nice, and canned responses noticeably decreased agent response times. I never tried Freshdesk's AI assistant for writing knowledge articles.
My company originally selected Freshdesk due to price, but as we grew, we found it lacking compared to its more expensive counterparts. I briefly compared Zendesk to resolve our main issues with Freshdesk, but I'd spent so much time and effort customizing Freshdesk that we deemed the switch not worth it. According to colleagues, HubSpot is a great sales CRM but makes a poor support ticketing system. My current company uses Salesforce, which trumps Freshdesk on almost all accounts, but in my opinion, Salesforce is so customizable that users need a dedicated Salesforce team (developers, admins, etc.); Salesforce may not suit smaller organizations well.

Do you think Freshdesk delivers good value for the price?

Yes

Are you happy with Freshdesk's feature set?

No

Did Freshdesk live up to sales and marketing promises?

No

Did implementation of Freshdesk go as expected?

Yes

Would you buy Freshdesk again?

No

Freshdesk does the job for smaller organizations, particularly if they only need a ticketing system. Freshdesk's other features, like user forums and knowledgebase management, are lacking. For example, the knowledgebase article editor is cumbersome, and article organization options are limited. It's also difficult to restrict portal access to certain types of users, so Freshdesk works better for public-facing information. The features, such as custom objects, that Freshdesk includes to supposedly make it a pseudo-CRM do not work well in practice. Finally, there are numerous obvious API endpoints that don't exist.

Freshdesk Feature Ratings

Organize and prioritize service tickets
8
Expert directory
6
Ticket creation and submission
8
Ticket response
7
External knowledge base
4
Internal knowledge base
5
Customer portal
4
Social integration
2
Email support
8
Help Desk CRM integration
1

Using Freshdesk

4 - We had three Freshdesk agents: three customer support agents plus the sales lead.
2 - Two of the Freshdesk support agents were available to troubleshoot issues and implement optimizations, automation, and customizations.
  • Managing customer support tickets
  • Providing self-service knowledgebase articles
  • Tracking user-company relationships and integration history
  • Codifying parent-child company relationships
  • Distributing meeting recordings to customers
  • Exposing customer communications to their distributors
  • More nested knowledgebase organization (requires a higher plan)
  • Further portal customization by editing the theme code
  • Integrating phone and chatbot support in addition to email
My company that used Freshdesk was acquired by another company that uses Salesforce, so our only reason to keep Freshdesk would be records, but migrating the tickets, notes, and company details from Freshdesk to Salesforce was straightforward enough. Had the acquisition not occurred, we would have renewed Freshdesk because the cost of switching would've been too great in terms of price, time, and sunk cost (our Freshdesk customizations would not port over well).

Evaluating Freshdesk and Competitors

  • Other
My company was very small when it purchased Freshdesk, and budget was limited. Essentially, our only requirement was a sane way to manage a rapidly increasing customer support ticket volume. A "support@..." email wasn't cutting it anymore.
Had the budget been larger, my company may have chosen another ticketing system, but it's hard to say in retrospect whether we anticipated our needs growing beyond basic support ticket management.

Freshdesk Implementation

Change management was minimal - There was only one support agent when my company implemented Freshdesk, so he simply configured Freshdesk to meet our needs and that was that. Later, when more agents were onboarded and started implementing our own customizations and optimizations, we simply alerted the relevant tea members of the change or new feature. There was no formal change management process.
  • Language barriers with Freshdesk support and success

Freshdesk Training

The Free plan with basic features was easy for a single support agent to set up. Other features required a few support tickets but not dedicated training.

Configuring Freshdesk

Freshdesk heavily advertises theme customization, but this is limited in practice without costly third-party development services. There's a neat automation feature, but it only provides a few common use cases with limited support for webhooks and API calls. Speaking of the API, it lacks several obvious endpoints, and the documentation is minimal.
Use the defaults if possible. This eliminates the need to test custom configurations.
Some - we have done small customizations to the interface - We attempted some more involved customizations, but Freshdesk development is its own industry, and we experienced difficulty achieving our goals in-house. Nevertheless, we did implement the following customizations: additional navbar items for support meeting scheduling, color scheme and logo, and banners.
Some - we have added small pieces of custom code - Freshdesk's code editor isn't the most user-friendly, but at least Freshdesk provides a preview before you make the changes live. I wrote some custom HTML, CSS, and JavaScript for the portal UI, but options are limited.
We attempted to use Freshdesk as a pseudo-CRM by creating custom objects and relationships among them, but Freshdesk was never meant to be a CRM, and the limitations outweighed the benefits.

Freshdesk Support

Support genuinely tries to be helpful 99 percent of the time. Positives include bug fixes in response to my tickets (although one such bug fix didn't end up working) and hours-long response time as opposed to days. It's easy for support agents to troubleshoot in your Freshdesk instance. Ticket submission is simple via email and chat. Chat responses are fast, including escalations to the appropriate parties. Negatives include the occasional language barrier, and fragmented ownership of tickets. Often, when I submitted another ticket related to a previous one, a different agent picked up the new ticket with no knowledge of my previous issue.
ProsCons
Quick Resolution
Good followup
Knowledgeable team
Problems get solved
Kept well informed
No escalation required
Immediate help available
Support cares about my success
Quick Initial Response
Need to explain problems multiple times
No. As far as I'm aware, all Freshdesk plans include unlimited email and chat support.
Yes - A resolution was attempted to a bug that was found as a result of my support ticket. However, bug fixes reported on Freshworks Community, the users forum, tend to linger for a while.
I recall receiving a comprehensive response within a few minutes of my support email.

Using Freshdesk

Freshdesk is generally intuitive to use, but some features are clunky, such as the knowledgebase article editor, especially the HTML editor. Some features are glaringly missing, like using the same editor for canned responses as for knowledge articles, and embedding video files in knowledge articles.
ProsCons
Like to use
Relatively simple
Easy to use
Technical support not required
Well integrated
Convenient
Feel confident using
Familiar
Inconsistent
Slow to learn
  • Replying to support tickets
  • Drafting knowledgebase articles before publishing for customers
  • Associating a contact with multiple companies
  • Editing the theme with custom code
  • Editing knowledgebase article HTML/CSS
  • Customer account activation and password reset

Freshdesk Reliability

My company had Freshdesk agents from support and success. It's generally difficult to customize permissions for different agent "roles." We were a fully distributed company, so "multiple sites" doesn't apply to us. We found Freshdesk features lacking as we grew our customer base, and adding agents wasn't easy because price steeply increases with number of agents.
There were a couple of hours-long total outages during business hours that significantly impacted our customers' and distributors' experience. Besides that, intermittent slowness or temporary non-functionality of specific features was common.
Freshdesk is pretty slow but not unusably so. Integration with other systems doesn't noticeably hamper performance.

Integrating Freshdesk

Ease of integration varies depending on the system.
Integration with other systems is provided by apps on the Freshworks Marketplace. Some apps are written by Freshworks, but others by Freshdesk users. Most apps are paid and don't work well, but the Jira integration, for example, allows you to tag tickets with Jira issue numbers. Some other systems have their own integrations with Freshdesk, but we didn't use these.
  • Zapier
Zapier has some Freshdesk automations, and even more can of course be done with the Freshdesk API, but more automation and API endpoints would be great.
  • File import/export
  • API (e.g. SOAP or REST)
Thoroughly vet an app from the Freshworks Marketplace before purchasing it.

Relationship with Freshworks Inc

Sales and success were proactive to make sure we were satisfied with the product, even if many of these emails were automated. They were especially persistent about complimentary implementation assistance and training. When we considered upgrading our plan, sales was very enthusiastic and available to answer our questions. However, there was an occasional language barrier, and pitching irrelevant features was often prioritized over my company's specific needs.
Support and success seem genuinely helpful, and most of our issues were addressed in a timely manner. However, support was a bit disconnected; agents seemed to lack knowledge of my previous related tickets. It seemed that there was poor communication among support agents on their end, so I often had to rehash previous issues to provide context.
I did not professional services from Freshdesk, but sales was persistent in suggesting them.
We didn't negotiate, just purchased the standard plans without issue.
I was not very involved with the purchase/contract (my company purchased Fresjdesk before I was brought on), but I will say that pricing per agent made it difficult to grow our support team. Additionally, we were kind of disappointed after our upgrade because it didn't solve our pain points as much as we expected.
If possible, reopen a previous support ticket instead of creating a new one. Communication among support agents is poor, and you'll likely have to provide a lot of context if your issue isn't new to you.
With success, be sure to emphasize your specific goals that you want to achieve with Freshdesk; it's easy for them to focus on the standard demo instead of your needs.

Upgrading Freshdesk

Yes - We did not upgrade to a new release, but we did upgrade our plan to Pro. There was no downtime, and everything went as expected: all our data was retained, and we instantly gained access to the new features in the higher plan. Freshdesk offered plenty of support from both technical support an customer success, including training and configuration assistance.
  • Association of a contact with multiple companies
  • Custom objects
  • More custom contact/company fields available
  • A higher plan offers more folder nesting
Yes - We noted numerous deficiencies in the basic plan that higher plans offer, including custom objects, more custom contact and company fields, and association of contacts with multiple companies. The price increase was reasonable, but the new features weren't as impactful as we had hoped. For example, further nesting of solution article folders actually requires an even higher (more expensive) plan.

Comments

More Reviews of Freshdesk