Sorry™ Audiences:
Public and customer-specific status. One page.

But what happens when an incident affects a customer's team? Their workspace might be unavailable while your shared services are running normally.

You could give that customer a separate status page. But that’s another page to set up, another subscriber list to look after, and another place to publish updates.

That's where Sorry™ Audiences comes in. You’ll be able to keep your public services visible to everyone, while giving customers access to their own components and incident updates on the same page.

Public visitors, customer teams and internal teams can all use that page, with access to the components intended for them. And your team still has one place to manage it.

How it works

Every visitor to your status page sees something. The question is whether what they see is actually relevant to them. With Sorry™ Audiences, it is.

What a subscriber sees depends on who they are. Public visitors see your public components. Authenticated subscribers see the same public view, plus any components scoped specifically to them.

Authentication happens via access links tied to each subscriber record. No passwords, and no SSO setup required. Subscribers click a link, and they’re in. They see exactly what they’re supposed to see.

If you need a fully private status page (one that requires authentication to view anything), that’s still an option. Audiences is an addition, not a replacement.

A new component UI to go with it – An improvement for all Sorry™ customers

To support this release, the component UI (where you configure and manage the services, products, etc., on your status page) is being rebuilt from the ground up. This brings an improved component UI to all Sorry™ customers.

The new component UI will include a cleaner design, easier reordering of components, and metrics controls that live alongside your components. The new component UI is also where you’ll configure your Audiences.

With Audiences, you can control the visibility of components, metrics, and notice history for all subscribers.

What this looks like in practice

Say you’re running a SaaS platform with a mix of customers on different infrastructure, plus an internal engineering team that needs its own view. Today, your status page serves all of them, but it shows everyone the same thing.

With Audiences, that changes. You configure visibility at the component level tied to an email domain, a named subscriber, or an Audience group. Your public customers see your components that everyone sees. Each customer group sees its own components. And your internal team sees theirs. Nobody sees anything they shouldn’t.

You can control visibility across components, metrics, and historical notices. Each audience sees the components, metrics and incident history relevant to them.

How this is different

Some status page providers offer customer-specific views through a separate page that customers sign in to, alongside your public status page.

With Sorry™ Audiences, you’ll be able to keep that customer-specific information on the page you already use. Public visitors will still see your public services, while customers can sign in to see their own components and incident updates.

Managing multiple products – the enterprise use case

If you’re running multiple status pages (one per product, region, or brand), Sorry™ Collections brings them together into a single subscriber experience across all your products and services.

Audiences gives your page depth, providing a unique perspective for every visitor. Each page in your collection can also serve a unique view, so your customers see the products and components relevant to them, all in one place.

Collections and Audiences are designed to work together for enterprise organizations running at scale.

Coming soon

Audiences is in the final stages of development, and we’re targeting an October launch. If audience-specific visibility is something you’ve been waiting for, or you’d like to see how it could work for your setup, we’d love to hear from you.