> 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/knowledge-base/alerting-and-notifications/which-alerting-channels-does-ilert-support.md).

# Which alerting channels does ilert support?

ilert supports bi-directional alerting via:

* **SMS**: ilert supports sending SMS alerts worldwide. For many countries, SMS alerts are sent from a local number. See [here](/alerting/overview/phone-numbers.md#sms-alerts) for details.
* **Phone calls**: ilert supports international voice calls and converts the alert summary text into speech using text-to-speech technology. See [here](/alerting/overview/phone-numbers.md#voice-alerts) for the caller IDs that ilert uses when making phone calls.
* **Emails**
* **Push notifications** on iOS and Android
* **WhatsApp**
* **Telegram**

These channels are one-to-one notification channels and are configured in the [user's profile](/alerting/configure-alerting/notification-settings.md).

Moreover, ilert sends alerts to chat tools like [Slack](/chatops/slack.md), [Microsoft Teams](/chatops/microsoft-teams.md), [Google Chat](/chatops/google-chat.md), [Mattermost](/integrations/outbound-integrations/mattermost.md) and [Discord](/integrations/outbound-integrations/discord.md). These are configured as alert actions, and responders can accept and resolve alerts in Slack, Microsoft Teams and Google Chat without leaving the chat.

{% hint style="info" %}
**Related Documentation**

* [Phone Numbers](/alerting/overview/phone-numbers.md)
* [Notification Settings](/alerting/configure-alerting/notification-settings.md)
* [Chat Integrations](/chatops/overview.md)
  {% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ilert.com/knowledge-base/alerting-and-notifications/which-alerting-channels-does-ilert-support.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.