Skip to main content

​
Overview

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.”
  • “Catch me up. What’s still open, and who owns it?”
Rootly AI in Slack brings the parts of Rootly you reach for during an incident into the channel where your team already operates.
Rootly AI in Slack answering "has anything changed on checkout-api?" with a deploy and a feature-flag change pulled from a connected source, including the rollback command
Answers like this one draw on your own tools through Connectors: plug in your observability, code, and docs sources and Rootly AI investigates with them. Private Agent is an Early Preview for approved customers. When both Private Agent and AI SRE are enabled for the selected team, it lets Rootly AI reach services inside your network. Its capabilities follow your Rootly role and the agent’s local policy, with a separate access boundary from SaaS connectors.
Setup takes one toggle and a Slack reconnect. See Getting Started.

​
How Rootly AI in Slack Works

Rootly AI reads from your Rootly data and the channel conversation, including bridge call transcripts when available, to answer questions and take actions on your behalf. Type @Rootly and ask. It uses the incident’s live context to decide how to respond, and replies in-thread so the channel sees any action taken. Rootly AI also answers in the Slack assistant pane and in DMs. Those surfaces cannot change Rootly records, but a connector can expose separately governed external actions. See Using Rootly AI in Slack for the full guide. Model details, including failover behavior, are documented in Data Privacy for Rootly AI.

​
Key Capabilities at a Glance

This table is a sample. The full prompt catalog lives in What to Use Rootly AI For.

​
Who Can Use Rootly AI in Slack

Rootly AI in Slack requires an Incident Response role. Without one, Rootly AI asks you to contact your admin, and requests to page or check who is on call are refused.

​
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. Connector data and actions can add a separate access boundary. A connector guide identifies which users can use its tools and the provider account that scopes the available data and operations. For example, Devin repository reads use the connected service user’s repository access, including for Slack AI users who cannot manage the connector.
Permissions are managed in Configuration → Roles & Permissions. There is no separate AI permission system.

​
Frequently Asked Questions

Rootly AI has to be invited to a channel before it sees anything there or takes action. User permissions still apply on top.
Rootly AI’s native paging action uses Rootly On-Call only and does not fall back to third-party paging integrations configured elsewhere in Rootly. A connector with an explicitly supported paging tool can define a separate permission boundary; see that connector’s guide.

Getting Started

Turn on Rootly AI in Slack and walk through your first interaction.

Using @Rootly

Where to invoke Rootly AI, how clarification cards work, and how actions run.

What to Use Rootly AI For

The full catalog of prompts, grouped by use case.

Troubleshooting

Common symptoms and how to resolve them.