Which channel wakes an engineer: phone, SMS, push or Slack
A phone call is the channel most likely to wake a sleeping engineer, SMS is the most widely reachable, push depends on an app that is installed and signed in, and chat is for people who are awake. Each fails in its own way, so layer them, require an acknowledgement, and test the whole path from the phone.
The question is what wakes a person
Choosing a paging channel is not about features. It is about a specific moment: an engineer is asleep, the phone is on the bedside table, and an alert has to get through. Every channel is a chain with links that can fail. A message must leave the sender, cross a network, reach a device, be allowed to make a sound, and be noticed by a person. Any link can break.
Two ideas keep the discussion honest. The first is the difference between delivered and acknowledged. A message can be delivered to a silenced phone and never seen. The number to trust is how many pages a human acknowledged, and how quickly. The second is that no channel is reliable on its own. The answer is a layered path, tested from the receiving end.
Channel by channel
| Channel | What it takes to wake someone | How it fails |
|---|---|---|
| Phone call | A ringing phone with signal | Silenced or do-not-disturb, spam blocking, voicemail answers |
| SMS | A phone with signal and a message tone | Carrier filtering or delay, silent mode, a muted sender |
| Push notification | An installed, signed-in app with permission to alert | Signed out, battery limits, silent mode, no data connection |
| Chat (Slack, Teams) | A running app and notification settings that allow it | Muted channels, do-not-disturb schedules, “away” status, message lost in a busy channel |
| Someone looking at their inbox | Filtering, delay, nobody reading it at night |
Each row is worth a closer look, because the failure modes are what a plan has to cover.
Phone calls
A call is the most insistent channel. It rings, it keeps ringing, and it needs no app or data connection. That is why it sits at the top of most escalation policies for urgent alerts. Its failures are about the phone’s rules. Do-not-disturb and focus modes can silence calls unless the number is allowed, and some phones separately silence unknown callers. Some phones and carriers screen or label automated calls as spam. Most phones have an emergency bypass for chosen contacts, so add the paging numbers to it, and add every number the tool calls from, since it may use more than one. A call that reaches voicemail can look “answered” to a system that only checks the line was picked up, so a page should need a deliberate action, such as a keypress or a spoken confirmation, to count as acknowledged.
Calls also interrupt. Use them for what deserves it. How an AI can place and run the call is covered in how voice paging works.
SMS
Text messages reach almost any phone, with no app and no mobile data, and often work with weak signal. They are the widest net. Their limits are carrier behaviour and the phone’s settings. In some countries carriers filter or delay automated and bulk messages, and senders may need to register their traffic. Delivery is not guaranteed, and a message tone is easy to miss or silence. A short message also carries little context, so link to the incident.
Push notifications
A push notification needs an app that is installed, signed in and allowed to alert, and a phone that will let it. Battery optimisation can delay or drop notifications from an app the system thinks is idle. Silent mode and focus settings suppress them unless the person has granted an override. When someone gets a new phone, the app has to be signed in again, and until then the path is broken with no error. Push is convenient and cheap, but it is only as good as each person’s setup.
Slack and Teams
Chat notifications follow each person’s own settings: channels muted, do-not-disturb schedules, mentions only. A message in a busy channel is easily lost. Chat is at its best when people are awake: it starts the coordination, keeps the record and brings in colleagues. It is a poor way to wake someone unless a direct message or mention is set to break through, and even then it depends on the app running.
Layering the channels
Because every channel fails somewhere, a good policy layers them. A common shape:
- First step: a gentler channel, or two together, for example SMS and a chat message.
- After a short wait with no acknowledgement: a phone call to the same person.
- After a longer wait: the same sequence for the next person, as the escalation policy defines.
Three rules help. Match the strength to the urgency: reserve calls for alerts that justify one. Make the last channel for a person the strongest. And always require an acknowledgement, so the policy moves on when nobody has confirmed. A 30-day plan for alert fatigue keeps the strong channels meaningful by keeping the volume low.
Tracing a missed page: an example
This example is invented. An urgent alert fires at night. The policy sends a push notification, waits five minutes, then calls. Nobody acknowledges, and the page escalates to the secondary engineer, who answers. The review asks what went wrong for the primary.
The trail is short. The push was delivered to the app, which had been signed out since the engineer changed phones the week before, so it made no sound. The call rang, but the phone was in a focus mode that silenced numbers not in the contacts, and the paging number was not. Two links failed for two different reasons, and the layered path worked only because the secondary engineer was next in line.
The fixes are small: a setup checklist for anyone who changes phone, the paging numbers allowed through focus modes, and a monthly test page. None of them needed a new tool. They needed someone to look at the path from the receiving end.
What to measure
Delivery reports are easy to collect and easy to misread. The measures that tell you whether the path works are about people:
- Time to acknowledge, by channel and by hour. A channel that is slow at night is telling you something.
- Pages that nobody acknowledged at the first step. A rise means the first channel is not reaching people.
- Results of test pages. Who was reached, by which channel, how quickly.
- Escalations caused by no answer, not by a hard problem. These are missed pages in disguise.
Review them alongside the wider numbers described in MTTA vs MTTR. A slow acknowledgement time is often a delivery problem before it is a people problem.
Set up each person, then test
The last mile is the person’s phone. A short setup for everyone on the rotation:
- Allow calls and messages from the paging numbers through do-not-disturb and focus modes, and use the phone’s emergency bypass for them if it has one. Add every number the paging tool uses.
- Turn off battery optimisation for the paging and chat apps, and keep them signed in.
- Set a distinct sound for pages, at a volume that wakes.
- Keep a second way to be reached, such as a second number.
Then test the path from the phone, not from the dashboard. Send a real page at a realistic hour and check that it woke the person and that they could acknowledge it. Repeat the test when someone joins, changes phone or number, or changes their settings, and on a regular schedule regardless. A paging path you have not tested is a hope.
Frequently asked questions
Which paging channel is the most reliable?
None is reliable alone. A phone call is the hardest to sleep through and does not need an app, but it can be silenced, blocked or sent to voicemail. SMS reaches the widest range of phones but can be filtered or delayed. Reliability comes from layering channels and confirming that a person acknowledged.
Why did an engineer miss a page that was delivered?
Delivered means the message reached the phone or the app, not that a person saw it. Silent mode, do-not-disturb, battery settings, notification permissions and a signed-out app can each stop a delivered message from making a sound. Measure acknowledgement by a person, not delivery.
Is a Slack or Teams message enough to page someone?
Not at night. Chat notifications follow each person's settings, which usually mute channels, respect a do-not-disturb schedule and rely on the app running. Chat is excellent for coordination while people are awake and for a shared record. For waking people, pair it with a phone call or SMS.
Should we send every channel at once?
For the most urgent alerts, sending two channels together is reasonable, for instance SMS and a call. Sending everything to everyone teaches people to ignore all of it. Use a sequence for most alerts: a gentler channel first, a stronger one if nobody acknowledges within a few minutes.
How often should we test the paging path?
Whenever a person joins the rotation, changes phone or number, or changes their phone settings, and on a regular schedule regardless. Send a real test page at a realistic hour and confirm it woke the person and that they could acknowledge it.