Subscriber Notifications
Let users subscribe to status updates via email, Slack, Discord, and more -- and manage your subscriber list.
Subscriber Notifications
Subscribers are users who want to be notified when something changes on your status page. Instead of requiring users to manually check the page, Seenty pushes updates to them automatically.
Subscriber channels
Email subscribers
Email is the primary subscriber channel. Users can subscribe to your status page by entering their email address on the public page.
The subscription flow includes protections against abuse:
- The user enters their email address on the status page
- A CAPTCHA verification prevents automated signups
- Seenty sends a confirmation email with a verification link
- The user clicks the link to confirm their subscription
- They are now subscribed and will receive status updates
Each status update email includes an unsubscribe link so users can opt out at any time.
Integration channels
In addition to email subscribers, you can connect integration channels to your status page to broadcast updates to your team or community:
| Channel | Description |
|---|---|
| Slack | Post status updates to a Slack channel via an incoming webhook |
| Discord | Post status updates to a Discord channel via a webhook |
| Microsoft Teams | Post status updates to a Teams channel via a connector |
| Webhook | Send status updates as HTTP POST requests to any URL for custom integrations |
These integration channels are configured by your team in the status page settings, not by end-user subscribers. They are useful for keeping internal channels or community platforms in sync with your public status page.
RSS and Atom feeds
Every status page automatically generates RSS and Atom feeds that anyone can subscribe to using a feed reader. The feed URLs follow this pattern:
https://your-slug.status.seenty.app/rss
https://your-slug.status.seenty.app/atomFeeds include all public status updates -- component status changes, incident creation and resolution, and scheduled maintenance notices. They are a good option for technically inclined users who prefer feed readers over email.
What triggers a notification
Subscribers receive notifications when:
| Event | What is sent |
|---|---|
| Component status change | A component changes state (e.g., Operational to Major Outage, or Partial Outage to Operational) |
| Incident created | A new incident is posted to the status page |
| Incident updated | An existing incident has a status change (e.g., acknowledged or escalated) |
| Incident resolved | An incident is marked as resolved |
| Scheduled maintenance | A planned maintenance window is announced, started, or completed |
Subscribers are not notified for every individual escalation step or internal timeline event. Only public-facing changes trigger subscriber notifications to avoid overwhelming them with internal details.
Managing subscribers
As an organization admin, you can view and manage your subscriber list from the status page settings:
- View all subscribers -- See a list of all confirmed email subscribers
- Remove subscribers -- Remove individual subscribers if needed (e.g., spam signups that bypassed CAPTCHA)
- View subscriber count -- The total number of confirmed subscribers is shown on the status page settings dashboard
Subscribers who have not confirmed their email (clicked the verification link) are not counted and do not receive notifications.
Subscriber limits
Each status page has a limit on the number of email subscribers, depending on your plan:
| Plan | Subscribers per status page |
|---|---|
| Pro | Up to 100 |
| Ultra | Up to 500 |
| Enterprise | Unlimited |
Integration channels (Slack, Discord, Teams, Webhook) do not count toward the subscriber limit.
If you are approaching your subscriber limit, consider upgrading your plan or using RSS/Atom feeds as an alternative that does not consume subscriber slots.