For the complete documentation index, see llms.txt. This page is also available as Markdown.

Notification settings

How ilert reaches you: the contacts it can use, the channels you have activated, and the rules that decide which one fires when.

Everything about alerting so far decides that you should be told something. This page decides how — and it is per-person, not per-account. Two people on the same escalation policy can be reached completely differently.

Click your avatar in the top right and choose Notification settings.

An admin can open anyone's notification settings and change them. That is deliberate: a new joiner who has not set up any rules will not be paged, and someone has to be able to notice and fix that.

There are two halves, and the first has to come before the second: a rule can only use a channel you have already activated.

Contacts and channels

The contact information section of ilert notification settings, listing an email contact, two phone number contacts with one marked PRIMARY, and a registered push notification device, each with links to add another contact.
Contacts are addresses. Channels are the ways ilert can use them.

A contact is an address — an email address or a phone number. A channel is a way of reaching that address:

Contact
Channels it can carry

Email address

Email

Phone number

SMS, Phone call, WhatsApp, Telegram

Mobile device

Push

ilert creates an email contact from your login address automatically, and push devices appear on their own once you sign in to the iOS or Android app — there is a QR code on this page to make that login quick.

Add the rest with Add email or Add phone number. Each channel then has to be activated, which means entering a code ilert sends to it. Activating a phone number by SMS activates phone calls on it at the same time; WhatsApp and Telegram have their own flows, described as you go.

Use Send test notification afterwards. It is the only way to learn that a channel is genuinely working before an incident asks the question for you.

Notification rules

Notification rules in ilert, showing a High priority alerts & incidents card with two rules — immediately notify via Push, then one minute after assignment notify via Voice at a masked phone number — a Low priority alerts card reading do not notify me, an Alert updates card set to notify via Push when an alert is resolved, and a Status update notifications card set to notify by email.
Each category is independent. An empty category means silence, not a default.

Five categories, each with its own rules:

Category
Fires when

High priority alerts & incidents

A high-priority alert is assigned to you — on creation, or when you are added as a responder. Also when you are paged onto an incident

Low priority alerts

The same, for low-priority alerts. These never escalate

Alert updates

Status update notifications

A status update reaches you as a subscriber. See below

On-call reminder notification

A set time before one of your on-call shifts begins, from 15 minutes to 24 hours, or as it begins

To add one, expand a category and click Add notification rule, then choose a contact and channel. Not every category offers every channel: Alert updates and On-call reminder notification have no phone call, and Status update notifications offers only email, SMS and push.

Chaining rules with delays

Alert rules take a delay, which is what turns a list into an escalation of its own:

Immediately notify me via Push 1 minute after assignment, notify me via Voice

The second rule only fires if you have not responded within the minute. Push first, then something that wakes you, is the pattern most on-call engineers land on.

Incident pages

When someone pages you onto an incident — directly, or through a team, an on-call schedule or an escalation policy — ilert reaches you through your High priority alerts & incidents rules. That is what the "& incidents" in the name means. There is no low-priority path: a page always uses this category.

Two things work differently from an alert:

  • Every rule fires at once. Delays are ignored, so a chain built for alerts — push, then a phone call a minute later — rings your phone straight away when you are paged.

  • WhatsApp and Telegram rules are skipped. A page goes out by email, SMS, phone call and push. If your only rules here use WhatsApp or Telegram, a page does not reach you.

With no rules in this category, a page reaches you on no channel at all, but the incident still lists you as Notified.

Alert updates

These keep you informed about alerts that are, or were, yours. Each rule names one event:

Event
Fires when

accepted

Someone else accepts an alert that was assigned to you

resolved

An alert assigned to you is resolved by someone else, or resolves automatically

escalated

An alert assigned to you escalates on its own when the timeout runs out, or is reassigned to another user or an on-call schedule. Moving it to a policy level by hand, or reassigning it to an escalation policy, does not count

commented

Someone else comments on an alert you are a responder on

Status update notifications

This category is how ilert users hear about status updates. A status update published with notifications on reaches you here if you subscribe to the incident it is posted from, to a service it affects, or to a status page it appears on. Subscribing more than one way does not send you the same update twice.

Subscribing is not enough on its own. With no rule here, ilert delivers nothing, however many services and status pages you subscribe to.

The same rules carry the notice you get when you are added to or removed from a service's or a status page's subscribers, and maintenance window notices to the subscribers of its services and of the status pages that show them. Despite the wording on the card, being added as a subscriber to an incident sends no notice of its own.

Rules here use email, SMS or push. SMS also needs SMS subscription notifications enabled for your account; without that, ilert refuses to save an SMS rule in this category.

Responding from the notification

Notifications are two-way. You can act on an alert from the channel it reached you on, without opening ilert:

  • Acknowledge it — escalation stops

  • Resolve it

  • Escalate to the next level in the policy

Reply to the SMS, press a key during the phone call, tap the push notification. Which options appear depends on the channel.

FAQ

I am not getting notified at all.

Check, in this order: the channel is activated (not merely added), the category has at least one rule, and the alert source's notification priority matches the category you put rules in. High-priority rules do nothing for an alert sent as low priority.

I subscribed to a service, but its status updates never reach me.

Add a rule to Status update notifications. A subscription decides which updates are yours; this category decides whether and how they are delivered, and without a rule there is nothing to deliver.

Can I be reached differently outside working hours?

Not from this page — rules do not know the time. The time-based decision lives on the alert source, via support hours, which flips alerts between high and low priority. Give your low-priority category quieter channels and the effect is the same.

How do I stop everything temporarily?

Mute notifications, for a holiday or a night off.

Does a phone number have to be verified to receive calls?

Yes. Verifying by SMS covers both SMS and phone calls on that number.

What is the primary phone number for?

It is the number ilert uses where a single number is required, and the one shown on your profile. Set it from the phone number's own menu.

Last updated

Was this helpful?