# Overview

Manage org-wide notification subscribers by channel.

Source: https://statusdashboard.com/docs/subscriptions

Subscriptions are **customer and end-user** notification subscribers across your organization: people who sign up on status dashboards to receive event alerts via **email**, **SMS**, or **WhatsApp**. Each channel has its own subscriber list, quota, and admin workflows. See [Email](/docs/subscriptions/email), [SMS](/docs/subscriptions/sms), and [WhatsApp](/docs/subscriptions/whatsapp) for channel-specific tasks.

***

## Plan entitlement vs. quota
Each consumer channel has a **plan entitlement** plus separate numeric quotas. The entitlement controls whether the product feature is available at all: public subscribe, admin subscriber management, and event notification delivery. Numeric quotas enforce capacity only; they do not turn a channel on by themselves.

| Channel      | Plan entitlement    | Subscriber quota                                                                     | Monthly send quota                                                     |
| ------------ | ------------------- | ------------------------------------------------------------------------------------ | ---------------------------------------------------------------------- |
| **Email**    | Enabled or disabled | **Email subscribers** — maximum unique email addresses (pending and verified)        | **Emails per month** — event notification sends (UTC calendar month)   |
| **SMS**      | Enabled or disabled | **SMS subscribers** — maximum unique E.164 phone numbers (pending and verified)      | **SMS per month** — event notification sends (UTC calendar month)      |
| **WhatsApp** | Enabled or disabled | **WhatsApp subscribers** — maximum unique E.164 phone numbers (pending and verified) | **WhatsApp per month** — event notification sends (UTC calendar month) |

Transactional verify and manage messages do **not** count toward the monthly send quota. See each channel page for examples.

SMS and WhatsApp both use phone numbers, but subscriber quotas are tracked **separately per channel**. The same number subscribed to both SMS and WhatsApp consumes one slot in each quota.

## Subscriber quota model
Subscriber limits work the same way on email, SMS, and WhatsApp:

* Your plan sets a maximum number of **unique contacts org-wide**, not per status dashboard. Email counts unique **email addresses**; SMS and WhatsApp each count unique **phone numbers**.
* A visitor who signs up with a **new** contact consumes **one** slot when the first subscription record is created (public sign-up, admin add, or import), including while the subscription is still **pending**.
* The same contact subscribing on an additional status dashboard does **not** consume another slot.
* When the org-wide limit is reached, **new** contacts are rejected at sign-up time. Contacts **already in your organization** may still subscribe on other dashboards.
* If a visitor never completes verification, the pending record expires after **24 hours**. The quota slot is released automatically once that pending record is removed. Removal may take up to an additional **48 hours** to process, so the slot may still appear consumed in the admin quota bar during that window.

Public sign-up, verification, and manage flows use the same double opt-in pattern on all three channels.

## Related configuration
Per-dashboard **Subscriptions** toggles control whether visitors can sign up on a given status dashboard. The channel must be **enabled on your plan** and the dashboard toggle must be on for it to appear on the **Subscribe** link.

See [Status dashboard subscriptions](/docs/status-dashboards/subscriptions) for visitor flows and dashboard toggles.

## When components or dashboards are removed
**Deleting a component** removes it from any status dashboards that reference it. Subscribers who were only following that component on a dashboard are removed automatically. Subscribers who still follow other components on the same dashboard keep their remaining selections. If removing a subscriber leaves an email address or phone number with no active subscriptions anywhere in your organization, that contact is freed from your subscription quota for that channel.

**Removing a component from a dashboard** (without deleting it from your organization) applies the same subscriber rules on that status dashboard only: orphan subscribers are removed, multi-component subscribers keep their other selections, and quota is released when a contact has no remaining subscriptions org-wide for that channel.

**Deleting a dashboard** removes all subscribers associated with that status dashboard. Any email addresses or phone numbers that no longer have subscriptions elsewhere in your organization are freed from your quota for the relevant channel.