I have been using Freshservice for approximately five months through the AWS marketplace. During this time, I have handled incident management, workflow automation, and internal IT requests. I have also explored integrations with AWS services such as CloudWatch and S3 to streamline monitoring and ticket management.

The main use case for Freshservice is managing IT services, requests, and incidents across cloud environments. On a typical day, I use Freshservice to track and resolve internal AWS-related requests, such as EC2 instance access issues or S3 bucket permission changes. I also assign tickets, set SLAs, and use automation rules to route them to the right team members. Integrating Freshservice with AWS CloudWatch allows us to receive alerts directly into the platform, so we can respond quickly to issues without constantly monitoring multiple dashboards.

I find Freshservice automation rules fairly intuitive for basic workflows such as auto-assigning tickets or sending notifications when certain conditions are met. Setting them up is mostly straightforward through the rule builder. When integrating with AWS CloudWatch, it is more technical because you have to set up SNS topics or Lambda triggers to push alerts into Freshservice, which requires some knowledge of AWS services. Once configured, it works reliably and saves a lot of manual effort. The main challenge I encountered was mapping CloudWatch events to the right ticket categories and ensuring alerts do not create duplicate tickets. After fine-tuning the rules and testing different scenarios, the integration became smooth and efficient.

Using Freshservice via the AWS marketplace allows us to leverage AWS security and scalability. All ticket attachments can be stored securely in S3, and we can use CloudWatch for proactive monitoring. The automation of repetitive tasks such as routing tickets or triggering notifications based on AWS events saves the team a lot of manual effort. The combination of Freshservice and AWS helps us maintain high service reliability, streamline IT operations, and quickly respond to issues.

The best features that Freshservice offers include automation because automating repetitive tasks such as ticket assignments and SLA notifications saves a lot of time and reduces human error. Integration is another key feature because the ability to integrate with AWS services such as CloudWatch, S3, or Lambda is a huge advantage. Alerts and events from AWS can directly trigger tickets or updates, making incident management much more efficient. Reports and analytics are also valuable because Freshservice dashboards and reports give much clearer visibility into ticket volumes and team performance, helping with continuous improvement. The Service Catalog, also known as workflow management, has predefined workflows for common IT requests, streamlining approvals and provisioning, especially when managing cloud resources. These features make managing IT operations in an AWS environment much more efficient and reliable.

The reporting and dashboard in Freshservice are really helpful for our team because they give us a clear overview of ticket volumes, SLA compliance, and response times. We can quickly see which types of AWS-related requests, such as EC2 access issues or S3 permission changes, are taking longer to resolve. These insights allow us to identify bottlenecks, adjust workflows, and improve SLA compliance. After noticing recurring delays in AWS resource provision requests, I created automation rules to route these tickets faster, which significantly reduced resolution time. The dashboard also helps when communicating team performance to management by providing visual evidence of how efficiently we are handling IT requests and AWS operations. The analytics helps us work smarter and continuously improve our processes.

Freshservice's self-service portal and knowledge base are very useful because users can resolve simple AWS-related requests on their own, which reduces the number of tickets that reach our team. The combination of automation, integrations, and reporting ties everything together, making our workflow efficient, transparent, and easier to manage. All of these features help us maintain high service reliability and respond to issues much faster.

Freshservice has had a significant positive impact, especially when managing AWS-related IT operations by centralizing incident management and automating repetitive tasks. Our team has become more efficient and responsive. Faster ticket resolution thanks to automation rules and integration with AWS, improved SLA compliance, and dashboards and reporting give visibility into team performance. The Service Catalog and predefined workflows allow us to handle common AWS requests such as EC2 access or S3 permission changes consistently. Freshservice has changed the way our team works by making processes more organized, measurable, and efficient, allowing us to focus on higher value tasks instead of manual ticket handling.

