Status Page Template: What to Say When You Don't Know What's Broken Yet
The first message on a status page is never the diagnosis — you don't have one yet. It's the promise that you've seen it and someone is on it. Teams freeze here, hold the update until they "know more," and the customers who noticed first write the story for them on social media. This page is the fix: a status page template you can fill in ten minutes into an outage, before you understand it.
Why waiting for the diagnosis fails
Silence doesn't read as "careful engineering." It reads as "either they don't know or they're hiding it." Meanwhile every customer with a broken checkout is doing their own troubleshooting and drawing their own conclusion. A two-line acknowledgement in minute ten costs nothing and buys you the hour you need to actually find the cause.
The first post — three sentences, minute ten
Paste this, fill the brackets, publish:
[Service] is currently degraded. We identified the issue at [HH:MM] [timezone] and a
member of the team is actively working on it. Next update by [HH:MM] even if the situation
hasn't changed.
The last sentence is the one most teams skip, and it's the most important: a named next-update time converts silence into schedule. If you miss the time you set, that becomes the story — so set the first one conservatively and beat it.
The update cadence that holds trust
- Every hour on the clock, changed or not. "Still investigating; no change since the 14:00 update" is a legitimate post. A predictable cadence means customers stop refreshing and start trusting.
- Only one place, append-only. Updates stack on the same incident page; nobody reconstructs events from scattered tweets.
- Say what you've ruled out. "Not a payment-processor outage" is real information that halves your support ticket volume.
- Resolve is a post, not a shrug. What was wrong, what fixed it, what time it fully recovered — and the sentence that starts the postmortem instead of the arguments.
The wording that keeps customers calm
- Plain verbs. "We're investigating checkout failures" — not "experiencing a degradation event in the transaction pipeline."
- No blame, no jargon, no "third-party provider issues" until you've confirmed them.
- Give the workaround its own line. "Orders can still be placed by phone" saves more carts than any apology.
- Never promise a fix time you don't control. Promise the next update, which you fully control.
The 20-minute version
Pre-write the first post now — with brackets — and store it next to your incident channel template. The team that publishes a placeholder in minute ten always looks calmer than the team still drafting prose at minute forty, even if they resolve at the same minute.
Pre-written versions of every message on this page — first post, hourly updates, the workaround line, and the resolution post — are in our comms pack: Ops Starter Kit ($14). The advanced volume adds the full major-incident comms flow (stakeholder updates, exec briefs, post-incident customer note): Ops Starter Kit Vol. 2 ($27).