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

# On-call notifications

> Choose how you are paged, set quiet hours and acknowledge a page from your phone or Slack.

export const Plan = ({tier}) => <Badge color="blue">{tier} plan</Badge>;

This page covers how the person on call finds out and how they acknowledge. To set up schedules and rotations first, see [Set up on-call](/guides/respond/on-call).

<Plan tier="Free" />

## Choose how you are notified

You are told over up to five channels. Each person sets up their own under **Account**.

| Channel | What it does | Set it up |
| - | - | - |
| Push | A notification on each device you enable, with an **Acknowledge** button. It does not break through silent mode or Do Not Disturb. | **Account**, **Push notifications**, **Enable on this device** |
| Pushover | A message that keeps ringing through Do Not Disturb until you acknowledge it. | **Account**, **Pushover**, paste your user key, **Save Pushover key** |
| Telegram | A chat message with an **Acknowledge** button. It does not break through Do Not Disturb. | **Account**, **Telegram**, **Link Telegram**, then press Start in the bot |
| Slack DM | A direct message with an **Acknowledge** button. | Link your Slack account, see [Slack](/guides/respond/slack) |
| Email | Always part of the policy. | Your account address |

On an iPhone or iPad, push needs iOS 16.4 or later and a Home Screen install: in Safari tap Share, then Add to Home Screen, open SRE Agent from its icon and enable push there. Use **Send a test** on each card to check a channel. The Pushover and Telegram cards appear on **Account** once they are available for your organization.

<Tip>
  Push and Telegram are nudges, not pagers. If a page must wake you, add Pushover, or keep Slack or
  email as a backup.
</Tip>

If you are on call and a channel is missing a link, the **On-call** page and your **Account** page say exactly what to fix.

### Per-moment steps and the organization minimum

Under **Account**, **On call**, you choose which channels fire, and after how many minutes, for each moment: you are paged, a page is repeated because nobody acknowledged it, your shift is about to start or has ended, an override puts you on or takes you off call, an override that covers you changes, and (for admins) a schedule will have nobody on call.

An admin sets the minimum for everyone under **Settings**, **Notifications**, **On-call policy**, then **Save on-call policy**. By default a page goes out by push and Slack DM at once and by email after 5 minutes. You can add channels or earlier delays, but you cannot remove what the policy requires. Email is always part of it, and a page can never be turned off. The same card sets how often an unacknowledged page repeats and how many times, how long before a shift the incoming person is told, and how far ahead to warn about gaps.

### Quiet hours

Under **Account**, **On call**, tick **Hold reminders and override notices during quiet hours** and set **From** and **until** in your timezone. The window can cross midnight. **Quiet hours never hold a page**, including repeated pages.

## Acknowledge a page

Acknowledge from wherever the page reached you: the **Acknowledge** button on a push notification, in the Pushover app, in the Telegram message, on the Slack DM or channel message, or on the alert page. Acknowledging stops the repeats and rewrites the Slack and Telegram messages to show who took it. You must still be an active member with a role that can acknowledge alerts.

## See what was sent

An alert page shows a line such as **Notified via push 21:03, Slack DM 21:05**. The **On-call** page lists the latest notifications with who, channel, status, reason and time. A step that could not send (no device, no linked chat, no linked Slack account) is shown as skipped with the reason, and the next channel still goes out.

## Related

* [Triage alerts](/guides/respond/alerts): acknowledge from the alert page.
* [Manage people and roles](/guides/administer/organizations-and-roles): who can acknowledge a page.
* [Troubleshooting](/guides/reference/troubleshooting): why a page was not delivered.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.