> ## Documentation Index
> Fetch the complete documentation index at: https://relevanceai-tsp-1444-docs-update.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Alerts

> Set up rules to get notified when your agent encounters an issue, reaches a threshold, or gets updated.

Set up rules to get notified when your agent encounters an issue, reaches a threshold, or gets updated.

<Note>
  Alerts are available on paid plans only.
</Note>

## Alert rules

Stay on top of agent issues by creating alert rules that notify you automatically when specific events occur. Each rule has a **trigger condition** (what happened) and one or more **notification channels** (where to send it).

### Alert types

<CardGroup cols={3}>
  <Card title="Status change" icon="rotate">
    Triggers when an agent task enters one or more specific statuses you select.
  </Card>

  <Card title="Tool error" icon="wrench">
    Triggers when a tool fails during execution, optionally scoped to specific tools.
  </Card>

  <Card title="Agent published" icon="rocket">
    Triggers when the agent is published. No additional configuration needed.
  </Card>
</CardGroup>

#### Status change

Triggers when an agent task enters one or more specific statuses. Select which statuses you want to be alerted on from the multi-select dropdown.

<Accordion title="Available statuses">
  Starting up, Waiting for capacity, Pending approval, Running, Cancelled, Idle, Timed out, Escalated, Unrecoverable error, Paused, Completed, Exhausted retries, Queued for approval, and Queued for rerun.
</Accordion>

<Tip>
  A common configuration is to alert on failure states like **Timed out**, **Unrecoverable error**, and **Exhausted retries** so your team can respond quickly when something goes wrong.
</Tip>

#### Tool error

Triggers when a tool fails during execution. You can optionally scope this to specific tools — leave the selection empty to watch all tools, or pick individual tools to monitor. This is useful for critical integrations where a tool failure could block your agent's workflow.

#### Agent published

Triggers when the agent is published. No additional configuration is needed — select a notification channel and you'll be alerted whenever a new version goes live.

### Notification channels

Each alert rule can send notifications to one or more channels:

<CardGroup cols={3}>
  <Card title="Email" icon="envelope">
    Add one or more email addresses. No OAuth connection required.
  </Card>

  <Card title="Slack" icon="slack" iconType="brand">
    Connect your Slack workspace via OAuth, then select a channel.
  </Card>

  <Card title="Microsoft Teams" icon="microsoft" iconType="brand">
    Connect your Microsoft Teams account via OAuth, then select a team and channel.
  </Card>
</CardGroup>

For Slack setup details, see [Slack integration](/integrations/popular-integrations/slack). For Teams, see [Microsoft Teams integration](/integrations/popular-integrations/microsoft-teams).

<Note>
  When you remove a connected OAuth account (Slack or Teams), a confirmation dialog shows how many alert rules route notifications through that account. Review those rules before disconnecting to avoid breaking alert delivery.
</Note>

### Setting up an alert rule

1. Navigate to your agent and open the **Alerts** tab
2. Click **Create alert rule**
3. Select a trigger type from the left panel
4. Configure the trigger conditions (if applicable)
5. Preview how the notification will look
6. Add at least one notification channel
7. Click **Save**

You can create multiple alert rules, each with different triggers and channels. Existing rules appear as cards showing the trigger description, active channels, and controls to edit, delete, or toggle them on/off.

### Notification channel health

When a notification channel experiences a permanent delivery failure — such as a deleted OAuth account, a removed Slack bot, an archived channel, or a token that can no longer be renewed — Relevance AI surfaces warnings so you can identify and fix the issue before critical notifications are missed.

#### Channel issue badge

Alert rule cards display a yellow **Channel issue** badge when the rule's notification channel has a permanent delivery failure. The badge appears in both the agent and eval views, making broken channels easy to spot at a glance.

#### Warning banner when editing

When you open an alert rule with a broken channel for editing, a warning banner appears in the channel configuration step. The banner identifies which specific channel is broken and explains why delivery failed, so you know exactly what needs to be updated.

#### Fallback-to-email delivery

If all of an alert rule's configured notification channels are permanently broken, Relevance AI automatically falls back to emailing the alert rule's original creator. This ensures critical notifications are still delivered even when all configured channels fail.

***

## Agent escalations

When your agent encounters a situation it cannot handle, it can escalate the conversation to a human manager using the built-in **Escalate to Manager** tool.

This is different from alert rules — escalation is an in-conversation handoff where the agent actively routes a conversation to a human, rather than a background notification about an event.

### Enabling the escalation tool

In the **Agent escalations** section at the bottom of the Alerts page, click **Enable escalation tool**. This adds the "Escalate to Manager" tool to your agent's available tools.

Once enabled, you can reference the tool in your agent's prompt using the **/** command to give the agent guidance on when to escalate. Click **Edit prompt** to go directly to the prompt editor.

### When to use escalation

<CardGroup cols={2}>
  <Card title="Complex technical support" icon="headset">
    Issues requiring specialized knowledge beyond the agent's training.
  </Card>

  <Card title="Sensitive situations" icon="hand-holding-heart">
    Customer service scenarios that need human empathy and judgment.
  </Card>

  <Card title="Product feedback" icon="comment">
    Detailed feedback that should reach product managers directly.
  </Card>

  <Card title="High-value sales" icon="handshake">
    Opportunities requiring personalized human attention.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.