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

# Warrn assistant

> Ask Warrn about live operations and take supported actions from Slack.

The Warrn assistant answers questions using data from your Warrn organization and the Slack conversation you are in. Use it in Slack's assistant panel for a private conversation, or mention `@Warrn` in a channel or thread for a contextual response.

## Start a conversation

<Tabs>
  <Tab title="Assistant panel">
    Open **Warrn** from Slack's Apps section and start a new conversation. The panel suggests prompts for active incidents, open alerts, and current on-call coverage.

    If you open the assistant while viewing a channel, Warrn can use that channel as context when it is relevant to your question.
  </Tab>

  <Tab title="Channel or thread">
    Mention `@Warrn` followed by your question. In a thread, Warrn reads the thread before answering and keeps its reply in that thread.

    ```text theme={null}
    @Warrn summarize what we know about this outage
    ```
  </Tab>
</Tabs>

You must [link your Slack identity to Warrn](/integrations/slack#slack-oauth-recommended) before using the assistant.

## What you can ask

### Incidents

* List incidents and filter them by status or severity.
* Get details for a specific incident such as `INC-42`.
* Declare a new live incident from a request or the current thread.
* Share the current incident's postmortem in its incident channel.

```text theme={null}
@Warrn show active SEV1 and SEV2 incidents
@Warrn tell me about INC-42
@Warrn declare an incident from this thread
```

### Alerts

* List alerts by status, severity, time range, team, service, or search text.
* Get details for a specific alert.
* Find the alerts that have fired most often.
* Acknowledge or resolve an alert after you approve the action.

```text theme={null}
Show critical alerts on the payments service from the last 24 hours
Which alerts were the noisiest this week?
Acknowledge the checkout latency alert
```

### Teams, services, and on-call

* List teams and services in your Warrn organization.
* Find the person currently on call for a team.

```text theme={null}
Who is on call for Payments right now?
List our services
```

### Slack context

* Summarize the current thread or accessible channel.
* Search for a public channel by its name or topic.
* Ask to join a public channel when access is needed. Warrn requests your approval before joining.

Warrn cannot join a private channel on its own. Invite the Warrn app to the private channel first.

### War-room investigation

In an incident channel, ask about what was said, decided, or shown during a recorded war-room call. Warrn hands the question to its incident investigation agent, which can use the available transcript and screen-share recording and posts the result back to the thread.

```text theme={null}
@Warrn what root cause did the team agree on during the call?
@Warrn what query was shown on screen?
```

This requires an incident with an available war-room recording or transcript.

### Product feedback

Tell the assistant about a Warrn feature request or product issue. Warrn turns it into a concise submission and asks you to approve it before sending.

```text theme={null}
I want alert cards to show the last deployment for the affected service
```

## Declare, import, or attach

These actions sound similar but produce different results:

| Intent                       | What Warrn does                                                                                     | Example                                       |
| ---------------------------- | --------------------------------------------------------------------------------------------------- | --------------------------------------------- |
| Declare a live incident      | Starts an active incident and runs your configured response workflows                               | `@Warrn declare an incident from this thread` |
| Import a historical incident | Preserves a past Slack thread as a resolved or historical incident without starting a live response | `@Warrn import this old incident`             |
| Attach context               | Adds the current Slack thread to an existing Warrn incident                                         | `@Warrn add this to INC-42`                   |

For a live declaration, Warrn prepares a proposal with a title, summary, and suggested severity. Select **Declare**, **Edit**, or **Cancel**. Import and attach requests open a form so you can review the destination and details before anything is saved.

## Actions that require approval

Warrn pauses and shows a confirmation before it:

* Declares a live incident.
* Acknowledges or resolves an alert.
* Joins a public Slack channel.
* Submits product feedback or a feature request.

Read-only questions do not require approval.

## Current limits

The assistant does not modify team settings, escalation policies, alert rules, routing rules, or on-call schedules. Use Warrn's dashboard for those changes.

Use [slash commands](/integrations/slack/commands) to change an incident's status or severity, add responders, post status updates, and view incident-specific timelines.