> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rootly.com/llms.txt
> Use this file to discover all available pages before exploring further.

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

<Note>
  These commands are built-in and cannot be modified. To create custom commands that trigger your own workflows or forms, see [Custom Workflows](/integrations/slack/workflows/custom-workflows) and [Custom Forms](/configuration/custom-forms).
</Note>

***

## 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` | Escalate to PagerDuty, Opsgenie, or VictorOps | 🚨    |

***

## 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           | 🚨    |

<Tip>
  Alias: `/rootly action` also works for viewing action items.
</Tip>

***

## On-Call & Paging

| Command          | Description                                 | Where                  |
| ---------------- | ------------------------------------------- | ---------------------- |
| `/rootly oncall` | View on-call schedules                      | 🌐                     |
| `/rootly page`   | Page a schedule, team, or escalation policy | 🌐 (with On-Call) / 🚨 |
| `/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

<AccordionGroup>
  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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 page`

    Page responders through Rootly On-Call. Select schedules, teams, or escalation policies. Add an optional note for context.

    ### `/rootly escalate`

    Escalate the current incident to external paging providers. Requires the relevant integration to be installed.
  </Accordion>

  <Accordion title="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).
  </Accordion>
</AccordionGroup>