PagerDuty announces the availability of Response Mobilizer and Response Bridge, two new features that enable seamless collaboration between responders for dynamic incident response and faster resolution.
Using PagerDuty’s new Response Moblizer feature, customers can notify and enlist additional experts and critical stakeholders to an incident. With the PagerDuty Response Bridge, customers can share a conference bridge for real-time collaboration on open incidents. Together, these features allow customers to respond at scale with the right people and contextual information for faster incident resolution.
Outages in the digital economy have serious customer experience and revenue implications that push ITOps and DevOps teams to constantly seek better tools and processes to mitigate the impact on their business. Critical incidents typically require a greater level of organization because the impact can span across multiple teams and business units, however, delays in enlisting the right subject matter experts cross-functionally can be detrimental for a time-sensitive resolution. Beyond the standard on-call schedules, PagerDuty Response Mobilizer allows customers to rapidly bring the right people together with the right contextual information to address business-critical issues in real-time. By helping customers recruit the right responders, PagerDuty reduces mean-time-to-resolve (MTTR) by minimizing the amount of time spent searching for responders . After gathering the right responders and key stakeholders, PagerDuty Response Bridge enables teams to collaborate via their existing conference bridge or chat tools. With custom messages that include critical incident context for new responders, PagerDuty provides a single incident view to coordinate the ideal response.
PagerDuty Response Mobilizer and Response Bridge enables customers to:
- Notify the Right People: Easily select and invite individuals by name or escalation policy to collaborate directly on any PagerDuty incident
- Mobilize Teams Immediately: Decrease response times by customizing how team members are notified (phone, push notifications, SMS), and identify their response status in real-time and escalate if necessary
- Access Contextual Information: Include a brief message to responders detailing why they are needed and leverage the rich, contextual details already embedded inside every incident so all responders are immediately aligned
- Conferencing Support: Include meeting details in any PagerDuty incident and invite responders to collaborate in a meeting, dramatically reducing MTTR
- Leverage existing Conferencing Platform: PagerDuty supports multiple conferencing providers, including Cisco WebEx, GoToMeeting, and Blue Jeans, so teams can operate within their established communication channels
“Many companies take 30-60 minutes just to get the right people on a conference bridge during business-impacting outages or incidents,” said Tim Armandpour, SVP of Product Development, PagerDuty. “When down-time is your business’s enemy, how fast you respond to an incident matters to the bottom line. PagerDuty Response Mobilizer and Response Bridge drastically reduce the amount of time and effort needed to collaborate and resolve an incident, but more importantly, mitigate a business issue.”
PagerDuty Response Mobilizer and Response Bridge are available now to all Standard and Enterprise customers.
The Latest
In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...
Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...
Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...
Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...
The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...
The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...
In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...
AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.