iPhone Emergency Alerts Are Not All The Same, And They Are Doing It Wrong For Most People
iOS sends several categories of emergency alerts under the Settings > Notifications page, and each one has a different behavior pattern that Apple's documentation muddies together. You get presidential alerts, AMBER alerts, severe threat alerts, public safety alerts, and the test notifications that every carrier pushes once a year. The system treats them as one monolithic bucket in the UI, which is misleading because the underlying priorities are completely different. Presidential alerts cannot be turned off at all. The rest can, but the toggles are split across two menus and one of them moved around in iOS 17 without any visible notification. What most people miss is that the "Alerts" toggle you see under Settings > Notifications does not control the sound or the banner for every category. There is a separate switch under Settings > Notifications > Critical Alerts. That second menu item only shows up if your carrier supports it and if you have Location Services enabled for System Services. If either condition is false, the Critical Alerts section disappears entirely and you are left wondering why your phone stays silent during a local emergency while nearby Android devices go absolutely nuts. I hit this exact wall when I moved to a rural county in northern Ohio and my wife's iPhone SE kept missing sheriff office AMBER alerts while her Samsung from three years earlier lit up every screen in the house. The fix was turning on System Location Services > Significant Locations and then enabling the Critical Alerts toggle for her carrier, which is Verizon at the time. Took about ten minutes of digging through Settings panels. Here is how the priority stack actually works when a new alert arrives. Critical Alerts bypass Do Not Disturb and the physical Silent switch. They use the highest possible audio priority and they will wake a sleeping device. Normal emergency alerts, like severe weather warnings, respect Do Not Disturb unless you have explicitly allowed alerts from the issuing authority. Presidential alerts bypass everything, including the mute switch, and they play a distinctive two-tone siren that you cannot change. That siren is hardcoded into the firmware. You cannot swap the audio file, you cannot lower the volume below a certain threshold during an active alert, and there is no settings toggle for it.
To configure what your iPhone actually does with these notifications, go to Settings > Notifications. Scroll down to the bottom section labeled EMERGENCY AND PUBLIC SAFETY. You will see AMBER Alerts, Critical Alerts, and Severe Threat Alerts. Toggle each one based on whether you want to receive that category. The Default Alerts section below that controls public safety messages from your local government, which most people do not realize can be individually disabled. If you live in a flood zone, leave Severe Threat Alerts on. If you live downtown where those alerts are mostly construction accidents and lost pets, turn them off and save yourself the distraction. There is a configuration profile option that some enterprise environments push to devices. It is called EmergencyNotifications.plist or something similar, and it can override the user-facing toggles depending on the iOS version. I ran into this when helping a friend who worked for a municipal emergency management office. Their phones were receiving alert spam from a misconfigured test script that sent fake earthquake warnings at 3 AM. The workaround was removing the configuration profile under Settings > General > VPN and Device Management, then restarting. Without that, the toggles in the Notifications menu were grayed out and completely ineffective. Another thing nobody explains is that carrier provisioning matters more than iOS settings. AT&T, T-Mobile, and Verizon all have different threshold configurations for when they relay a NLEAS alert to your device. In some markets, a tornado warning has to reach a specific EF rating before the carrier decides to push it. In other markets, any warning from the local NWS office gets pushed. This is not something you can control from your phone. It is baked into your carrier's subscription data. If you want to know what your carrier is actually configured to send, you have to call them and ask, or check the FCC's NLEAS carrier compliance page. The information is public but scattered across four different documents.
If you want finer-grained control, jailbreaking is technically an option but I would not recommend it for this particular use case. The system-level alert handling is deeply embedded in the kernel extension layer, and a bad tweak can actually prevent alerts from arriving rather than just silencing them. The official settings cover 95 percent of what a normal user needs. The remaining 5 percent requires understanding your carrier's provisioning and your local emergency management's alert philosophy. That second part is outside the phone entirely. One practical tip that saves time: enable the "Allow Alerts When Silent" option inside the Critical Alerts section. By default, even Critical Alerts will not make sound if your phone is in the physical Silent position, unless the alert is a Presidential alert. For everything else, you need that checkbox turned on if you want the loud alarm to trigger while the ring/silent switch is flipped. I set mine this way after realizing my phone had been silently sitting on my desk during a flash flood warning last summer, and the Silent switch was already in the off position by the time I noticed the notification. By then, the basement was already six inches of water.
Get the Full Details
