Post Status Updates and Communications

Before you start

• Decide whether you are updating internal responders only or publishing outward as well.
• Know the current incident status and severity before you change them.

Do this

1. In Status Flow, set the incident status to the current stage such as investigating, mitigated, or resolved.
2. Update severity if the impact has changed.
3. Use the timeline composer for operator-facing notes, decision points, and next actions.
4. In Status Pages, select Post Update.
5. Write the message you want responders and stakeholders to read.
6. Publish internally only, or enable external publishing if customer-facing Statuspage targets should receive the same update.
7. If external pages are configured, choose the pages that should receive the update and publish.

Check it worked

• The incident status on the page matches the current response stage.
• The new message appears in the incident timeline or communication stream.
• If you published externally, the linked Statuspage target shows the update and attachment state you expected.

If it does not work

• If responders are confused, shorten the message and lead with current impact, action, and next update time.
• If external publishing is unavailable, check the Statuspage integration and configured target pages.
• If the wrong page is attached, detach it from Status Pages before you post the next update.

Next

• Use bridge links and alert context
• Close the incident and hand off follow-through