startups
incident-response-microsoft-teams
home
jsm-jira-vs-rootly-full-comparison
pagerduty-vs-rootly-on-call
opsgenie-vs-rootly-on-call
humans-of-reliability
retrospectives
integrations
incident-response-slack
on-call
blog
ai-sre
pricing
customers
Rootly On-call Health
Your on-call team Is burning out: here's how to see it coming
New updates and improvements to Rootly.
Our new User Lookup feature allows you configure workflows to auto-invite Jira Reporters and PagerDuty users to your incident Slack channel.
We’ve just added another touch of configurability by allowing you to upload your own banner image in the Incident Overview pop-up in Slack.
When an incident is resolved, Rootly automatically generates a Confluence page with all of the incident’s key information populated in a clean, easy-to-read template. We just gave our templates a refresh so they’re even easier on the eyes.
We’re adding another degree of control to workflows that post to Slack by allowing you to choose whether you want workflows to post a new Slack message or update a previous one.
We've made an exciting upgrade to our Statuspage.io integration: customers using Statuspage.io can now use Rootly to automatically update component statuses!