The latest News and Information on Incident Management, On-Call, Incident Response and related technologies.
2018 has been a momentous year at PagerDuty. We spent the past six months accelerating the development of many new PagerDuty product innovations, and have released a variety of updates and enhancements across our digital operations management platform and mobile applications.
A year ago, I introduced a new Slackbot, fondly known as Donut, to PagerDuty. When I interned in San Francisco last summer, I was looking for ways to meet people who weren’t on my team, in my department, or even in the same office as I was. Randomly messaging employees in the Toronto office or on the Sales team seemed like a little much, even for someone like me, who enjoys taking occasional strides outside of her comfort zone.
It’s no secret that PagerDuty’s robust and ever-expanding integrations ecosystem and highly engaged partner community help drive value for our customers. In addition to updating existing integrations to keep up with new product features and adding new IT tool integrations, we’re busy working on new ways to connect our shared customers to unique solutions.
An incident response process is a business process and should be treated accordingly. Because if your enterprise puts its incident response process on the backburner, the consequences could be severe.
It’s 2:37 a.m. on a Tuesday night, you’re asleep—but it’s also your turn to be on call. You receive a phone call from PagerDuty. Your partner hits you with a pillow in an attempt to wake you up. It worked. You groggily answer the call and hear your favorite robo-guy on the other end of the line.
Customers are the lifeblood of a successful enterprise. Yet too often, enterprises fail to keep their customers up to date during an outage. In these scenarios, enterprises risk alienating customers and losing them to rivals. To better understand why this may be the case, let’s consider an example.
