Skip to main content
Rootly provides slash commands to manage incidents directly from Slack. All commands work with both /rootly and /incident prefixes.
These commands are built-in and cannot be modified. To create custom commands that trigger your own workflows or forms, see Custom Workflows and Custom Forms.

​
Quick Reference

​
Getting Started

​
Create & View Incidents

​
Update Incidents

​
Incident Status

​
Teams & Services

​
Roles & Assignments

​
Action Items

Alias: /rootly action also works for viewing action items.

​
On-Call & Paging

​
Advanced

​
Command Details

​
/rootly new

Opens the incident creation form. Fill in title, summary, severity, and type. Rootly will:
  • Create a dedicated Slack channel
  • Post the initial incident message
  • Trigger configured workflows

​
/rootly test

Same as /rootly new, but the incident is marked as a test and won’t be publicly announced. Use for training and workflow testing.

​
/rootly maintenance

Schedule planned maintenance. Maintenance incidents appear in the Rootly web UI and can be published to status pages.

​
/rootly status

Opens a modal to change the incident status (In Triage → Active → Mitigated → Resolved → Closed).

​
/rootly mitigate

Quick action to mark the incident as mitigated. You’ll be prompted to add a comment explaining the mitigation.

​
/rootly resolve

Quick action to mark the incident as resolved. You’ll be prompted to add a resolution comment.
Tasks are actions to complete during the incident (e.g., “Restart the database”).Follow-ups are post-incident actions (e.g., “Add monitoring for this failure mode”).Use /rootly action items to see a checklist of items assigned to you for this incident.

​
/rootly oncall

View who’s currently on-call for any schedule. Works with Rootly On-Call and integrated providers (PagerDuty, Opsgenie, VictorOps).

​
/rootly escalate · /rootly call · /rootly page

These three words are aliases for the same command — pick whichever your team prefers. The dialog that opens depends on where you invoke the command:
  • Inside an incident Slack channel — the escalation dialog opens with the current incident’s context. If your team has an external paging integration (PagerDuty, Opsgenie, VictorOps, PagerTree), the dialog routes the page through that provider; otherwise it uses Rootly On-Call.
  • In any other channel — the manual page dialog opens for ad-hoc paging (Rootly On-Call schedules, teams, services, functionalities, or escalation policies).
You can prefill target users by @-mentioning them after the command: /rootly page @alice @bob. Non-mention trailing text is ignored.If a team admin has enabled a custom Slack paging workflow (Team Settings), the alias set is disabled and these commands won’t respond.

​
/rootly convert

Convert an existing Slack channel into a Rootly incident channel. Use this when an incident discussion is already happening in a channel before it’s formally declared.Run this command in the channel you want to convert (not an existing incident channel).