> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/platform/platform-core/alert-and-escalation.md).

# Alert & Escalation

Alert & Escalation covers the notification and escalation capabilities that help BuildingPro Suites react to events and keep users informed.

This section focuses on how messages are delivered, how users are notified, and how external channels such as email, SMS, Slack, or Google Chat are used when an escalation is triggered.

## What You Can Manage Here

This section is divided into two areas:

* [Escalations](https://docs.buildings.ability.abb/collection/platform/platform-core/alert-and-escalation/escalations.md) for defining who is notified, how they are notified, and when notifications are sent
* [Notifications](https://docs.buildings.ability.abb/collection/platform/platform-core/alert-and-escalation/notifications.md) for managing in-app and browser-based notifications seen directly by users

## How the Areas Relate

Notifications and escalations serve different purposes:

* **Notifications** are shown inside BuildingPro Suites or in the user's web browser
* **Escalations** send alerts through external communication channels and can be configured with schedules, recipients, and channel-specific settings

Together, these features ensure that important events are visible both inside and outside the platform.


---

# 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.buildings.ability.abb/collection/platform/platform-core/alert-and-escalation.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.
