We performed a comparison between Freshservice and PagerDuty Operations Cloud based on real PeerSpot user reviews.
Find out what your peers are saying about ServiceNow, Atlassian, BMC and others in Help Desk Software."The admin feature is the UI, so it's very clean. The asset management and its model are valuable as well."
"I do like the workflow automation capabilities, where based upon certain actions, it will automatically go and route tickets to a particular person. It is fairly user-friendly."
"The overall functionality of the product is excellent."
"What I have seen in Freshservice is there's no room for customization. Which works as an advantage in some cases and it works as a disadvantage in others. If you are someone that starts managing your IT services, it is a great solution, because there's no way to go out away from the direction of the system. You have to follow the process as it was intended for the designers of a solution because there's no room for customization or configuration."
"The solution’s timely automated triggers increase our IT team’s productivity."
"The most valuable feature is the sandbox, which allows me to test new configurations, automations, and workflows before taking them live on the production system."
"Freshservice has automated a lot of our tasks, including ticket responses and call assignments, which has sped up our operations considerably."
"It has a very easy, flexible model. You can open up a particular module and work on the next. That's what we did. Overall, it provides a simple way of getting your support teams up and running. That was one thing that I thought was quite easy to do."
"The SMS pages and the mobile application are pretty much the top two features."
"The product easily integrates with other solutions."
"The initial setup is straightforward."
"PagerDuty is very stable and very reliable."
"It has scaled well for us."
"PagerDuty let us set up rosters based on our shifts. We could assign a hierarchy for how the calls should be escalated and the number of times the call will be transferred between people before it is answered. It makes it easy to access an agent via mobile phone."
"The most valuable features of PagerDuty are customization, access, policies, and different rules regarding the path of escalation. Additionally, it's easy to use and create overrides. For example, if you all are on a call for one week each, but somebody wants to go on PTO, the team needs to swap shifts in PagerDuty. This is easy to do by creating overrides to switch up the set schedules. It's very user-friendly in that aspect. It works well for monitoring and alerting."
"The inbound integrations that PagerDuty provides with most of the DevOps tools are valuable."
"The round robin ticketing feature that they have is not ideal."
"The most significant area for improvement is consistency across the different modules, as they are inconsistent. 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 instant management, but not in problem management, for example, and I don't see why that should be the case. It would be good to see more consistency in the development process."
"The ability to customize the user interface is a bit lacking, and the reporting is a bit lacking because they're very stringent upon what you can pull reporting-wise within Freshservice. They have a lot of built-in reports that are very nice, but when it comes to customizing these, they just provide you with certain data. When you try to build your own report wizard, you aren't able to go and select some of the data that is shown in some of the reports that come with Freshservice. This is something that we have brought up with our account representative, and we have suggested these as feature updates in the future. We're still waiting on them to go and implement something like that."
"I would suggest that Freshservice enhance its technical capabilities, particularly when it comes to ICT network discovery."
"We haven't had any issues with the stability of Freshservice. However, we have had some issues with data imports, we have noticed that large amounts of data can get stuck. This is something that we haven't seen in other solutions."
"On the reporting side, when we were doing reporting, one thing that was a bit of a limitation was when you had a data list containing a list of changes that have occurred for the whole time and you had to fit the list onto a page. If the list went over the page, it would just truncate it at the page. You wouldn't get all your data. So, it didn't work. That was one big stand-out for me. What we tended to do was convert things into a more readable format, and then we had more targeted exception reporting, but it would be nice to have a full list of things that could be automatically generated and that can flow over pages."
"The reporting and management information (MI) are very limited, and stopped realistic and timely reporting on outstanding incidents."
"You can't implement a complicated delivery workflow. We don't have the same problems with incident and change workflows. It's only for delivery workflow. They have a mechanism for modifying your incident or change workflow. There's a visual interface for that, so there's no reason not to have the same function for request management."
"I would like the UI to be more intuitive. I would like to be able to group or color-code the discoveries. When you create a system, you have a listing of all the different configurations. You can list them by teams, but some additional color coding would be helpful. I would break it down by incident controls. In other words, it should be broken down it into response teams and engineering divisions."
"Something that needs to be improved, is adding multilingual support."
"The product can be improved by including out-of-the-box integration with other standard tools used in our fields such as Confluence, and Jira."
"I am not a direct end user of PagerDuty. It's hard to consider its shortcomings in that sense."
"It is a very non-customizable product, so you cannot add things like root cause analysis or the classification of incidents based on the area where you are getting more incidents. For example, if you're getting a lot of database issues, that may be an are you want to probe."
"The solution's analytics are okay. I don't think the features, at this point, give you a lot of insights. We have actually been trying to get insights from it but it hasn't really given us a lot of extra points to explore. We were looking at the number of alerts to see where many of the alerts were coming from. We never managed to get many insights on this."
"The On-Call Teams feature could be better in terms of levels of conditions related to which team or member should get the responsibility of handling a matter or incident."
"The user interface could be more intuitive."
Freshservice is ranked 5th in Help Desk Software with 29 reviews while PagerDuty Operations Cloud is ranked 1st in IT Alerting and Incident Management with 35 reviews. Freshservice is rated 8.0, while PagerDuty Operations Cloud is rated 8.8. The top reviewer of Freshservice writes "Provides excellent traceability along with improved efficiency and reliability". On the other hand, the top reviewer of PagerDuty Operations Cloud writes "Effectively generates alerts for incidents, making it suitable for 24/7 monitoring of infrastructure". Freshservice is most compared with ServiceNow, JIRA Service Management, Microsoft Project, Zendesk and ServiceNow IT Operations Management, whereas PagerDuty Operations Cloud is most compared with Opsgenie, ServiceNow, JIRA Service Management, Everbridge IT Alerting and Splunk On-Call.
We monitor all Help Desk Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.