# Scheduled maintenance reminder before the window opens

> Publish planned maintenance on the status page early enough that subscribers get both the announcement and the one-hour reminder before the work starts.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/scheduled-maintenance-reminder-before-the-window-opens/
- Source: [support.atlassian.com](https://support.atlassian.com/statuspage/docs/schedule-maintenance/)
- GrowthDex source hub: [Atlassian Statuspage Docs: Schedule maintenance](/sources/atlassian-statuspage-docs-schedule-maintenance-support-atlassian-com/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: low
- Channels: Lifecycle, Support, Brand
- Stages: incident comms, customer trust, retention, operations
- Key metric: Statuspage can send a reminder to email and SMS subscribers 60 minutes before scheduled maintenance begins.

## Why this can grow

A lot of maintenance backlash is not about the maintenance itself. It comes from making customers discover it in the middle of their own work. Statuspage's maintenance flow is useful because it lets teams announce the window in advance, notify subscribers right away, and then send a reminder to email and SMS subscribers 60 minutes before the maintenance starts. That gives customers time to move a launch, warn their own team, or postpone a risky task. The page stops acting like a post-fact explanation and starts acting like operational courtesy.

## 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 scheduled maintenance reminder before the window opens 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

Atlassian Statuspage says scheduled maintenance is added to the public page, can notify subscribers immediately, and sends a reminder to email and SMS subscribers 60 minutes before the maintenance starts.

## Adjacent tactics in the same lane

- [Dedicated status domain before first incident](/growth-ideas/dedicated-status-domain-before-first-incident/) - 3 shared channels, 2 shared stages
- [Component-level status subscriptions before broad blasts](/growth-ideas/component-level-status-subscriptions-before-broad-blasts/) - 2 shared channels, 2 shared stages
- [Public postmortem linked from resolved incident](/growth-ideas/public-postmortem-linked-from-resolved-incident/) - 2 shared channels, 1 shared stage
- [Customer-ready completion triggered by release production](/growth-ideas/customer-ready-completion-triggered-by-release-production/) - 2 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 who is affected before support opens](/blog/the-status-page-should-answer-who-is-affected-before-support-opens/) - brand trust, support-led growth, operations

## Advisory

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