
Overview

Product video
Freshservice provides an intelligent, right-sized service management solution for modern businesses of all sizes. Freshservice does this by taking a fresh approach to building and delivering modern employee experiences and unified service management businesses to achieve efficiency, fast time-to-value, and improved employee satisfaction and productivity.
Use-cases: MSP, ESM, ITSM, PPM, ITAM & ITOM
Plans & Pricing: Each plan has a different feature set & pricing (freshservice.com/pricing)
Some of the main features available in the most popular plan (PRO) are:
- ITIL Modules & Asset Management
- Alert Management
- Project Management
- Purchase Order Management
- Analytics Pro
- SaaS Management
DISCLAIMER : We have listed only one plan here(which is most popular), other plans can be procured via AWS Marketplace via Private offer.
For Additional queries, Different plan options, Custom / Volume Pricing via Private Offer please contact us at channels-awsportal@freshworks.com
Highlights
- Reduce costs and agent workload with advanced capabilities such as Workflow Automator and build powerful automation with simple drag-and-drop actions and zero coding effort.
- Empower employees to help themselves with end-to-end multichannel self-service with intelligent chatbots, and to reach IT support via the channel of their choice such as email, a self-service portal, mobile app, phone, chatbot, and feedback widgets.
- Integrate seamlessly with enterprise systems and your existing tools with our extensive ecosystem solutions, marketplace apps, and robust APIs for service desk integrations.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Description | Cost/month |
|---|---|---|
Pro | ITSM + ITOM + Project Management for large organizations | $119.00 |
Growth | For growing businesses across their LOBs | $59.00 |
Enterprise | Service management solution for enterprises | $167.00 |
Starter | For getting started | $29.00 |
Vendor refund policy
Unless otherwise specified in these Terms or a Form or a Service Plan, all Subscription Charges are nonrefundable. No refunds shall be issued for partial use or non-use of the Service(s) by You provided however You shall be eligible for a pro-rated refund of the Subscription Charges for the remainder of the Subscription Term if You terminate Your Account as a result of a material breach of these Terms by Us.
Custom pricing options
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Support
Vendor support
We offer free support for all our customers. We provide a 247 email support and 245 Chat/Phone support support@freshservice.com
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Standard contract
Customer reviews
Ticket categorization has streamlined incident tracking and reporting for recurring issues
What is our primary use case?
Freshservice is used to redirect ticket handling and acknowledge tickets and incidents received. Tickets are redirected with their short description and subject line in Freshservice , which allows for quick identification of ticket types within the dashboard.
The dashboard in Freshservice displays which user has how many tickets and what types of tickets based on priority, urgency, and impact. Incidents are shown according to status type including in progress, pending, open, resolved, and closed states. Additional status types can be added, and add-ons can be configured within Freshservice independently.
Weekly and monthly reports are generated in Freshservice to identify repeated and reoccurring issues and to track the number of issues received weekly. Reports are easily fetched in CSV and Excel formats. Freshservice offers many different types of filters, allowing for specific issue tracking. For example, issues can be filtered by CloudWatch, Prometheus, Grafana , or New Relic to retrieve only the relevant data needed.
During a high-impact event in the project, Freshservice was used to manage numerous Prometheus tickets over a two-month period. To fetch tickets by subject type and service, the export option in Freshservice was used to select Prometheus tickets. The subject line was filtered for Prometheus, and tickets were exported for a specific time period using created date and end date parameters. The report was downloaded in CSV or Excel format, allowing for deep analysis of specific dates and times when tickets were received for troubleshooting and log review purposes.
When facing many issues on the same day, data is fetched in Excel file format. All ticket types and incidents are exported, and specific ticket types such as Grafana alerts can be filtered to track spike counts and similar alert types. Data can be easily exported from a specific date to another date as required, and the Excel file can be searched by subject line or short description as mentioned in Freshservice tickets.
What is most valuable?
The best features Freshservice offers are the tagging of tickets with categories, subcategories, items, and CI type. Freshservice is preferred over other ITSM tools because it provides an excellent dashboard for ticket counts, displaying how many tickets are in open state, how many tickets are resolved today, and the types of fields for ticket status specifically.
What needs improvement?
Freshservice has an AI agent that needs improvement for finding knowledge base articles. When issues or incidents are received in Freshservice, new users should be able to receive direct help from the AI agent with knowledge base articles rather than requiring assistance from other employees. When a new user encounters an issue, the AI agent should provide relevant knowledge base articles based on the issue type and short description. The AI agent has already been set up and installed but requires further improvement.
For how long have I used the solution?
Freshservice has been used for more than five and a half years.
What do I think about the stability of the solution?
Freshservice is really stable.
What do I think about the scalability of the solution?
Freshservice's scalability is quite good and easy to use with no issues regarding scalability.
How are customer service and support?
When an issue occurred regarding ticket merging in Freshservice, support was obtained through email. The customer support team was very helpful and polite, demonstrating accuracy and understanding of the urgency. An employee had mistakenly merged multiple tickets from different domains into one ticket. The support team guided the resolution process and connected via a bridge call for screen sharing, resolving the issue in a minimal period of time.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Before Freshservice, ServiceNow was used. The switch to Freshservice occurred when changing organizations, and Freshservice was found to be more attractive compared to ServiceNow . ServiceNow operates slower and is more complicated in creating incidents.
How was the initial setup?
Pricing, setup cost, and licensing of Freshservice are handled by the business analyst or marketing team, so those details are not known. Technical reviews can be provided honestly from a technical perspective.
What about the implementation team?
Other options were not evaluated before choosing Freshservice.
What was our ROI?
Freshservice saved time, though the impact on employee headcount needs is uncertain.
What other advice do I have?
All features explored in Freshservice have proven to be helpful in reducing workload and ticket redundancy. Others looking into Freshservice should explore all features first, as they will help reduce workloads and redundancy in projects and decrease ticket count through problem management tickets. Ticket categorization features in Freshservice are particularly valuable. This review rates Freshservice as a nine out of ten.
Easy to Use and Complete, but Ticket Update Tracking Needs Improvement
Freshservice Unified Our Operations and Delighted Our Staff
Mobile access has transformed ticket handling and now reduces time, staff, and support effort
What is our primary use case?
We use Freshservice primarily for IT Service Management , including incident management, service requests, asset management, and change management to support daily IT operations efficiently.
Freshservice is used as our central platform for:
-
Managing IT incidents and service requests
-
Automating workflows and approvals
-
Tracking IT assets and licenses
-
Supporting ITIL-aligned change and problem management
-
Improving visibility through reporting and analytics
It's a great tool that makes our work very easy
How has it helped my organization?
Freshservice has improved our service desk efficiency by streamlining ticket handling, improving response times, and increasing visibility into IT operations.:
-
Centralizing incident and service request management
-
Reducing response and resolution times through automation and SLAs
-
Improving visibility with dashboards and reporting
-
Enhancing asset and change management
-
Increasing end-user satisfaction via a user-friendly self-service portal
Overall, it has helped standardize processes and improve operational efficiency.
What is most valuable?
Freshservice’s best features stand out because they combine ease of use with powerful IT service management capabilities that scale well as organizations grow. One of its strongest features is Incident and Service Request Management. The intuitive ticketing system allows teams to log, prioritize, categorize, and resolve issues efficiently, while automation rules, SLAs, and workflows help reduce manual effort and response times. This leads to faster issue resolution and improved end-user satisfaction.
Another key feature is the Self-Service Portal and Knowledge Base . Freshservice enables users to find answers, submit requests, and track their issues without contacting IT directly. A well-structured knowledge base reduces repetitive tickets and empowers users to resolve common problems on their own, freeing IT teams to focus on higher-value tasks.
What needs improvement?
Freshservice is a strong IT service management platform, but there are several areas where it could be further improved to deliver even more value. One key area is advanced reporting and analytics. While the current dashboards are useful, more customizable, real-time reports with deeper drill-down capabilities and predictive analytics would help organizations better forecast workloads, identify recurring issues, and make data-driven decisions.
For how long have I used the solution?
I have been using Freshservice for about five months.
What do I think about the stability of the solution?
Freshservice is stable.
What do I think about the scalability of the solution?
The scalability of Freshservice is very great.
How are customer service and support?
The customer support for Freshservice is super great, and I would rate the customer support a 10 out of 10.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I previously used Jira and ManageEngine before switching to Freshservice.
What was our ROI?
With using Freshservice, only two technicians are needed per one shift, but without Freshservice, for the same company size, we need about four technicians per shift, so it saved money and time.
What's my experience with pricing, setup cost, and licensing?
I do not have any experience with pricing, setup costs, and licensing, as it was assigned to the infrastructure team.
Which other solutions did I evaluate?
I did not evaluate other options before choosing Freshservice.
What other advice do I have?
My advice for others looking into using Freshservice is that it is a very great tool, as it saves your time, your money, and your team efforts. I would rate this product 9.5 out of 10.
Streamlined incident escalations have reduced resolution times and improved team collaboration
What is our primary use case?
The main use case for Freshservice is customer ticket escalation. We receive queries from users related to requests or incidents, and our primary focus is on problem management. Day-to-day incident and problem management constitute our main responsibilities.
A specific example of how we use Freshservice for incident and problem management involves P1 or P2 alerts. When monitoring our integrated system, a ticket is automatically generated and alerts our team. The engineer serves as the agent. Based on our licensing structure, we have different users for L1 and L2 support levels. L1 performs initial troubleshooting and follows established SLAs and SOPs for analysis. If they cannot resolve the issue within their SLA timeframe, they escalate the ticket to the L2 team. L2 begins triaging the issue based on the information provided by L1 and takes over the troubleshooting process. When L2 identifies and resolves the issue, they close the ticket with resolution steps or a workaround. If they cannot resolve it, they assign it to the L3 team. When engaging L3, we use Freshservice's integration with Azure ADO, which automatically creates a ticket in Azure ADO for the L3 resource to work on. This is the current flow we follow.
For reporting purposes, we have created different reports and dashboards based on the number of use cases. We download reports and tickets based on areas we call Pods. We have created workflows for different columns in the ticketing tool for incident creation. Based on these workflows, we segregate ticket volumes to determine how many incidents are created for each Pod. This is useful for further analysis when we connect with the engineering or development teams to focus on reducing ticket volumes in particular Pods or areas.
What is most valuable?
Freshservice is stable.
What needs improvement?
Freshservice can be improved by enhancing Asset Management or CMDB accuracy. A feature that requires fewer manual updates in CMDB would be beneficial. Additionally, more advanced reporting and dashboard options would be helpful. Reporting is good, but more customization options and filters would be very useful. Furthermore, improvements in the visualization part would also be quite beneficial.
The knowledge base can be improved by making it easier to link between known errors or problem records we maintain. This would help us identify reoccurring application issues more quickly and reduce them from the knowledge base.
For how long have I used the solution?
We have been working with Freshservice for the last six to seven years in previous organizations, and our current organization is also using the same.
How are customer service and support?
The customer support has been good. Initially, we contacted them frequently, but now it is rarely needed. We would rate the support nine out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We previously used a different solution, specifically a Microsoft tool. We started with that solution, but the storage price was very high compared to Freshservice. The database storage cost was prohibitively expensive for our organization, which was one of the primary reasons for switching. Furthermore, that solution was not flexible, and the configuration was tricky for our team to train on, especially since we had previously used Freshdesk and found Freshservice to be more convenient and easy to use. Clearly, pricing and usability were the main factors for switching.
What was our ROI?
We have definitely seen a return on investment based on the use cases we have implemented. We observed improvement in resolution time and first response time. Automation has contributed significantly, resulting in reduced resource counts, which equates to savings in money and time.
What's my experience with pricing, setup cost, and licensing?
We were not heavily involved in the licensing and pricing aspects, but we participated in discussions regarding how many users would be required for the license, as our team would be primarily using this. Although we were not directly involved in the negotiations, the price was very comfortable for our organization to proceed with the migration from Freshdesk to Freshservice. It was one of our suggestions to switch for better features.
Which other solutions did I evaluate?
Before choosing Freshservice, we evaluated other options, including Zendesk . ServiceNow was also considered, but it is too costly. We had a trial long ago, and overall, our only viable option remained Freshservice.
What other advice do I have?
Our advice for others considering Freshservice is to definitely proceed with it. We have only a customer relationship with this vendor. We have provided all feedback based on our previous and current experiences using this tool. Our last two organizations have used the same tool, which has made our work significantly easier. Our overall review rating is eight out of ten.
