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

# Setting up notifications on iOS

<Info>
  **Download our mobile app**

  If you'd like the best possible experience as a responder, download our mobile app [here](https://apps.apple.com/us/app/incident-io/id6471268530).
</Info>

<Info>
  For responders in Mainland China, see [Mobile app in China](/on-call/china-mobile-app) — Critical Alerts aren't
  available in the 事件incidentio app, so push notifications can't bypass silent mode.
</Info>

When you are paged, we'll try and contact you according to your [notification rules](https://app.incident.io/~/user-preferences/on-call-notifications).

By default, assuming you've enabled them, this will include:

* Push notification
* Phone call
* SMS
* Email
* Slack direct message
* WhatsApp message

For push notifications, phone calls, and SMS messages, there are steps you can take to ensure you get notified, regardless of what your phone's silent mode and do-not-disturb settings are set up like.

***

## Phone calls + SMS

To receive phone calls and SMS that bypass silent mode and Do Not Disturb, you'll need to save the incident.io contact and enable Emergency Bypass.

1. Add the incident.io contact card to your phone's contacts
   * Open the **incident.io** app, go to **Settings** → **Contacts**, and enable the **incident.io contact** toggle to keep the contact automatically updated
2. Open the **Contacts** app and tap **Lists** in the top-left corner
3. Select **All Contacts** — do not use the "incident.io" section (see note below)
4. Find and open the **incident.io On-call** contact
5. Tap **Edit**, then tap **Ringtone**
6. Enable **Emergency Bypass** so calls ring even when your phone is silenced
7. Repeat for **Text Tone** if you want SMS alerts to bypass silent mode
8. Tap **Done** to save

<Info>
  **Note for iOS 18+ users:** You may see an "incident.io" section in your Contacts app. There's a known Apple bug
  where editing contacts from this section causes the screen to become stuck. Always edit from "All Contacts" instead.
  We've reported this to Apple.
</Info>

<img src="https://mintcdn.com/incidentio-18bb4170/ZxFf2cgoY4sfLjxB/images/help-centre/setting-up-notifications-on-ios/screenshot-1.png?fit=max&auto=format&n=ZxFf2cgoY4sfLjxB&q=85&s=03e9b1e0f39c8b1b76faee3911ef8119" alt="emergency-bypass-steps.png" width="4952" height="2622" data-path="images/help-centre/setting-up-notifications-on-ios/screenshot-1.png" />

**Testing:** Send yourself a test page from your incident.io dashboard while your device is locked and silenced to confirm calls come through.

<Note>
  In some iOS versions the automatic contact can't be edited, which means you may not set up DND bypass, so to work around this, we can create an editable version.

  <Frame>
    You can enable this by going to Setting → Contacts → Can't set up Do Not Disturb bypass
  </Frame>
</Note>

### Call screening

iOS can screen calls from unknown numbers before they reach you, using features like [Screen Unknown Callers and Silence Unknown Callers](https://support.apple.com/en-gb/guide/iphone/iphe4b3f7823/ios). When these are on, an on-call phone call from an unknown number may be intercepted, sent to voicemail, or answered by an automated screening assistant instead of ringing your phone.

This causes two problems for on-call:

* You might miss the call entirely, because it never rings through to you.
* The screening assistant can interact with our call and register a keypress, which we may record as you acknowledging the escalation even though you never picked up.

We can't change how iOS call screening answers calls. The fix is to make sure our number counts as a known contact so screening lets it straight through:

1. Save the incident.io contact card and enable **Emergency Bypass**, following the steps above.
2. Confirm the incident.io On-call number is saved in your **Contacts**. Screening applies to unknown numbers, so a saved contact won't be screened.
3. Send yourself a test page while your device is locked to confirm the call rings through as expected.

<Warning>
  If you rely on iOS call screening, you must have the incident.io contact card saved. Without it, screening can silence
  our calls or auto-answer them, and an auto-answered call can be misrecorded as an acknowledgement.
</Warning>

## Push notifications

iOS has a concept of `Critical notifications`, which are push notifications that'll make a noise, regardless of whether your phone is on silent, or if you are in sleep/do-not-disturb. The incident.io app supports these natively so as long as you agreed to these notifications during set up of the app, you'll receive them. If you did not agree to them, you'll see a warning on the home screen of the app.

To enable these notifications, open the `Settings` app on your phone, scroll down to incident.io, select `Notifications` and then enable critical notifications.

<Info>
  Please note that the following settings in iOS could interfere with push notifications:

  **[Announcing notifications](https://support.apple.com/en-gb/guide/airpods/dev8c670727e/web):** if you have toggled
  "Announce notifications" in your incident.io app settings, sounds might go through connected AirPods or other devices
  when your device is locked.

  **Screen Time:** if you have a time limit set on your device, iOS might not deliver notifications correctly. Consider
  adding the incident.io app to your list of "Always on" apps.
</Info>

**Apple Watch**

If you have an Apple Watch paired with your iPhone, notifications are delivered to your watch by default when it's on your wrist and your iPhone is locked. This means your iPhone won't make a sound — the notification goes to your watch instead.

If you'd prefer to always receive incident.io notifications on your iPhone, open the **Watch** app on your iPhone, tap **Notifications**, find **incident.io** in the list, and select **Off**. This will stop notifications from being mirrored to your watch, so they'll always play on your phone.

Connected **headphones or earbuds** (such as AirPods or other Bluetooth audio devices) can also affect where notification sounds are routed. If you have "Announce Notifications" enabled, sounds may play through your AirPods instead of your phone's speaker when your device is locked.

**Custom notification sounds**

For push notifications, you can pick a custom notification sound from Notifications > **Notification sounds**. If you want the notification to make a sound for a long time, we have notification sounds ranging from 1 second to 2 minutes long.

**Contact card**

If you're unable to provide contacts permission, you can still manually download our contact card [here](https://app.incident.io/api/mobile/responder_vcard) - however you'll need to periodically update it yourself as we may add phone numbers from time to time.

## WhatsApp

You can receive escalations as WhatsApp messages, and acknowledge or mark yourself as not available straight from the buttons in the message. We support WhatsApp messages only, not calls.

To make sure your pages come through, allow the WhatsApp app to override Do Not Disturb: head to **Settings → Focus → Do Not Disturb**, tap **Apps** under **Allowed Notifications**, and add **WhatsApp**.
