The SaaS Founder's Guide to Status Pages and Customer Communication

Key Facts

Direct answer: The direct answer is that SaaS customer communication during incidents has three components: a status page (where customers check your uptime), incident communication (what you say during an incident), and post-mortems (what you say after).
Component 1: The Status Page: A status page (e.g., status.myapp.com ) shows your app's uptime and incident history.
Component 2: Incident Communication: When an incident occurs, communication is as important as the fix.
Component 3: Post-Mortems: A post-mortem is a document that describes what happened, why it happened, what was done to fix it, and what will be done to prevent it from happening again.

When your SaaS goes down, customers want to know what happened, what you are doing about it, and when it will be fixed. Without a status page and a communication plan, you will receive dozens of support emails, your customers will panic, and your reputation will suffer. A status page and a communication plan are not optional — they are part of running a SaaS. This article is the founder's guide to status pages, incident communication, and post-mortems.

The direct answer is that SaaS customer communication during incidents has three components: a status page (where customers check your uptime), incident communication (what you say during an incident), and post-mortems (what you say after). Each component builds trust and reduces support burden. For more on incident response, see our article on how to handle your first SaaS deployment incident.

Component 1: The Status Page

A status page (e.g., status.myapp.com) shows your app's uptime and incident history. It serves three purposes:

Self-service. Customers can check the status page instead of emailing you, which reduces support burden during outages.
Transparency. A public status page shows you are transparent about your uptime, which builds trust.
History. The incident history shows your track record, which helps potential customers evaluate your reliability.

How to set up a status page

Use a hosted status page service. Services like Uptime Robot (free), Better Stack (free tier), or Statuspage (paid) provide hosted status pages with uptime monitoring, incident management, and subscriber notifications. You do not need to build your own.

Point it to your health check. The status page should monitor https://myapp.com/health (not just the homepage), so it checks the app's health, not just whether the server responds.

Set up subscriber notifications. Allow customers to subscribe to status updates (via email or Slack), so they are notified when an incident occurs.

Link it in your app. Add a link to the status page in your app's footer and in your support emails.

Component 2: Incident Communication

When an incident occurs, communication is as important as the fix. Here is the communication timeline:

At the start of the incident (within 5 minutes)

Post an incident on the status page. Title: "Investigating [issue]." Description: "We are investigating an issue with [feature/service]. We will provide an update within 15 minutes."
Do not speculate. Do not guess the cause or the fix time. State what you know and what you are doing.
Notify subscribers. The status page service notifies subscribers automatically.

During the incident (every 15-30 minutes)

Post updates. Even if the update is "still investigating," post it. Customers want to know you are working on it.
When you identify the cause, share it. "We have identified the cause: [cause]. We are working on a fix and expect to have it resolved within [timeframe]."
When you apply a fix, share it. "We have applied a fix and are verifying it. We will confirm resolution within 5 minutes."

At the end of the incident

Post a resolution. "The issue has been resolved. [Brief description of what happened and what was fixed]. We will post a detailed post-mortem within 48 hours."
Notify subscribers. The status page service notifies subscribers automatically.

Communication templates

Investigating:

"We are investigating an issue affecting [feature/service]. Some users may experience [symptom]. We will provide an update within 15 minutes."

Identified:

"We have identified the cause of the issue: [cause]. We are working on a fix and expect to have it resolved within [timeframe]."

Monitoring:

"We have applied a fix and are monitoring the situation. We will confirm resolution within 5 minutes."

Resolved:

"The issue has been resolved. [Brief description]. We apologize for the inconvenience and will post a detailed post-mortem within 48 hours."

Component 3: Post-Mortems

A post-mortem is a document that describes what happened, why it happened, what was done to fix it, and what will be done to prevent it from happening again. Post-mortems are essential for learning from incidents and building trust with customers.

Post-mortem template

## Incident: [Title]

**Date:** [Date]
**Duration:** [Duration]
**Impact:** [Number of users affected, features affected]

### What happened
[Brief description of what the customer experienced]

### Root cause
[Technical description of what caused the incident]

### Timeline
- [Time]: Issue detected
- [Time]: Investigation started
- [Time]: Root cause identified
- [Time]: Fix applied
- [Time]: Issue resolved

### Resolution
[What was done to fix the issue]

### Prevention
[What will be done to prevent the issue from happening again]

### Lessons learned
[What was learned from the incident]

Where to publish post-mortems

On your status page. Most status page services support post-mortem posts.
On your blog. For significant incidents, publish the post-mortem on your blog for wider visibility.
Internally. Share the post-mortem with your team to ensure everyone learns from the incident.

Common Pitfalls and Troubleshooting

The first pitfall is not having a status page. Without a status page, customers email you during outages, which increases your support burden and makes you look unprofessional. The fix is to set up a status page before you need it.

The second pitfall is not communicating during the incident. Silence breeds panic. The fix is to post updates every 15-30 minutes, even if the update is "still investigating."

The third pitfall is speculating about the cause or the fix time. If you guess wrong, you lose credibility. The fix is to state only what you know and what you are doing.

The fourth pitfall is not publishing a post-mortem. Without a post-mortem, you do not learn from the incident, and customers do not see your commitment to improvement. The fix is to publish a post-mortem within 48 hours of every incident.

The fifth pitfall is blaming individuals. Post-mortems should focus on the system (not the person), because most incidents are caused by system failures (not individual mistakes). The fix is to use "what" language (not "who" language) in post-mortems.

Conclusion: Communication Builds Trust

When your SaaS goes down, how you communicate is as important as how you fix it. By setting up a status page, communicating transparently during incidents, and publishing post-mortems after, you build trust with your customers and reduce the business impact of outages. Customers do not expect perfection — they expect transparency.

Ready to set up your status page? Create a status page using Uptime Robot or Better Stack, link it in your app's footer, and draft your incident communication templates. For more, see how to handle your first SaaS deployment incident and monitoring your SaaS without hiring a DevOps engineer. Explore our free developer tools to speed up your workflow.