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

# Rootly AI in Slack

> Rootly AI works inside your incident channels — catch up on incidents, look up information in real-time, and take actions without leaving Slack.

<Note>
  Rootly AI in Slack is available on request — contact [support@rootly.com](mailto:support@rootly.com) to enable it for your organization. Once enabled, Rootly AI responds in any incident channel, the Slack AI assistant pane, or a direct DM. If you've tried `@Rootly` and haven't gotten a reply, the feature likely isn't enabled yet for your team.
</Note>

## Responding to Incidents in Slack

Rootly AI in Slack brings the parts of Rootly you reach for during an incident directly into where your team already operates. You can use Rootly AI in any incident channel, the Slack AI assistant pane, or a direct DM.

**Ask Rootly AI to:**

* "This is now a SEV1. Update the incident severity."
* "Draft comms to our high-value customers, letting them know the impact of the incident on their product experience."
* "Page the security team, and convert this to a private incident."

## How Rootly AI in Slack Works

The hardest part of running an incident isn't just mitigating and resolving it — it's also keeping teams and stakeholders up to date so they can quickly support you. Responders join late, miss key learnings, and take time to catch up. Comms leads need to draft customer updates while still triaging. Commanders need to pull in the right stakeholders. Leadership needs to be aware of major updates. Everyone needs context without adding distractions on other teammates.

Rootly AI in Slack collapses that context into a single conversational surface, right in the channel where the incident is being run. Rootly AI reads from your Rootly data, channel messages, and bridge call transcripts (when available) to take actions on your behalf.

To start, type `@Rootly` in Slack and ask your question. Rootly AI uses the incident's live context to decide how to respond, and replies in-thread to keep you aware of any actions taken.

[Learn more about using Rootly AI in Slack](/ai/rootly-in-slack/using-rootly-in-slack)

<Warning>
  Rootly AI can only take actions that you as a user have permission to perform. Check your Rootly role to confirm what your permissions are.
</Warning>

## Key Capabilities at a Glance

| Capability             | Description                                                                                               | Example question                                                                                          |
| :--------------------- | :-------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------- |
| Catch me up            | Structured brief of an incident's state, key events, current responders, and open action items            | @Rootly what's going on right now?                                                                        |
| Who's on call          | Look up current and historical on-call across teams, services, schedules, and escalation policies         | @Rootly who's on call for the Security team?                                                              |
| Page responders        | Page a team, user, escalation policy, service, or Slack user group via Rootly On-Call                     | @Rootly page the Search Experience team.                                                                  |
| Update an incident     | Change severity, status, title, services, custom fields, or roles — with Rootly AI confirming what it did | @Rootly add the Prod DB Team to the incident and bump up the severity to a SEV2.                          |
| Manage action items    | Create, update, list, or delete action items from natural-language requests                               | @Rootly create an action item for all of the next steps we discussed on the bridge.                       |
| Find similar incidents | Similarity search across past incidents, scoped to your tenant                                            | @Rootly I remember a similar incident happened last week that impacted this service. Summarize it for me. |
| Draft customer updates | Generate Slack-ready or status-page-ready update copy from the current incident state                     | @Rootly write a draft to send to the leadership team and our partners.                                    |

## How Permissions Work

Rootly AI uses each user's existing Rootly permissions. If a user can't see a private incident in the web app, Rootly AI won't surface it for them in Slack. If a role doesn't allow paging, Rootly AI declines to page when that user asks.

<Info>
  Permissions are managed in **Configuration → Roles & Permissions** in the Rootly web app. Rootly AI respects whatever role assignments are already in place — there's no separate AI permission system.
</Info>

## Where to Go Next

These pages cover using and configuring Rootly AI in Slack, plus how Rootly AI handles your data:

* **[Getting Started](/ai/rootly-in-slack/getting-started):** Enable Rootly AI for your workspace and walk through your first interaction
* **[Using Rootly AI in Slack](/ai/rootly-in-slack/using-rootly-in-slack):** Hands-on guide to the three surfaces, suggested prompts, and how Rootly AI communicates
* **[What To Use Rootly AI For](/ai/rootly-in-slack/what-to-use-rootly-for):** What Rootly AI in Slack can do to help responders during an ongoing incident, with concrete examples of how to ask
* **[Data Privacy for Rootly AI](/ai/data-privacy-for-rootly-ai):** Security, privacy, RBAC, audit, and reliability answers for security review
* **[Troubleshooting](/ai/rootly-in-slack/troubleshooting):** Common symptoms and how to resolve them

***

## FAQs

<Accordion title="What does it take to turn on Rootly AI?" icon="toggle-on">
  A Rootly admin enables it in **Configuration → Rootly AI** by toggling **Enable Rootly AI in Slack** on. A Slack workspace admin then needs to reconnect the Slack integration for the update to take effect.
</Accordion>

<Accordion title="Where can I use Rootly AI?" icon="sparkles">
  Rootly AI works best inside an incident channel, where it has full access to incident data. You can also use Rootly AI via Slack's AI assistant pane pointed at an incident channel, or by messaging it directly in Slack. For those two surfaces, Rootly AI can only read information, not take actions.
</Accordion>

<Accordion title="Does Rootly AI respect our roles and permissions?" icon="lock">
  Yes. Rootly AI uses the requesting user's existing Rootly permissions for every action. It cannot do anything in Slack that the user couldn't already do in the Rootly web app.
</Accordion>

<Accordion title="What about private incidents and private channels?" icon="eye-slash">
  Rootly AI has to be invited to a channel before it sees anything there and can take actions. User permission still applies: a user who can't see a private incident in the web app can't ask Rootly AI about it from any surface.
</Accordion>

<Accordion title="Can Rootly AI page using vendors outside of Rootly On-Call?" icon="bell">
  Paging happens through Rootly On-Call only. If you have a third-party paging integration configured elsewhere in Rootly, Rootly AI will not fall back to it.
</Accordion>

<Accordion title="What models does Rootly AI use?" icon="circle-info">
  Claude Sonnet 4.6 from Anthropic by default, with automatic failover to GPT-5 from OpenAI. Both providers are accessed through a managed gateway.
</Accordion>