Kyle Seyler
November 17, 2025

Table of contents
iOS 18.4's Priority Notifications
How Apple Intelligence Determines Priority
Technical Elements That Improve Notification Priority
Best Practices for iOS Notification Deployment
How Courier Simplifies iOS Notification Management
Other Push Notification Changes to Know
Frequently Asked Questions
Additional Resources
The push notifications landscape shifted dramatically in 2025. Apple Intelligence's Priority Notifications in iOS 18.4 changed how iOS surfaces important alerts, representing the most significant update to mobile push notifications since their introduction.
This guide provides deep technical utility for app developers and product managers navigating iOS 26 notification features. Whether you're managing push notification infrastructure through Courier's unified API or building directly against APNs, you'll find actionable implementation guidance backed by reputable sources.
iOS 18.4 (released March 31, 2025) fundamentally changed how push notifications compete for user attention by introducing Priority Notifications, an Apple Intelligence feature that uses on-device machine learning to automatically determine which alerts deserve prominent placement at the top of the Lock Screen. Here's what makes this different: Apple hasn't exposed the complete algorithm. Much of the prioritization system is black box AI, but over the eight months since the beta launched in February 2025, developers and testers have been systematically recording results to understand what gets prioritized.

According to testing reported by 9to5Mac and iDropNews, the system demonstrates clear preferences. Push notifications from Messages, Mail, and Calendar apps consistently get prioritized over news and entertainment apps.
Key Facts:
Apple hasn't published detailed technical documentation on the exact algorithm, but based on reputable sources and developer observations, here's what we know:
The AI analyzes what's in the notification to determine if it should stand out from the rest, using the same semantic analysis of notification content introduced in Apple Mail with iOS 18.1. In iOS 26, this system continues to perform on-device analysis to understand context and urgency.
The app generating the notification is a big clue. Something from Mail, Messages, or Reminders is far more likely to be a priority than a news headline. Initial tests suggest that Apple Intelligence tends to prioritize notifications from messaging apps or time-sensitive events, such as upcoming deliveries, over other apps such as Gmail or Asana.
Time Sensitive notifications (a feature since iOS 15) still rise to the top. Priority Notifications build on top of existing Time Sensitive notification infrastructure but use AI to fill gaps where developers haven't properly categorized their notifications.
The feature uses on-device machine learning to understand notifications that are most relevant to you, based on their context and your interaction patterns. Over time, the system learns from which notifications you actually engage with.
Based on Apple's developer documentation and implementation guidance, here are the specific technical elements that can improve a notification's chance of being prioritized:
Developers can set ios_interruption_level to "active", "time-sensitive", "passive", or "critical". The Time Sensitive level is key:
Implementation:
Copied!
{"aps": {"alert": {"title": "Your driver is arriving","body": "2 minutes away"},"interruption-level": "time-sensitive"}}
Time Sensitive notifications will still rise to the top, and Priority Notifications fill in a gap where developers haven't properly implemented Time Sensitive classification. This means properly implementing Time Sensitive for genuinely urgent notifications gives you the best chance of priority status.
Setup Requirements:
From iOS 15, Apple introduced the relevance-score field for iOS push notification payloads, designed to be used with Notification Summary to help the device determine the relative importance of notifications.
Implementation:
Copied!
{"aps": {"alert": {...},"relevance-score": 0.8}}
ios_relevance_score: Optional numeric value from 0 to 1 to indicate importance for delivery ordering. While this primarily affects Notification Summary, it may provide signals to Priority Notifications AI about importance.
For messaging, calling, or user-to-user communication apps, implementing Communication Notifications gives special priority treatment:
Why It Matters: Siri provides shortcuts and suggestions based on communication intents, and will suggest relevant people to break through in the Focus configuration, including those people associated with communications in your app. Communication notifications will feature the image or avatar of the contact they were sent from and can integrate with SiriKit so that Siri can intelligently provide shortcuts and suggestions for communication actions.
Implementation Requirements:
INSendMessageIntent or INStartCallIntent)Copied!
<key>NSUserActivityTypes</key><array><string>INSendMessageIntent</string></array>
This is only appropriate for genuine person-to-person communication, not marketing messages or transactional notifications.
Apple's AI has undocumented safeguards in place to prevent abuse, and the only way apps can try to circumvent the OS is by making their content look urgent.
Based on testing reports:
Your app's category in the App Store and its general function matters. A productivity or communication app will have better odds than an entertainment app.
While Apple hasn't documented the exact content analysis, these elements appear to matter:
Title and Body Structure:
Examples of likely prioritized content:
Examples of likely deprioritized content:
Do NOT abuse these systems:
Priority Notifications functionality introduced in iOS 18.4 remains consistent through iOS 26. These best practices apply to all current iOS versions.
Critical/Time Sensitive:
Active (default):
Passive:
Build trust by accurately representing the urgency of each notification. People have several ways to adjust how they receive notifications from your app, including turning off all notifications, so it's essential to be as realistic as possible when assigning an interruption level.
Good Examples:
Bad Examples:
Priority Notifications AI is designed to identify genuinely urgent content. The best technical strategy is to properly classify your notifications using existing iOS features (Time Sensitive, Communication Notifications) and write notification copy that accurately reflects the urgency of the content.
Courier abstracts the complexity of managing notification infrastructure across APNs and other platforms. Here's how Courier helps:

