Blameless announced the availability of its new CommsFlow product capability, designed to keep all stakeholders updated as the reliability of services and applications are impacted by incidents.
The new CommsFlow streamlines all communication during and after incidents, significantly speeding up the critical task of delivering context-rich and timely updates to customers and internal teams. Updates are automatically sent at workflow transitions or as task reminders for on-call engineers, reducing the cognitive load, speeding time to resolution, and improving learning.
Blameless’ new CommsFlow is designed to run effective, automated, and comprehensive communication strategies, from incident resolution to retrospectives after completion. It makes the lift much lighter, keeps everyone up to speed, and most importantly, frees up engineering focus time.
Additional enhancements include tighter integration with Pagerduty, StatusPage, and Microsoft Teams Chat and Video. These features give engineers full control when managing incidents from beginning to end. Operations run smoothly, and teams focus precious time on development work.
Blameless New Product updates include:
- CommsFlow: Automatically triggers communication flow using email, SMS, Slack, and Microsoft Teams based on changing incident and retrospective workflow conditions.
- Microsoft Teams: Blameless integration and chat bot now available on the Microsoft AppSource.
- Statuspage: Integration provides finer control of the specific services (components) that incidents are affecting.
- Pagerduty: Now users bring more context to incidents by linking the Pagerduty services impacted with simple bot commands inside your messaging tool.
“Managing incidents requires focused energy from your team. If we can alleviate that burden with features that automatically communicate at the right moments, it’s a game changer for on-call teams,” said Lyon Wong, Co-Founder and CEO, Blameless.
The Latest
The 2024 State of the Data Center Report from CoreSite shows that although C-suite confidence in the economy remains high, a VUCA (volatile, uncertain, complex, ambiguous) environment has many business leaders proceeding with caution when it comes to their IT and data ecosystems, with an emphasis on cost control and predictability, flexibility and risk management ...
In June, New Relic published the State of Observability for Energy and Utilities Report to share insights, analysis, and data on the impact of full-stack observability software in energy and utilities organizations' service capabilities. Here are eight key takeaways from the report ...
The rapid rise of generative AI (GenAI) has caught everyone's attention, leaving many to wonder if the technology's impact will live up to the immense hype. A recent survey by Alteryx provides valuable insights into the current state of GenAI adoption, revealing a shift from inflated expectations to tangible value realization across enterprises ... Here are five key takeaways that underscore GenAI's progression from hype to real-world impact ...
As software development grows more intricate, the challenge for observability engineers tasked with ensuring optimal system performance becomes more daunting. Current methodologies are struggling to keep pace, with the annual Observability Pulse surveys indicating a rise in Mean Time to Remediation (MTTR). According to this survey, only a small fraction of organizations, around 10%, achieve full observability today. Generative AI, however, promises to significantly move the needle ...
While nearly all data leaders surveyed are building generative AI applications, most don't believe their data estate is actually prepared to support them, according to the State of Reliable AI report from Monte Carlo Data ...
Enterprises are putting a lot of effort into improving the digital employee experience (DEX), which has become essential to both improving organizational performance and attracting and retaining talented workers. But to date, most efforts to deliver outstanding DEX have focused on people working with laptops, PCs, or thin clients. Employees on the frontlines, using mobile devices to handle logistics ... have been largely overlooked ...
The average customer-facing incident takes nearly three hours to resolve (175 minutes) while the estimated cost of downtime is $4,537 per minute, meaning each incident can cost nearly $794,000, according to new research from PagerDuty ...
In MEAN TIME TO INSIGHT Episode 8, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses AutoCon with the conference founders Scott Robohn and Chris Grundemann ...
Numerous vendors and service providers have recently embraced the NaaS concept, yet there is still no industry consensus on its definition or the types of networks it involves. Furthermore, providers have varied in how they define the NaaS service delivery model. I conducted research for a new report, Network as a Service: Understanding the Cloud Consumption Model in Networking, to refine the concept of NaaS and reduce buyer confusion over what it is and how it can offer value ...
