Incident comms that build trust

During an incident, silence feels like denial. Clear severity, honest impact, and timely updates turn a bad hour into a retained customer.

• Publish component-level status early
• Use plain language for impact — not internal ticket IDs
• Update on a cadence even when the fix is still in progress
• Close with a short postmortem customers can actually read

Start at Status for live signals, and Support when you need a human during an active event.