# Component-level status subscriptions before broad blasts

> Let customers subscribe to the product component they actually use so incident communication lands on the right inboxes instead of becoming background noise.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/component-level-status-subscriptions-before-broad-blasts/
- Source: [support.atlassian.com](https://support.atlassian.com/statuspage/docs/enable-component-subscriptions/)
- GrowthDex source hub: [Atlassian Statuspage Docs: Enable component subscriptions](/sources/atlassian-statuspage-docs-enable-component-subscriptions-support-atlassi/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: low
- Channels: Lifecycle, Support, Product
- Stages: incident comms, customer messaging, retention, self-serve support


## Why this can grow

Most status communication gets ignored because it asks every customer to care about every system. Component subscriptions make the alerts narrower. A developer using the API can subscribe to the API component while a merchant watching checkout can subscribe to payments. That cuts false urgency, reduces alert fatigue, and makes the next real incident update more likely to be opened and believed. It also lowers support load because people get direct updates about the part of the product they depend on, rather than having to infer whether a vague site-wide warning applies to them.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. For retention, I would watch the second and third use, not just the first click. A tactic is real when it changes a habit. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where component-level status subscriptions before broad blasts can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Lifecycle and Support channel.
3. Use the evidence from support.atlassian.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Statuspage lets page admins enable component subscriptions so subscribers can receive updates only for the components they choose instead of every incident on the page.

## Adjacent tactics in the same lane

- [Customer-ready completion triggered by release production](/growth-ideas/customer-ready-completion-triggered-by-release-production/) - 3 shared channels, 1 shared stage
- [Dedicated status domain before first incident](/growth-ideas/dedicated-status-domain-before-first-incident/) - 2 shared channels, 2 shared stages
- [Scheduled maintenance reminder before the window opens](/growth-ideas/scheduled-maintenance-reminder-before-the-window-opens/) - 2 shared channels, 2 shared stages
- [In-product help links at friction points](/growth-ideas/in-product-help-links-at-friction-points/) - 3 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The status page should answer before the ticket does](/blog/the-status-page-should-answer-before-the-ticket-does/) - brand trust, incident communication, support deflection

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.