According to my experience, Freshservice works very well, but there are a few areas where improvements would help. The AWS integrations could be deeper; for example, CloudWatch alerts come in correctly, but more native mapping for metrics, log data, and enrichment would make incident handling much faster. The automation workflows are powerful, but the UI can feel limited; once the workflows get complex, it becomes hard to visualize them. A cleaner drag and drop builder or better debugging options would help reduce mistakes. Reporting is useful, but the customization is still restricted, and it would be great to build more detailed reports that combine multiple data sources, especially for cloud-related operations. The mobile experience can feel slow at times; most technicians rely on mobile alerts, so a more responsive app would make a difference. I would also like more flexibility with ticket forms and dynamic fields since we want conditional fields that change based on AWS resource types or alert categories, but that is not always possible. The platform is strong, but deeper cloud integrations, more flexible automation, and better reporting would make it even more effective.

Small details that would improve the platform include alert noise reductions, such as CloudWatch alerts coming in too frequently; Freshservice could offer better built-in correlations or group similar alerts automatically. Faster syncing between AWS resources and Freshservice assets would help keep the CMDB aligned with real cloud changes. Better tagging support, more templates for cloud incidents, and finer control over role permissions are needed. I would like more templates for cloud incidents.

I have been using Freshservice for approximately five months.

Freshservice is stable at the moment. We have not encountered significant downtime or reliability issues. The service runs smoothly most of the time, and performance has been consistent even when ticket volumes and AWS alerts are high.

Freshservice scales very well. As our organization has grown and ticket volume related to AWS resources increased, Freshservice handled the extra load without any performance issues. The automation, reporting, and integration features continue to work smoothly even when demand increased.

Freshservice's customer support is responsive and helpful. When we have questions about configuring AWS-related integrations and automation rules, we reach out via the support portal and get clear answers in a reasonable time. Their documentation is also good, making setup easy without needing frequent support requests. Support is reliable enough for our needs; sometimes, responses take a bit longer when issues are complex, but overall it is adequate.

Before Freshservice, we used a more basic ticketing tool that did not integrate well with AWS or support advanced automation. We switched to Freshservice because it offered better cloud integrations, automation, reporting, and workflow management, allowing our team to handle AWS-related IT requests more efficiently and reliably.

The pricing is reasonable for the features we needed, and the setup did not require any additional costs on our side since it is a cloud-based service. Licensing is very straightforward and easy to manage; we mainly had to choose the plan that matched our workload, and after that, everything is simple to maintain.

We have seen a tangible return on investment with Freshservice. Time saved is approximately twenty to twenty-five percent, which frees up our engineers to focus on more high-value tasks. Faster resolution means the average ticket resolution time decreased by roughly twenty-five to thirty percent since alerts are automatically converted into tickets and routed to the right team. SLA compliance improved from eighty percent to ninety-five percent, which reduces delays and improves reliability for internal IT requests. We did not need to hire additional staff to handle AWS-related incidents because the current automation and reporting streamline workflows very efficiently. These improvements translate into fast response times, better resource utilization, and reduced operational overhead, which we consider a clear return on investment.

We did not purchase Freshservice through the AWS marketplace. We use it separately from our main AWS billing.

Before choosing Freshservice, we evaluated a few other IT service management tools such as ServiceNow and Jira Service Management. We decided on Freshservice because it offered a good balance of automation, cloud integrations with AWS, reporting capabilities, and ease of use for our team, meeting our needs without being overly complex or costly.

If I have to give advice to others looking into using Freshservice, I would advise taking advantage of Freshservice's automation and cloud integration from the start, especially if you are using AWS. Setting up workflows and alerts early ensures tickets are automatically routed and prioritized. Investing time in reporting dashboards helps identify bottlenecks and improve SLA compliance quickly. Testing and customizing your workflows to match your organization's specific processes is key, as that is where Freshservice really delivers value. Careful planning for your setup will make it much more effective.

Freshservice has been a strong solution for our organization, especially when used with AWS. It has improved efficiency, reduced ticket resolution times, and streamlined our workflows. The main areas for improvement would be deeper AWS integrations, more flexible automation and reporting, and a smoother mobile experience. It is reliable, scalable, and a tool our team depends on daily, and I would recommend it to other organizations looking for a cloud-friendly IT service management platform. I give this product a rating of eight out of ten.