The three primary goals of a hosted status page are:

1. to improve the customer experience by proactively communicating when there are issues with your application and when those issues are resolved,
2. to improve customer retention by contextualizing issues within your long track record of excellent service, and
3. to reduce the burden on your IT/DevOps team by handling the communication side of things.

PagerDuty is an intelligent operations platform that provides a dashboard view of the various tools you use to track incidents in your application(s), making managing multiple alert tools much more manageable! It also routes alerts to the appropriate engineer or manager via their preferred communication channel (e.g. email, text, phone, push notification).

Similarly, using a webhook integration, StatusCast pulls designated alerts from PagerDuty, allows you to rephrase them into terms more relevant to your end-users, and sends them out to impacted users via each individual user’s preferred communication channel. As with all status updates in StatusCast, you can program them to send immediately, to send automatically but with a time delay, or to require manual approval before being sent at all.

Using a Hosted Status Page to Bridge the Customer Experience Gap

PagerDuty allows for delivery confirmation and automatic re-routing of alerts, so that you can ensure that the issue is being taken care of on your end. This is great internally – but what about on the customer end? This is where a hosted status page comes in. An email blast might be read by some users, but it won’t necessarily be those affected by the incident (which could do more harm than good) and it won’t necessarily be noticed if email is not the best method of communication for alerting users about application performance.

StatusCast helps you bridge the customer experience gap by sending out alerts based on affected components (meaning only impacted customers receive the communication), and sending them out through the communications channel your customers have identified themselves to be most effective for status updates.

Using a Hosted Status Page to Bridge the Customer Retention Gap

PagerDuty recently announced downtime insurance for their enterprise level customers – read more about that here. This demonstrates their commitment to keeping their customers, and to helping their customers retain their own customers in turn. Though PagerDuty stands behind their product, they have processes in place to accommodate for the unlikely disruption.

StatusCast is built with a similar idea in mind – though downtime is unlikely, to an extent it is unavoidable. Rather than deny that unpleasant truth, better to be prepared to handle it professionally. By providing the history of uptime on your hosted status page, you are reminding customers when downtime occurs that it is a rare occurrence rather than the norm.

Using a Hosted Status Page to Bridge the IT/DevOps Efficiency Gap

PagerDuty professes that: “Ops and dev engineers should spend their time resolving the right problems and building great products, not responding to alert spam, dealing with on-call burnout and wasting time elbow deep in root cause analysis. We know this first hand and want to give engineers what’s needed to improve system reliability and quality of life.”

One of the reasons StatusCast was built as a hosted status page tool in the first place was to help IT/DevOps focus on resolving the issues impeding application performance, by taking the burden of communicating about the issue and its resolution off of that team’s shoulders. By working with another team (for instance Marketing) in advance, to ensure the customer-facing alert language is user-friendly but accurate, IT/DevOps can free themselves to focus on what they do best when the need for their timely attention is at its greatest.