> 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/incidents-and-status-pages/incidents/incident-channels.md).

# Incident channels

Connect a Slack, Microsoft Teams, or Google Chat channel to an incident in ilert for real-time coordination.

An incident channel is a dedicated chat channel connected to an [incident](/incidents-and-status-pages/incidents.md) for real-time coordination. It gives your responders one place to talk through the response while the incident keeps the structured record.

For a live call rather than a written conversation, attach a [conference bridge](/incidents-and-status-pages/incidents/conference-bridges.md)—an incident can have both.

## Before you start

Incident channels rely on a connected chat integration. Make sure one of the following is set up for your account:

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

See the [ChatOps overview](/chatops/overview.md) for how to connect a chat tool to ilert.

## Create an incident channel

You can connect a channel in two ways:

* **While declaring an incident** — select **Create incident channel** in the [Declare incident dialog](/incidents-and-status-pages/incidents/declare-an-incident.md).
* **From an existing incident** — in the incident view, use the **Incident channel** section to create one.

If more than one chat platform is connected to your account, you choose which one to use when the channel is created.

{% hint style="info" %}
An incident can have one incident channel. The platform is fixed once the channel is created—you can disconnect a channel, but you cannot switch it to a different platform.
{% endhint %}

## What reaches the channel, and what does not

A [comment](/incidents-and-status-pages/incidents/incident-timeline-and-comments.md#comments) written on the incident is posted into the channel as a threaded reply, so people watching there see it without switching windows. It does not work the other way round: what is said in the channel stays in the channel and never appears on the [timeline](/incidents-and-status-pages/incidents/incident-timeline-and-comments.md).

The channel is not lost for it. When you [generate a postmortem](/incidents-and-status-pages/incidents/postmortems.md), the ilert bot can read the channel and pull the parts that mattered into the document — which is where the conversation ends up on the record.


---

# 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/incidents-and-status-pages/incidents/incident-channels.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.