The world’s largest eCommerce site adopts OnPage to streamline its operations and workflows. This news showcases OnPage’s continuous growth in the business-to-business (B2B) space, providing a reliable and secure critical alerting solution for different use cases. In this blog post, I’ll be discussing how the eCommerce juggernaut leverages OnPage’s live call routing capabilities to enhance team communications.

With the implementation of electronic health records (EHRs) into practices, patient experience has improved, among other advancements at the point of care. These include better access to patient records and highly efficient care delivery. While these are some significant benefits, some practices experience certain drawbacks too, such as temporary slowdown of processes during EHR transition and high ongoing maintenance costs. One of the most pressing issues include patient record retention.

One of our customers came to us asking for a way to easily log tickets created during the night shifts in order to allow team members to be up to date on any nightly occurrences even when the On-Call staff hadn’t been at the office yet. Our initial suggestion was to just send a broadcast message to the team members inboxes but due to concerns that such a setup would just add clutter we investigated alternate ways of providing this functionality.

Outages are inevitable. It is how we respond that can make or break our company. In this post, we will talk about how Service Catalogs can impact your incident response process and make it more effective. When a company has just a handful of services, it can be relatively easy to figure out who to call when something breaks. But when companies are at the stage of having dozens of services to manage, figuring out who to page or reach out to can be a challenge.

Doing on-call management in a way that’s better, less stressful and actually works to improve your incident response processes, uptime & reliability.

One of the most important steps in an incident’s lifecycle is the postmortem. It provides an essential time to reflect on what happened, what could have been done better, and how to build more resilience into a system. But we consistently hear from engineers that incredible toil is typically involved in coordinating stakeholders to write good postmortems.

With Priority-Based Alerting, you can set different notification rules for high and low priority incidents.