Skip to main content

Where to Interact With Rootly AI

Rootly AI works the same way in every supported chat tool. Mention @Rootly in an incident channel to run the incident where the whole team can see it, or ask outside the incident channel for questions and on-call lookups. Changes to an existing incident happen only in that incident’s channel. Where you open Rootly AI depends on your platform:

In Slack

Incident channels, the Slack assistant pane, and DMs.

In Microsoft Teams

Incident channels, team channels, and chats.
Every surface requires an Incident Response role.
Ask questions in the incident channel when the context might be relevant to other teammates, so they can also benefit from the reply.

Interacting With Rootly AI

While Rootly AI works, a status indicator shows what it’s doing, for example “Checking who’s on call”. Replies include the answer and a confirmation of any action taken.

Giving Feedback

In Slack, rate replies with 👍 / 👎. Feedback flows into Rootly’s evaluation pipeline and does not directly fine-tune the model.

Providing Clarifications

If something is ambiguous or required data is missing, Rootly AI asks rather than guesses.
Rootly AI in Slack asking "Which Andre would you like to page?" with a button for each matching user and an expiry notice

Using Clarification Cards

Based on how much input Rootly AI needs, you’ll be able to reply via: Cards expire after 60 minutes. Re-ask your question to get a fresh card.

Taking Action With Rootly AI

Ask for an action and Rootly AI runs it, confirming what it did in its reply. When an action is destructive, or Rootly AI wants your sign-off first, it posts the change as a card with a Confirm button and runs only after you approve.
Rootly AI in Slack proposing an Update incident roles action after being asked "can you make me commander?", with a Confirm button before anything runs
If anything fails, Rootly AI tells you why in the same thread. Every Rootly-native action is capped at your Rootly permissions and attributed to you in the audit trail. Rootly AI cannot perform a Rootly action you couldn’t perform yourself in the Rootly web app. An AI connector can use a provider account shared by the team for both reads and actions. The AI connector’s Rootly permission checks determine who may use each tool, and the connected provider account determines which provider data and operations are available. For example, every Slack AI user can use Devin’s repository tools and supported read-only platform actions against data available to the service user, while actions that change Devin resources additionally require permission to manage AI connectors. Private Agent is an Early Preview for approved customers. If it and AI SRE are enabled for the selected team, Rootly AI can also call capabilities inside your network. The tool is offered and checked against your Rootly role, and the agent enforces its local policy. Owners and admins can use registered safe-read, sensitive-read, and write tiers; users can use safe reads. See the Private Agent security model before enabling a capability.

Worked Example: Paging an On-Call Team

This shows the clarification flow in action:
  • Type @Rootly page the team in the incident channel.
  • Rootly AI searches your Rootly catalog for the team to page.
  • If multiple teams match, Rootly AI posts a clarification card: "Which team do you want to page?" with a dropdown. You pick one and click Confirm.
    A clarification card in Slack asking "Which team do you want to page?" with a dropdown listing the workspace's teams
  • Rootly AI pages via Rootly On-Call to the team’s current on-call, using their configured notification preferences. Rootly AI replies: "Page request submitted to Rootly On-Call for the Rootly team." The audit trail attributes the page to you, not to Rootly AI.
  • If you don’t have permission to page in Rootly, Rootly AI tells you so and stops.

AI Agent in Communication Channels

What Rootly AI is and everything it can do.

What to Use Rootly AI For

The full catalog of prompts, grouped by use case.

Troubleshooting

Common symptoms and how to resolve them.