Operations | Monitoring | ITSM | DevOps | Cloud

The chaos of manual on-call management is a familiar story for many IT Operations teams: frantic phone calls, confusing spreadsheets, missed alerts, and frustrated engineers on the verge of burnout. This reactive approach doesn’t just strain your team; it risks service-level agreement (SLA) breaches and customer churn.

It’s been a busy quarter at OnPage. We recently rolled out our updated Enterprise Management Console to a select group of beta customers, and the early feedback has been exciting to see. The new experience gives teams a cleaner, more modern way to manage critical communication workflows, on-call schedules, alerting activity and team visibility from one place. But we have not slowed down there.

The impact vision for PagerDuty.org is to enable mission-driven teams to build a resilient world and a sustainable future for all. As a leader in modern, AI-first operations, we know that operational excellence supercharges social impact. As artificial intelligence rapidly reshapes the social sector, this commitment to resilience and efficiency has never been more vital.

Creating incidents often means filling out the same information over and over again. That’s why we’ve added Incident Templates – a faster way to create incidents using pre-configured settings. With templates, you can save commonly used incident details and apply them with a single click whenever you need them.

IncidentHub's latest product update includes private status ingestion for Microsoft Azure and Microsoft 365, a simpler UI for alerts configuration, an option to disable the public status page, and a better looking status page layout. Plus, support for more vendors (1070+ and counting). As always, I am grateful to all our customers and beta testers who have shared their feedback which has made IncidentHub better.

When a major IT incident hits, most organizations know what it costs in the moment: lost transactions and missed SLAs. But according to the findings of our 2026 State of AI-First Operations report, the most significant consequences often don’t show up until long after the incident is closed—in customer relationships, team health, and brand reputation.

Many teams invest time building an on-call rotation, but inbound calls often ignore that structure completely. A support number forwards to a single phone. One engineer ends up taking every call. Sometimes the call goes unanswered and the voicemail lands in a shared mailbox that nobody checks until the next morning. Even worse, the team might have several engineers on duty, but the phone system has no awareness of who is actually responsible at that moment.

When incidents are not addressed – or not addressed quickly enough – businesses incur significant costs. Mean Time to Resolution (MTTR) increases. In the worst cases, the financial impact extends beyond your organization to customers and partners. Automated alerting reduces response times and notifies the right people when action is needed.