> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/chatops/overview.md).

# Overview

ChatOps handles alerts where your team already talks. Alerts are published into channels you already have, responders accept, reroute, and resolve them there without opening ilert, and colleagues who have no ilert account can still raise one from a channel they already use.

## What you can do

ilert integrates with **Slack**, **Microsoft Teams**, and **Google Chat**. All three support the same four things:

* [Receive and respond to alerts](#receive-and-respond-to-alerts)
* [Raise an alert from chat](#raise-an-alert-from-chat)
* [Look up who is on-call](#look-up-who-is-on-call)
* [Open a dedicated channel](#open-a-dedicated-channel), on an incident

The platforms differ only in how you invoke them: Slack and Google Chat use slash commands, Microsoft Teams uses a mention of the ilert bot.

{% hint style="info" %}
**Existing channels carry alerts. A dedicated channel belongs to an incident.**

ChatOps sends alerts into channels your team already has, and lets responders act on them there. You cannot create a channel of its own for an alert. When a problem needs one, you [declare an incident](/incidents-and-status-pages/incidents/declare-an-incident.md) and create an [incident channel](/incidents-and-status-pages/incidents/incident-channels.md) with it.
{% endhint %}

## Receive and respond to alerts

Alerts arrive in the channel as cards showing status and priority, with buttons to accept, reroute, and resolve. The card updates in place as the alert changes, so the channel reflects the current state rather than a growing pile of notifications.

* [Slack](/chatops/slack/post-alerts-to-a-slack-channel.md)
* [Microsoft Teams](/chatops/microsoft-teams/chat.md)
* [Google Chat](/chatops/google-chat/google-chat-app.md)

## Raise an alert from chat

Anyone can report a problem from a channel. Each platform offers two modes:

| Mode           | Who can raise an alert                          | Setup                                                                                                            |
| -------------- | ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| **Restricted** | Only chat users who also have an ilert account  | None beyond installing the app                                                                                   |
| **Open**       | Any user in the workspace, ilert account or not | Requires a dedicated alert source, which fixes the channels, escalation policies, and priority available to them |

The open mode is the useful one for support and sales colleagues who need to escalate but will never log in to ilert.

* [Slack](/chatops/slack/create-alerts-in-slack.md)
* [Microsoft Teams](/chatops/microsoft-teams/create-alerts-in-microsoft-teams.md)
* [Google Chat](/chatops/google-chat/create-alerts-in-google-chat.md)

## Open a dedicated channel

A channel of its own belongs to an **incident**. Declare the incident — from scratch, or from the alert that surfaced the problem — and create the channel with it. Responders are invited automatically, and the incident keeps the structured record while the channel carries the conversation.

* [Incident channels](/incidents-and-status-pages/incidents/incident-channels.md) — how to open one, on any of the three platforms

## Look up who is on-call

Check who is currently on-call for an alert source or an escalation policy without leaving the channel. Like alert creation, this can be restricted to users with an ilert account or opened to the whole workspace.

* [Slack](/chatops/slack/lookup-who-is-on-call.md)
* [Microsoft Teams](/chatops/microsoft-teams/look-up-who-is-on-call-in-microsoft-teams.md)
* [Google Chat](/chatops/google-chat/look-up-who-is-on-call-in-google-chat.md)

## Set up your platform

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Slack</strong></td><td>Authorize your workspace, then pick a use case.</td><td><a href="/pages/-M9Scygmee351oXjfG4W">/pages/-M9Scygmee351oXjfG4W</a></td></tr><tr><td><strong>Microsoft Teams</strong></td><td>Install the certified ilert bot, via the chat app or an incoming webhook.</td><td><a href="/pages/-M9Sbmv3q5SXOPdpF5M0">/pages/-M9Sbmv3q5SXOPdpF5M0</a></td></tr><tr><td><strong>Google Chat</strong></td><td>Install the Google Chat app, or use a webhook where app permissions are restricted.</td><td><a href="/pages/T1Ne8463UUF3KvV6Vlw4">/pages/T1Ne8463UUF3KvV6Vlw4</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ilert.com/chatops/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.