NSE Filtering for encrypted incoming calls: what technical details should we provide?

We’re preparing the first iOS release of ANTINTWRK, an encrypted messenger with voice and video calls. Our push gateway sends a regular APNs alert for the encrypted event. On the receiving device, the Notification Service Extension fetches and decrypts the referenced event. In this delivery path, the gateway does not distinguish an encrypted call invitation from a message. When the extension identifies a ringing call, it uses CXProvider.reportNewIncomingVoIPPushPayload to hand it off to CallKit and suppresses the original alert to avoid a duplicate notification.

Our Notification (NSE) Filtering request, submitted on October 25, 2026, still shows Submitted. Xcode cannot export the App Store build because the extension’s distribution profile lacks com.apple.developer.usernotifications.filtering. We have contacted Developer Support under Entitlements.

We’re following Apple’s Sending End-to-End Encrypted VoIP Calls guidance. For this design, what technical details or test evidence should we provide so the capability review team can evaluate the request? Is there a recommended way to attach that material to the existing request? We can provide the request and support case IDs privately if needed.