Unified API for All Platforms:
Example Courier Implementation:
Copied!
{"message": {"to": {"user_id": "user_123"},"content": {"title": "Your driver is arriving","body": "2 minutes away"},"routing": {"method": "single","channels": ["push"]},"providers": {"apn": {"override": {"body": {"aps": {"interruption-level": "time-sensitive"}}}}}}}
Brought significant notification changes after Apple Intelligence summaries caused issues with news headlines:
Current Status (iOS 26): These features remain active in iOS 26, with Apple Intelligence continuing to refine notification summaries and priority detection through on-device learning.
APNs updated server certificates in sandbox on January 20, 2025, and in production on February 24, 2025. The new server certificate uses the USERTrust RSA Certification Authority (SHA-2 Root). Most notification providers (including Courier, OneSignal, Firebase) handled this automatically, but teams with custom APNs implementations needed to update their server trust stores.
Twilio Notify will end of life on December 31, 2025. After this date, the Notify API will cease to function entirely. Twilio itself chose Courier for their own multichannel orchestration needs when they needed to replace Notify's capabilities internally.
Legacy Firebase Cloud Messaging APIs were terminated effective June 20, 2024. Anyone still on the legacy API needs to migrate to FCM HTTP v1. FCM HTTP v1 API has a rate limit of 600,000 requests per minute by default.
A: Courier makes this simple through provider overrides. Use the providers.apn.override parameter in your API call to set the interruption level. Courier's APNs integration handles all the complexity of certificate management and delivery tracking, so you can focus on crafting the right message.
A: With Courier's smart routing, failed push notifications can automatically escalate to SMS or email based on your configuration. This ensures critical notifications reach users even if their device is offline or push is disabled. Set up multi-channel routing to never miss an important alert.
A: Not with Courier. Create a single notification template, and Courier automatically formats it correctly for each platform. iOS 26-specific features like Time Sensitive notifications are configured through provider overrides, keeping your templates clean and maintainable.
A: Courier's analytics dashboard tracks delivery, open rates, and engagement metrics across all channels. This helps you understand which notifications drive action and which ones users ignore, so you can refine your urgency classification and improve Priority Notification selection rates.
A: Courier provides built-in preference management so users can control which notification types they receive on which channels. This respects user choice while ensuring critical notifications (like security alerts) still get through. Learn about preference management.
A: While the SiriKit implementation happens in your iOS app (compatible with iOS 15 through iOS 26), Courier handles the notification delivery side seamlessly. Once you've configured Communication Notifications in your app, use Courier's provider overrides to send the properly formatted payloads that iOS expects.
A: Courier provides a complete migration path with the same multichannel capabilities Twilio chose for their own internal operations. Start your migration here with free tier access that includes 10,000 notifications per month.
Get started with Courier:

Introducing Courier Skills: Teaching Your AI IDE to Build Notifications Correctly
AI IDEs are great at generating plausible code, but they lack durable domain context. Courier Skills gives your AI a shared baseline for building production-ready notifications, with opinionated guidance on channels, patterns, and constraints that matter in real systems.
By Thomas Schiavone
January 30, 2026

Customer Engagement Orchestration: How to Unify New Messaging Channels in One Platform
Customer engagement orchestration lets you manage notifications across WhatsApp, Slack, Teams, in-app inboxes, and SMS through a single API instead of maintaining separate integrations. This guide covers why B2B companies are moving to orchestration platforms, compares modern messaging channels (including Stream Chat for marketplaces), and explains how to evaluate solutions. Includes channel comparison table and guidance on when orchestration infrastructure makes sense versus building your own.
By Kyle Seyler
January 27, 2026

The Notification Platform Developers Choose
Most notification platforms built dashboards first and added developer tools later. Courier did the opposite. With a CLI that handles real workflows, MCP integration with setup management, typed SDKs in seven languages, and SOC 2 Type 2 certification, Courier is built for teams that ship. This isn't marketing copy: Twilio chose Courier to unify notifications across their 10M+ developer platform. LaunchDarkly uses Courier to power feature release workflows. When the companies that build developer infrastructure choose your notification platform, that says something about the technical foundation.
By Kyle Seyler
January 26, 2026
© 2026 Courier. All rights reserved.