Status Page vs. Email Support: When to Use Each
A status page answers "Is it down?" instantly. Email support handles everything else. Use both to keep users happy and your inbox sane.
When something breaks, users want to know two things: Is it down? And when will it be back? A status page answers the first question in one click. That keeps "Is it just me?" out of your inbox so you can focus on fixing the issue—and so support can handle real questions.
What a status page is for
A status page shows the current state of your systems: operational, degraded, or down. It can show per-service or per-endpoint status and sometimes a short incident message. Its job is to be the single source of truth for "are we up?" so you don't have to repeat yourself.
What email support is for
Email (or chat) is for everything else: billing, feature requests, bugs that aren't outages, and questions the status page doesn't answer. When you have a status page, support can reply with the link instead of explaining the outage again and again.
Use both
Link to your status page from your footer, docs, and support replies. When an incident happens, update the status page first; then use email or social only for big announcements if you want. Your users get instant answers, and you get a calmer inbox.