In the middle of an incident, paging multiple teams or services shouldn’t slow you down. Whether you’re escalating to multiple on-call schedules, teams, or services, this update enables you to page multiple responders in one go—directly from Slack or the web—from a single command or modal.
Why it matters
When things go sideways, responders need to mobilize fast. Previously, paging several teams required running /rootly page or clicking Start Paging multiple times. This release eliminates that repetitive overhead by allowing you to select multiple notification targets—Rootly automatically pages each one.
The result: faster coordination, fewer clicks, and no wasted time.
How it works
- Slack command:
- Run
/rootly pagein any Slack channel (if Rootly On-call is enabled) or in an incident channel.
- Run
- Web experience:
- The same multi-select functionality is available when paging via the Start Paging button in the web UI.
- New modal experience where you can:
- Add a short alert summary
- Select one or more teams, schedules, escalation policies, or services to page
- Include an optional escalation note for added context
- Rootly then creates an alert for each selected target, all from a single action.
.png)
Check out the docs to learn more.
New & Improved
New Features
- On-Call Admins are able to bulk-delete Alerts.
- Enabled hyperlinks in form field descriptions for improved documentation and user guidance.
- Metrics timestamps display "X days ago" for durations over 1 day.
Bug Fixes
- Resolved search result reset issue in scheduling that made it difficult to add users to rotations.
- Fixed shifts API response to include remainder of shifts after overrides rather than omitting them.
- Resolved deleted incident types still appearing in incident type selection dropdowns.
- Updated incident form field selection permissions to be controlled by incident permissions rather than custom field permissions, allowing proper access control.

.avif)



















