# Alerts & schedule

The schedule is the same for every item, so nobody has to configure reminders. Alerts get louder as the date gets closer, and stop once someone has it in hand.

## The schedule

| When | What happens |
| --- | --- |
| 30 and 14 days before | One alert each. |
| Final 7 days | An alert every day until someone snoozes it. |
| On the day | An alert saying it expires today. |
| After expiry | A daily reminder for up to a week, then Radardue stops. |

Alerts are worked out every few minutes, so a newly added item that's already close to its date alerts straight away.

## What an alert says

The subject names the client, the item and the time left, for example `[Acme Dental] shop.acme-dental.com expires in 7 days`. The body adds the type, the exact date, the issuer or registrar, and a link to the item in Radardue.

## Snoozing

When someone is dealing with a renewal, open the item and click **Snooze alerts** (it appears within 30 days of expiry). Alerts for that item pause until **3 days before** the date, then come back as a final check.

A snooze belongs to one expiry date. Once the certificate is renewed or you change a renewal's date, the new date is watched from scratch; there's nothing to un-snooze.

## Who gets alerts

Every alert channel on the account receives alerts for every client, except channels limited to one client, which only receive that client's alerts. That lets you send a customer's alerts to their own Slack or Discord while your team still sees everything. See [Alert channels](https://radardue.com/docs/alert-channels).

If none of the channels accept an alert (for example a webhook is down), Radardue tries again on the next run.

## Weekly summary

Each person can turn on a Monday email under [Account → Weekly summary](https://radardue.com/app/account). It lists everything due in the next 30 days plus any failing checks, across all clients. It's sent from 07:00 UTC on Mondays.

Source: https://radardue.com/docs/alerts