Status Page
Route: /org/resolve/settings?tab=status_page · Permission: Manage Helpdesk Settings
1. What it is
A public page stating whether your services are up. During an incident it is the cheapest support you will ever provide: one update read by everyone affected, instead of fifty tickets asking the same question.
2. How it spreads
3. Why it exists
| Without a status page | With one |
|---|---|
| Fifty tickets saying "is it down?" | One banner, read by everyone |
| Agents retyping the same update | A single source customers refresh |
| Silence reads as nobody noticed | Silence reads as acknowledged |
Publish before the queue fills, not after
The value is entirely in the first ten minutes. A status update posted after the tickets have arrived saves nothing — by then everyone has already asked. Make publishing part of the incident declaration, not part of the post-mortem.
4. Don't confuse this with…
| These two | Differ by |
|---|---|
| Status page vs ticket status | Public service health vs one ticket's workflow position |
| Status page vs Executive Telemetry | Outward-facing vs internal KPIs |
| Status page vs customer portal | A health banner vs the whole support site |
5. Troubleshooting
| Symptom | Cause |
|---|---|
| Page not reachable publicly | Not enabled, or the portal page is not wired |
| Customers still ask "is it down?" | It was not updated at declaration time |