> For the complete documentation index, see [llms.txt](https://docs.widgelix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.widgelix.com/actions-formerly-rule-engine/escalation-chain.md).

# Escalation Chain

An **Escalation chain** turns an action into an on-call style alert. The alert is assigned to a user, who has to acknowledge it within a time window. If nobody acknowledges it in time, it moves on to the next step.

## Enable the escalation chain

In the action editor, below the THEN actions, turn on **Escalation chain**. A first step is created automatically.

<figure><img src="https://2494440469-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fggsr9Xlsze5cwVr4WMof%2Fuploads%2FNAFzqUyZrBDQlGrfdQPj%2Fthen-escalation-schedule.png?alt=media&amp;token=fdcfa894-d826-494b-9e0a-d55f0e9b2f03" alt="Escalation chain in the action editor"><figcaption><p>Escalation chain with one step</p></figcaption></figure>

* **Auto-resolve when condition clears**: when ticked, the alert is resolved automatically as soon as the action's condition is no longer true, so nobody has to close it manually.
* Each **Step** card shows the assigned user, the acknowledge window (e.g. *Ack: 15 minutes*) and its notification channels.
* **+ Add escalation step** adds the next level, for example the team lead after the on-duty engineer.

## Configure a step

Click a step card to open **Edit escalation step**.

<figure><img src="https://2494440469-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fggsr9Xlsze5cwVr4WMof%2Fuploads%2FzyFBKgJM4JEItxpN4RhG%2Fescalation-step.png?alt=media&amp;token=0e759be2-ab57-4a2d-9931-77075c148b30" alt="Edit escalation step dialog"><figcaption><p>Edit escalation step</p></figcaption></figure>

| Field                     | Required | Description                                                                                                                                                                                                                                 |
| ------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Assign to user**        | Yes      | Member of the organization responsible for this step.                                                                                                                                                                                       |
| **Acknowledge window**    | Yes      | How long the user has to acknowledge the alert (seconds, minutes or hours; default 15 minutes) before it escalates to the next step.                                                                                                        |
| **Notification channels** | Yes      | How the user is notified. **Email** to the user's profile email and in-app notification are added by default. Use **Edit** to change a channel, **Remove** to delete it and **+ Add channel** to add Email, SMS, Slack, Discord or Webhook. |

Click **Save step**.

## Acknowledging an alert

When an alert with an escalation chain fires, the assigned user receives the notification together with an in-app pop-up that has **Acknowledge** and **Open event** buttons. Acknowledging stops the escalation for that alert.

All open alerts, their current escalation step, acknowledgement deadlines and history are tracked on the **Events** page. See [Incidents & Escalation](https://docs.widgelix.com/events/incidents-and-escalation.md).

{% hint style="info" %}
The escalation chain works in addition to the regular THEN actions: the THEN actions still run, while the chain makes sure a specific person takes ownership of the alert.
{% endhint %}
