Skip to content

Open-source status page, incident response and uptime monitoring

chore: new use-case pages (#1999)

Maximilian Kaske4bc924933935
diff --git a/apps/web/src/app/(landing)/use-case/page.tsx b/apps/web/src/app/(landing)/use-case/page.tsx
index d1bff7b29..38724f714 100644
--- a/apps/web/src/app/(landing)/use-case/page.tsx
+++ b/apps/web/src/app/(landing)/use-case/page.tsx
@@ -6,7 +6,7 @@ import { ContentList } from "../content-list";
const TITLE = "Use Cases";
const DESCRIPTION =
- "Discover how teams use OpenStatus for compliance, open-source projects, crypto exchanges, and API infrastructure.";
+ "Discover how teams use OpenStatus for compliance, reducing support tickets, closing enterprise deals, open-source projects, crypto exchanges, and API infrastructure.";
export const metadata: Metadata = {
...defaultMetadata,
diff --git a/apps/web/src/content/pages/use-case/enterprise-sales.mdx b/apps/web/src/content/pages/use-case/enterprise-sales.mdx
new file mode 100644
index 000000000..49e1a9067
--- /dev/null
+++ b/apps/web/src/content/pages/use-case/enterprise-sales.mdx
@@ -0,0 +1,63 @@
+---
+title: "Status Pages for Enterprise Sales"
+publishedAt: "2026-03-22"
+author: "openstatus"
+description: "Enterprise prospects expect a status page. When their security team sends a vendor questionnaire, a branded status page with uptime history and incident communication turns a blocker into a checkbox."
+category: "Sales"
+faq:
+ - question: "Do enterprise customers require a status page?"
+ answer: "Increasingly, yes. Enterprise security and procurement teams evaluate vendor reliability as part of their due diligence. A public status page with uptime history, incident reports, and subscriber notifications demonstrates operational maturity. Many vendor questionnaires explicitly ask for a status page URL."
+ - question: "What do security questionnaires ask about incident communication?"
+ answer: "Common questions include: How do you communicate incidents to customers? Do you have a public status page? How are customers notified of outages? What is your incident response process? A status page with subscriber notifications and timestamped incident history answers all of these."
+ - question: "Can I create a private status page for enterprise clients?"
+ answer: "Yes. Use password protection to create private status pages for specific enterprise customers. Show them only the components and services relevant to their account. This gives them dedicated visibility without exposing your full infrastructure."
+ - question: "Can I host my status page on a custom domain?"
+ answer: "Yes. Host your status page on your own domain (e.g., status.yourcompany.com) to maintain brand consistency. Enterprise buyers expect a professional, branded experience — not a third-party subdomain."
+---
+
+## Page three of the vendor questionnaire
+
+You're in the final stages of an enterprise deal. Their security team sends a vendor questionnaire. Somewhere on page three: **"Do you have a public status page? Provide the URL."**
+
+If your answer is "no" or a blank field, you just added friction to a deal that was nearly closed.
+
+## Enterprise buyers are buying transparency
+
+Enterprise customers don't just buy your product — they buy **your reliability story**. They need to prove to their own stakeholders that every vendor they depend on is transparent about uptime, incidents, and maintenance.
+
+A status page tells them three things:
+- **You monitor your own systems** — reliability isn't an afterthought
+- **You communicate proactively** — outages aren't swept under the rug
+- **You have a process** — incidents are detected, communicated, and resolved systematically
+
+Without one, they're taking your word for it. With one, they have proof.
+
+## What closes the deal
+
+### Verified uptime history
+
+Your status page shows **real uptime data** powered by synthetic monitoring from **28 global regions**. Not a self-reported "100% uptime" claim — actual, verifiable numbers. Procurement teams trust data, not promises.
+
+### Incident track record
+
+Every **status report** is timestamped and permanent. Buyers can see how you've handled past incidents — how fast you detected them, how you communicated, and how you resolved them. Your incident history becomes your strongest reference.
+
+### Branded custom domain
+
+Host on `status.yourcompany.com`. A custom domain signals your status page is a first-class part of your product, not a checkbox you filled in last week.
+
+### Dedicated client pages
+
+Create **password-protected status pages** for enterprise clients. Show only the components relevant to their account. Your largest customers get dedicated visibility — and feel like a priority.
+
+### Proactive subscriber notifications
+
+Enterprise clients **subscribe via email** and get updates the moment something changes. No checking, no guessing, no "why didn't you tell us?" conversations.
+
+---
+
+Make your status page the easiest checkbox in the vendor review
+
+<ButtonLink href="https://app.openstatus.dev">Create Your Status Page</ButtonLink>
+
+---
diff --git a/apps/web/src/content/pages/use-case/reduce-support-tickets.mdx b/apps/web/src/content/pages/use-case/reduce-support-tickets.mdx
new file mode 100644
index 000000000..912f70d1f
--- /dev/null
+++ b/apps/web/src/content/pages/use-case/reduce-support-tickets.mdx
@@ -0,0 +1,58 @@
+---
+title: "Status Pages for Reducing Support Tickets"
+publishedAt: "2026-03-22"
+author: "openstatus"
+description: "Every minute of downtime floods your inbox. A status page deflects support tickets by giving users a single source of truth — with real-time incident updates and subscriber notifications."
+category: "Operations"
+faq:
+ - question: "How does a status page reduce support tickets?"
+ answer: "When users can't reach your service, their first instinct is to contact support. A status page gives them an immediate answer — what's down, what's affected, and when it'll be fixed. Instead of filing a ticket, they check the status page, see the issue is acknowledged, and wait for updates."
+ - question: "What should I put on my status page during an outage?"
+ answer: "Post a status report as soon as you detect the issue. Include what's affected, the current severity, and your next update time. Update regularly — even if there's no progress, a 'still investigating' update is better than silence. Resolve the report when the issue is fixed."
+ - question: "Can I notify users automatically when there's an incident?"
+ answer: "Yes. Users can subscribe to your status page via email, RSS/Atom, or JSON feeds. When you publish or update a status report, subscribers are notified automatically. You can also scope notifications to specific components so users only hear about services they care about."
+ - question: "How do I embed status information in my app?"
+ answer: "Use the JSON feed to pull your status page data into your own application or support portal. Many teams add a status banner or badge to their app so users see service health without leaving the product."
+---
+
+## "Is it down?" — the ticket you get 200 times during an outage
+
+When your service goes down, users don't wait. They open tickets, send emails, ping your chat support, and post on social media — all asking the same question: **"Is it down?"**
+
+Your support team spends the entire incident answering that question instead of helping resolve the issue. Meanwhile, users who don't contact support assume the worst.
+
+## Give every user one place to check
+
+A public status page answers "is it down?" before anyone asks. Users check your status page, see the incident is acknowledged, and wait for updates — instead of flooding your inbox.
+
+Fewer tickets during outages. Less pressure on your support team. Users who trust you're handling it.
+
+## What makes ticket deflection work
+
+### Detect before users report
+
+Connect **synthetic monitors** to your status page components. When a monitor catches an issue, you know before your users do. Monitor from **28 global regions** to catch regional problems early — before a wave of tickets tells you something is wrong.
+
+### Timestamped status reports
+
+Publish a **status report** the moment you detect an issue. Add updates as you investigate, identify the cause, and resolve it. Every update is timestamped — users see progress without asking.
+
+### Proactive subscriber notifications
+
+Let users **subscribe via email, RSS, or JSON feeds** so they hear from you first. Proactive communication is the difference between "they're on it" and "do they even know?"
+
+### Component-level granularity
+
+Break your status page into **components** — API, dashboard, billing, webhooks. When only one service is affected, users of other services see everything else is operational. No unnecessary tickets from users whose workflows aren't impacted.
+
+### Scheduled maintenance announcements
+
+Announce maintenance windows in advance. Subscribers are notified before the work begins — so the tickets that would have come in during the window never get created.
+
+---
+
+Stop answering "is it down?" during every outage
+
+<ButtonLink href="https://app.openstatus.dev">Create Your Status Page</ButtonLink>
+
+---