PagerDuty is an IT alert and incident management application from the company of the same name in San Francisco.
$25
per month per user
ServiceNow IT Operations Management
Score 8.8 out of 10
N/A
Built on the Now Platform, the ServiceNow IT Operations Management bundle is designed to help users gain visibility across infrastructure and apps, maintain service health, and optimize cloud delivery and spend.
PagerDuty seemed to have a much more flexible setup that allowed the organization to build and manage how we respond to alerts and incidents. The ServiceNow product seemed to be a bit more rigid.
I think PagerDuty works great for medical practices. I have used other platforms through other companies, and PagerDuty is by far the best platform. It is because of the different features it has to communicate to other staff members how the call is being handled. It is easy to learn how to use.
[...] is changing the way our internal support staff (not only in the IT field) work and enhancing the experience for employees seeking IT assistance through ServiceNow IT Operation Management. We have moved the usual and personalized IT tools and functions from [...] service-desk to ServiceNow IT Operations Management. These advancements have sparked innovation in various aspects of our IT support management, such as enhancing accessibility, managing incidents, optimizing IT workflows and procedures, enforcing service level agreements (SLAs), incorporating AI/ML technology, utilizing virtual agents, streamlining automation, and sharing knowledge throughout the support team via data visualization, monitoring, and reporting. In brief, our collaboration with ServiceNow IT Operations Management is enhancing the effectiveness of our internal system and benefiting our shared clients.
In platform expertise and workflows, so we don't allows have to build everything from scratch.
Tight integration within ServiceNow (especially ITSM) but also brings information and data in from other sources, so I don't feel we are stuck in a proprietary hole.
Increased investment in AIOps and automation
Relatively fast time to value with out-of-the-box capabilities and automation.
When getting a phone call, PagerDuty doesn't seem to allow acknowledgments of alerts through the phone, which it says it does. I constantly receive a message that it was updated by another person - when in reality, it wasn't.
Smarter notifications. If an alert was snoozed for a time, when it comes back, it sends out another alert. It should, I think, send a message asking if the alert is still an issue and give the option to close.
The UI is more complex than I would like. Part of the challenge is that most users use PagerDuty infrequently; I don't remember how I changed a policy last time. Another part of the challenge is that some users expect alerting to be a trivial feature, and are reluctant to invest any time in reading the documentation.
We achieved in financial what we are aiming for, as our targets are fulfilled, we solved many issues using ServiceNow, Creation of knowledge article improved, Ticket system got customized, overall survey from the customer is 4 out of 5, customization is done without any hustle and integration was very easy.
PagerDuty is reliable and easy to set up. It gives an effective way to notify the team about critical incidents which results in a faster turnaround time on issues. users can customize their alerts rules based on their preferences. Overall it's effective and easy to use which adds great business value.
I have not use the 2 technologies for as long as I have used PagerDuty but in my opinion PagerDuty makes things a lot easier. The other tools got the job done and got alerts out but PagerDuty just seemed to make the setup for on-call alert schedules and integrations easier than the others. This isn't to say the others are difficult, just that PagerDuty was slightly better. I also have noticed that more tools have options to integrate to PagerDuty over the other tools.
We wanted it integrated with ITSM and ITBM. Prioir to that we used JIRA for agile development and SysAid for ticketing. So we started with converting SysAid. We went live with Vanilla ITSM. Then we could have a basis for ITOM. However, we needed to migrated from JIRA to ITSM. Only then we felt mature enough to examine ITOM, which required quite a lot of resources. You need networking, motoring, IT and Cyber security team members in your project!!
![Screenshot of Similar Incidents [Apple iPad], Open Incidents [iPhone 8], On-Call Schedule Menu [Apple Watch])](https://media.trustradius.com/product-screenshots/kf/M5/L6SIK3HGD31M.png)
