---
title: "Component Subscriptions for Your Status Page: Service-Based Alerts | Statusentry"
description: "Let status page subscribers choose which services they follow and only get relevant incident and maintenance notifications. Included in Statusentry Enterprise ($39.99/mo)."
url: https://statusentry.com/blog/service-based-subscriptions
updated: 2026-11-07
---

[All posts](https://statusentry.com/blog) Product

# Service-Based Subscriptions: Let Subscribers Follow Only the Services They Use

Subscribers can now pick the services they care about on your status page and only get incident and maintenance notifications for those services — by email, Slack or webhook. How it works, who gets notified and how it compares to Statuspage's component subscriptions.

Nov 7, 2026 6 min read by Statusentry team

Not every outage matters to every customer. Someone who only uses your API doesn't need an email about a slow dashboard, and a customer in Europe doesn't need to hear about maintenance in your US region. With **service-based subscriptions**, subscribers choose the services they care about on your status page, and Statusentry only notifies them about incidents and maintenance that affect those services.

[![Service-based subscriptions in StatusEntry](https://statusentry.com/images/blog/video-service-based-subscriptions.jpg)](https://www.youtube.com/watch?v=obK75p2tRHI)

Watch: Service-based subscriptions in StatusEntry (1:09 min)

Atlassian Statuspage calls this feature *component subscriptions*. It's included in Statusentry's Enterprise plan, and every new account can try it during the 30-day trial.

## What are service-based subscriptions?

A status page usually has one subscriber list: anyone who subscribes gets every update. That works while you have a single product. Once your page lists an API, a dashboard, a mobile app, a few regions and some third-party dependencies, it starts to break down. Every subscriber gets every notification, even for parts of your product they have never used.

Service-based subscriptions add one step to subscribing. When a visitor clicks **Subscribe** on your status page, they see a list of your services under *Notify me about*. They can tick the ones they use, or leave everything unticked to keep getting all updates. That choice travels with the subscription, whether they subscribe by email, Slack or webhook.

**In short:** subscribers pick their services once, and from then on they only hear about what affects them. Fewer irrelevant emails means fewer unsubscribes, and the updates they do get are more likely to be read.

## Why it matters

### Irrelevant notifications teach people to ignore you

Every notification a subscriber doesn't care about makes the next one easier to skip. After a few of them, many people unsubscribe or filter your emails into a folder they never open. Then, when an incident does affect them, the update you worked hard on goes unread and they open a support ticket instead. Sending fewer, more relevant notifications protects the channel for the moments that count.

### Customers use different parts of your product

B2B products in particular tend to have customers who only use a slice of them. An integration partner cares about the API and webhooks. A finance team cares about billing and invoices. A customer hosted in one region doesn't care about the others. Letting each of them follow only their slice makes your status page feel like it was built for them.

### Automations should only react to what's relevant

Webhook subscribers are often other systems: a customer's internal alerting, a chat bot or a ticketing tool. If a webhook fires for every incident on your page, the receiving team has to filter the noise themselves or turn the integration off. With a service selection on the webhook subscription, only incidents for the chosen services reach their system.

## How it works in Statusentry

### For your subscribers

1. They click **Subscribe** on your status page and choose email, Slack or webhook.
2. Under **Notify me about**, they tick the services they want updates for. Only public, enabled services are listed; internal services never appear.
3. They subscribe as usual. If they don't tick anything, they're subscribed to all services, exactly like before.

### For your team

- The subscriber lists in the admin panel show which services each subscriber follows, or *All*.
- Admins can change a subscriber's services at any time, for example when a customer asks to also follow your API.
- When you add a subscriber yourself or [import subscribers from a CSV file](https://statusentry.com/blog/import-status-page-subscribers), you can pick the services for them in the same dialog.

### Who gets notified

The rules are designed so that nobody misses an update they need:

| Situation | Who is notified |
| --- | --- |
| Incident or maintenance affects the Payments API | Subscribers who picked Payments API, plus everyone subscribed to all services |
| A later update (for example “Resolved”) doesn't list any services | The same people as the incident's earlier updates — affected services are collected across the whole incident |
| Incident or maintenance has no affected services at all | Every subscriber |
| Subscriber didn't pick any service | Every notification, as before |

Service selections apply to incident and maintenance notifications sent by email, Slack and webhook.

The second rule matters more than it looks. During an incident, teams often attach the affected services to the first update and then write quick follow-ups without them. Statusentry looks at all updates of the incident, so the people who got “Investigating” also get “Resolved”.

## Tips for getting the most out of it

- **Name services the way customers think about them.** “Checkout” and “Public API” are easier to pick than “svc-payments-v2”.
- **Set affected services on every incident and maintenance.** Service-based subscriptions can only filter what you tag. An incident without affected services goes to everyone.
- **Use service groups for regions or products.** A clear structure on the page makes the subscribe list easier to scan.
- **Don't force a choice.** Subscribers who want everything can simply skip the list, so the default experience stays one click.

## Plans and pricing

Service-based subscriptions are included in the **Enterprise plan ($39.99/month)**, together with 50,000 email, Slack and webhook subscribers and unlimited team members. New accounts start with a 30-day Enterprise trial, no credit card required.

If you later move to a smaller plan, Statusentry stops filtering and every subscriber receives every notification again. Nobody silently stops getting updates because of a plan change.

| Tool | Component / service subscriptions from |
| --- | --- |
| Atlassian Statuspage | Business — $399/month |
| Status.io | Basic — $79/month (all plans) |
| Statusentry | Enterprise — $39.99/month |

Monthly list prices for public status pages, checked November 2026. See the full [Statusentry vs Statuspage comparison](https://statusentry.com/atlassian-statuspage-alternative).

## Get started

1. Open **Services** in the admin panel and check that service names make sense to customers.
2. Make sure your incident and maintenance templates set the affected services.
3. Visit your status page and click **Subscribe** — the service list appears automatically on Enterprise.
4. Optionally, update the services of existing subscribers who asked for fewer emails.

Don't have an account yet? [Create one for free](https://app.statusentry.com/signup) and try service-based subscriptions during your 30-day Enterprise trial. Questions? Email [support@statusentry.com](mailto:support@statusentry.com).

## Keep reading

[All posts](https://statusentry.com/blog)

Product 6 min read

### [Add and Import Status Page Subscribers from a CSV File](https://statusentry.com/blog/import-status-page-subscribers)

Admins can now add email and webhook subscribers from the Statusentry admin panel, or import up to 5,000 at once from a CSV file. The file format, what happens to each row, and how to move your subscribers from Atlassian Statuspage.

Guides 8 min read

### [Signup Source Tracking: Know Where Your Customers Really Come From](https://statusentry.com/blog/signup-source-tracking)

Analytics tells you where visitors come from. It rarely tells you where customers come from. Why signup source tracking matters for a SaaS business, and a practical way to set it up with UTM tags, referrers, ad click IDs and a first-touch cookie.

Try Statusentry

## Communicate incidents calmly, transparently, instantly.

Start with a 30-day Enterprise trial. Afterwards, keep the free plan with no time limit.

[Start free](https://app.statusentry.com/signup) [View demo status page](https://demo.statusentry.com/)