Publishing is deliberate, not automatic. An incident attached to a service or functionality on your status page is not published on its own — someone on the response team writes and publishes each update, so every message is reviewed before customers see it.
What Gets Published
You can publish incidents to status pages to communicate incident details, timeline updates, and resolution status with your external stakeholders such as customers, partners, or internal teams. When you publish an incident to a status page, it will display:- Incident title
- Affected Services, Functionalities & External Services
- Timeline of events
- Incident resolution status

Publishing from Slack
In addition to using the web interface for publishing incidents to status pages, you can also accomplish the same thing without leaving Slack. To publish an incident using Slack, do the following: From Slack, navigate to the Slack channel specific to that incident, and type the command: /rootly statuspage
Publishing from the Web UI
To publish an incident on a status page in Rootly’s Web UI:- On the incident’s details page, navigate to the Status Page tab.
- Click ‘Publish Incident’, and fill out the form to write your incident update.
- Use any templates provided to help craft and standardize your message.
- Once you’ve provided all the details, the incident will be published to the status page.

Updating a Published Incident
As your incident progresses, you’ll need to continually communicate progress to your customers and stakeholders via the status page. You can do so from the same tab in your incident’s detail page.- Click ‘Add to status page’ and fill out the necessary information.
- Rootly will pre-fill the title based on the previous update that was published to the status page.