List customer-facing components
Name services users understand: API, Dashboard, Auth, Billing, Integrations. Avoid internal microservice names on the public page.
Write incident templates now
Investigating / Identified / Monitoring / Resolved drafts save panic typing. Always include impact, workaround, and next update time.
- What is affected
- Who is impacted
- Workaround if any
- When you will update again
Offer subscriptions
Email or webhook subscribe options turn the page into proactive communication. Do not rely on customers refreshing manually.
Put status on your domain
status.yourapp.com (or a portal module) with your brand. Link it from the app footer, login errors, and support macros.
Separate status from product news
Changelogs announce ships. Status announces health. Keep both nearby in the portal so users know which feed to trust.
Ready to put this into practice?
Add status to your portal