Commands

Quick reference for all Rootly Slack commands, including incident creation, status updates, on-call paging, action items, timeline events, and roles.

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

Icon	Meaning
🌐	Works in any Slack channel
🚨	Requires incident channel

---

Getting Started

Command	Description	Where
/rootly connect	Link your Slack account to Rootly	🌐
/rootly help	View available commands and descriptions	🌐
/rootly support	Report an issue to Rootly	🌐

---

Create & View Incidents

Command	Description	Where
/rootly new	Declare a new incident and create a channel	🌐
/rootly test	Create a test incident (not publicly announced)	🌐
/rootly maintenance	Schedule a maintenance window	🌐
/rootly list	View up to 10 active incidents	🌐
/rootly overview	Open incident control center	🚨
/rootly catchup	Get AI-powered incident summary	🚨

---

Update Incidents

Command	Description	Where
/rootly update	Edit incident fields (severity, type, etc.)	🚨
/rootly summary	Add or edit incident summary	🚨
/rootly timeline	Add an event to the incident timeline	🚨
/rootly timestamps	Edit status change timestamps	🚨
/rootly convert	Convert current channel to incident channel	🌐 (non-incident)

---

Incident Status

Command	Description	Where
/rootly status	Change incident status	🚨
/rootly mitigate	Mark incident as mitigated	🚨
/rootly resolve	Mark incident as resolved	🚨

---

Teams & Services

Command	Description	Where
/rootly add team	Attach a team to the incident	🚨
/rootly add service	Tag impacted services	🚨
/rootly add functionality	Tag impacted functionalities	🚨
/rootly add alert	Associate an alert with the incident	🚨

---

Roles & Assignments

Command	Description	Where
/rootly assign	Assign, add, or remove incident roles	🚨
/rootly escalate | /rootly call | /rootly page	Open the paging dialog. In an incident channel this attaches the page to the incident and routes through any configured external provider (PagerDuty, Opsgenie, VictorOps); outside an incident channel it opens the manual Rootly On-Call paging dialog. All three words are aliases for the same command.	🌐 / 🚨

---

Action Items

Command	Description	Where
/rootly task	Create a task (to complete during incident)	🚨
/rootly followup	Create a follow-up (post-incident action)	🚨
/rootly add action item	Create a task or follow-up	🚨
/rootly action items	View action items assigned to you	🚨

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

---

On-Call & Paging

Command	Description	Where
/rootly oncall	View on-call schedules	🌐
/rootly page | /rootly escalate | /rootly call	Alias for the paging dialog (see Roles & Assignments for full behavior).	🌐 / 🚨
/rootly alerts	View all alerts	🌐

---

Advanced

Command	Description	Where
/rootly manage fields	Set values for custom incident fields	🚨
/rootly integrations	Manage links to integrated tools (Jira, PagerDuty, etc.)	🚨
/rootly statuspage	Publish an update to a status page	🚨
/rootly feedback	Log feedback about the incident response	🚨
/rootly duplicate	Mark incident as duplicate of another	🚨
/rootly sub	Create a sub-incident	🚨 (parent)
/rootly workflows	Manually trigger a workflow	🚨

---

Command Details

Creating Incidents

/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.

Managing Status

/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.

Action Items

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.

On-Call Commands

/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.

Channel Conversion

/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).