> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/alarm/iot-alerts-app.md).

# IoT Alerts App

Receive Kilo operational alarms on iPhone and Android with the IoT Alerts app, including iOS Critical Alerts.

A push notification is only useful if it reaches the right responder in the state they're actually in — phone locked, in a meeting, on a night shift, or away from any workstation. The **IoT Alerts** app puts Kilo's operational alarms on the phones of your on-call team and escalates them with the urgency each severity demands.

The app is a delivery surface for the alarms you already define on the web platform. You author alarm definitions, severity policies, and escalation chains in Kilo IoT Server; the app receives the resulting events, signals them according to severity, and lets responders acknowledge or resolve from the field.

## Choosing Business Use

The first time you open IoT Alerts, it asks how you'll use it. Select **Business Use** for the Kilo IoT experience — the app signs in against your Kilo account, connects to your deployment, and applies Kilo branding throughout.

## Download

* **iPhone:** [App Store](https://apps.apple.com/us/app/chirp-alerts/id6756504956)
* **Android:** [Google Play](https://play.google.com/store/apps/details?id=io.chirpwireless.alarm)

## Approved for Critical Alerts on iOS

Apple restricts which apps may break through silent mode and a Focus or Do Not Disturb schedule. IoT Alerts holds Apple's **Critical Alerts** approval, so a Critical Kilo alarm can reach an on-call engineer even when the phone is silenced — provided the responder grants the Critical Alert permission when prompted. Lower-severity alarms follow the phone's normal notification rules. See [When Alerts Wake Your Phone](/alarm/iot-alerts-app/alert-behavior.md) for the exact behavior at each level.

## How it fits the alarm system

| You configure on the web                                                                                   | The app does                                                 |
| ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
| [Alarm definitions](/alarm/notification-rules.md) and [severity](/alarm/notification-delivery-settings.md) | Signals each event at an intensity that matches its severity |
| [Escalation chains](/alarm/escalation-and-response.md) with a **Push** step                                | Delivers the push leg of the chain to registered devices     |
| The **Push** channel under Alarm → Settings ([Delivery Channels](/alarm/notification-channels.md))         | Registers the device and receives delivery once Push is On   |

## What to read next

| Page                                                                   | When to read it                                                              |
| ---------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| [Set Up IoT Alerts](/alarm/iot-alerts-app/getting-started.md)          | Install, choose Business Use, sign in, and enable push delivery.             |
| [When Alerts Wake Your Phone](/alarm/iot-alerts-app/alert-behavior.md) | Understand exactly which severities ring the alarm and which arrive quietly. |
| [Acknowledge and Resolve](/alarm/iot-alerts-app/managing-alerts.md)    | Work the Inbox and manage Alert Definitions from the app.                    |


---

# 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.kiloiot.io/alarm/iot-alerts-app.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.