CUSTOM PAGE FOR EVERY AUDIENCE

Audience-Specific Status Pages

Automatically generate a custom status page for every end user based on their role and what they actually care about. Who you are determines what you see — different components, different services, different notifications, all from one status page solution.

Book a Demo

TRANSPARENCY, TRUST, AND FEWER TICKETS

Everything You Need to Serve Every Audience

Catering to different roles across your organization is hard — it usually means juggling multiple status pages and notification channels. Status Pages by IMR collapses that into one. With audience-specific pages, each end user sees only the components and services relevant to them, and hears from you only when something they depend on is affected. One solution, tailored views, less noise for everyone.

Who You Are = What You See

Catering to different roles in your company can be challenging, often requiring multiple status pages and separate notification channels. With audience status pages, who you are determines what you see. Each user gets their own view of components and services, and their own notification methods — all within a single status page solution.

Configure Audiences at Scale

Construct audience groups to assign components, incidents, and services to specific users. By combining subscription filtering with role-based access, you can generate personalized status page views and notifications for every audience — effortlessly, and at scale.

Minimize Noise, Improve Experience

Custom views cut straight to what matters for each end user. Display only the information that’s relevant to them, and mitigate alert fatigue by notifying people only when the services and components they actually depend on are affected.

Role-Based Access Built In

Control who sees what with granular, role-based permissions. Internal teams, customers, and partners each get the visibility appropriate to them — sensitive components stay hidden from audiences that shouldn’t see them, without maintaining separate pages.

BEYOND THE CORE

Everything Else That Makes Status Pages Work

Audience-specific pages should feel effortless to run. Status Pages by IMR pairs tailored views with the notification depth, filtering, and integrations that keep each audience informed without overwhelming them.

Subscription Filtering

Let audiences subscribe to only the components and services they care about, so every notification lands as relevant, never noise.

Multi-Channel Notifications

Reach each audience the way they prefer — email, SMS, Slack, Microsoft Teams, or webhook — with rules tuned per group.

Personalized Views at Scale

Generate tailored status page views for thousands of users without building or maintaining a separate page for each segment.

Custom Branding per Page

Match each audience page to the brand and voice the audience expects, from internal ops to external customers.

Real-Time Component Status

Every audience sees live, accurate component and service health the moment it changes.

WORKS WHERE YOU WORK

Built to Connect With Your Favorite Tools

Monitoring & Observability

Communication

Ticketing & ITSM

CI/CD & DevOps

Cloud Platforms

View All Integrations

Status Pages by IMR plugs into the monitoring, communication, and ticketing tools you already run — so audience pages stay in sync with real system state automatically. Set up in minutes with pre-built integrations and webhooks.

FAQ

Frequently Asked Questions (FAQs)

What is an audience-specific status page?

An audience-specific status page shows each end user only the components, services, and incidents relevant to them — all from a single status page solution. Instead of maintaining separate pages for customers, internal teams, and partners, you define audiences once and each person automatically sees the view built for their role.

How do audience groups work?

You construct audience groups and assign components, incidents, and services to them. Combined with subscription filtering and role-based access, those groups drive personalized status page views and notifications — so what a user sees and what they're notified about is determined by which audience they belong to.

Can one user belong to multiple audiences?

Yes. A user can belong to more than one audience, and their view reflects the combined set of components and services across those groups — so someone who spans teams sees everything relevant to them without a separate page for each role.

How does role-based access control what each audience sees?

Role-based access ties visibility to the audience a user belongs to. Sensitive components and services stay hidden from audiences that shouldn't see them, while each group gets the view appropriate to its role — giving you control over exposure without building and maintaining separate pages.

Can audiences choose their own notification channels?

Yes. Notification methods can be set per audience, so each group is reached the way that works best for them — email, SMS, Slack, Microsoft Teams, or webhook — and only for the services and components they actually depend on.

Does this replace running multiple separate status pages?

That's the point. Instead of standing up and maintaining a separate page for every role or customer segment, you run one status page solution and let audiences determine what each person sees. It removes the overhead of scattered pages while giving every user a more tailored experience.

How many audiences can I configure?

Audiences are designed to scale — you can generate personalized views and notifications for large numbers of users and segments without building each page by hand.

Can I brand each audience page differently?

You can tailor pages to the audience they serve, so an internal ops view and an external customer view can each carry the appropriate branding and voice.

LOVED BY 1000+ TEAMS

Trusted by Leading Teams

What sets Zenduty (now Xurrent IMR) apart from other big players in incident management is the level of interaction. If I write a query on Zenduty’s support channel, I know for a fact someone is going to come back and talk to me, and it’s very reassuring to know that my requests aren’t going into a black hole.

Heinrich Roets

Site Reliability Engineer, Electrum

Zenduty (now Xurrent IMR) offers a highly customizable alerting system. Notifications can be tailored based on severity, team, or incident type, ensuring the right people are alerted promptly. The integration with various communication channels such as SMS, email, Slack, and Microsoft Teams enhances our ability to respond quickly.

Abhishek Pal

Software Developer Engineer, Navi

Zenduty (now Xurrent IMR) is easy to use, set up, and integrate with tools. They provide excellent customer service and care, with support tickets answered immediately and feature requests quickly prioritized and added to the roadmap. As an alerting system, it sends alerts instantly, without delays or latency. The UI is clear and detailed, much clearer than those of competitors.

Tomer Cohen

Head of Cloud Infrastructure, Ever.C

“Zenduty (now Xurrent IMR)'s support team was extremely helpful and was there to answer all of our questions during our trial. They even went the extra mile by connecting us with a dedicated developer resource to help us build on top of their offerings. Truly one of the easiest tooling migrations we have ever gone through.”

Vinay Singh

DevOps Manager, IndiaMart

Mudassir Razvi

Senior Engineering Manager, DevOps at Razorpay

ITxM Platform

Status Pages

iPaaS