> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aciona.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Notifications

> Which channels exist, when each notification is sent, and how they complement each other.

Notifying is the heart of the product: an incident nobody receives is the same as an alert lost in a channel.

## Channels

<Columns cols={2}>
  <Card title="Email" icon="mail" horizontal href="/en/notifications/email">
    Always available, with action links to acknowledge and take ownership.
  </Card>

  <Card title="Push" icon="smartphone" horizontal href="/en/notifications/push">
    Browser and mobile. The channel that actually wakes someone up.
  </Card>

  <Card title="Slack" icon="slack" horizontal href="/en/notifications/slack">
    A card in the team channel, with actions.
  </Card>

  <Card title="Microsoft Teams" icon="message-square" horizontal href="/en/notifications/microsoft-teams">
    An Adaptive Card in the team channel.
  </Card>
</Columns>

## When each notification is sent

| Event                | What it triggers                                                            |
| -------------------- | --------------------------------------------------------------------------- |
| **Incident created** | Notifies the responder resolved by the schedule.                            |
| **No responder**     | When no on-call person could be resolved, notifies the organization owners. |
| **Acknowledged**     | Tells the team someone is looking.                                          |
| **Assigned**         | Notifies whoever received the incident.                                     |
| **Escalated**        | Notifies the new escalation target.                                         |
| **Resolved**         | Closes the loop for everyone following along.                               |

## How the channels combine

The channels do **not** replace each other — they stack, and each has a role:

<Steps>
  <Step title="Push is the paging channel">
    It is the only one that reliably pulls someone out of sleep. It must be active for anyone in the rotation.
  </Step>

  <Step title="Email is the record channel">
    It always arrives, carries the full context and leaves an auditable trail.
  </Step>

  <Step title="Slack and Teams are the team channel">
    They give collective visibility: who else is watching, who already acknowledged, what the status is.
  </Step>
</Steps>

<Note>
  Slack and Microsoft Teams messages go to the configured channel **regardless** of whether personal recipients were resolved. Even if the schedule fails to point at anyone, the team still sees the incident in the channel.
</Note>

## Delivery record

Every notification attempt is recorded with channel, destination, status, attempt count, error (if any) and send time. That makes "was I paged?" a question with a precise answer.

The incident moves to `notified` when **any** channel delivers successfully.

<Columns cols={2}>
  <Card title="Preferences and snoozing" icon="bell-off" horizontal href="/en/notifications/preferences" />

  <Card title="I did not get a notification" icon="life-buoy" horizontal href="/en/troubleshooting/notification-not-received" />
</Columns>