VoIP push for iOS

Ring the call, even when the app is closed

Make an iPhone ring with a real incoming call, even when your app is fully closed. Pushwoosh delivers the native iOS VoIP push that does it, over PushKit and CallKit.

Book a demo Start for free

iPhone showing the native iOS full-screen incoming call from a doctor, with the caller photo, the caller name, and decline and accept buttons, while the app behind it is closed

Trusted by 80,000+ companies to scale their engagement

How it works

Side-by-side comparison: on the left a closed app with a silent, undelivered alert; on the right the same app woken by a VoIP push, showing a full-screen incoming call ringing

When a user swipes your app away, a standard APNs alert cannot reliably wake it. For a calling app, that means the call never rings.

Apple’s PushKit VoIP push is a separate, highest-priority transport. It wakes even a terminated app and shows the native call screen at once.

Good to know: Apple’s PushKit rules. The SDK keeps you inside them.

iOS only. There is no Android PushKit equivalent.
Every VoIP push must report a call to CallKit at once, or iOS revokes the token.
PushKit is for calls only. App Review rejects other uses.
Mainland China bans CallKit, so calling apps fall back there.

An SDK module instead of a DIY PushKit build

The PushwooshVoIP module registers the PushKit VoIP token and wires CallKit for you, with a ready-made call delegate.

Registers the PKPushRegistry VoIP token for your app’s VoIP configuration.
Reports every incoming call to CallKit, so the native screen appears.
PWVoIPCallDelegate callbacks for incoming, answered, ended, started, and failed calls.
Configurable ringtone and CallKit handle types — generic, phone, or email.
Wakes the app in the background to run your code, or to schedule a missed-call notification.

PWVoIPCallDelegate callbacks

voipDidReceiveIncomingCall
answerCall
endCall
startCall
mutedCall
heldCall
voipDidFailToReportIncomingCall

Journey diagram: an incoming call on your backend triggers a VoIP push over PushKit, the SDK reports the call to CallKit, and the app answers

Pushwoosh sends the push, your backend runs the call

Pushwoosh sends the VoIP push and hands your app the incoming, answered, and ended events.

Your backend triggers a VoIP push through the Messages API on an incoming call.
The SDK reports it to CallKit and surfaces the answer and end actions.
You bridge those actions to your existing call stack.

Pushwoosh carries the push, not the media. The audio and video stay on your own WebRTC or SIP path.

See how it works

Same iOS SDK as the rest of Pushwoosh

VoIP push sits in the same iOS SDK and registration model as mobile push, in-app, email, SMS, and WhatsApp. Ship call delivery and your engagement messaging from a single integration.

VoIP simply runs at a different transport priority: one SDK, one customer profile.

Built for apps where a real call has to connect

Telehealth

The doctor starts a consult and the patient's phone rings, app closed.

Marketplaces

Connect buyer and seller without exposing a phone number.

Telecom & OTT

Your own calling app delivers the inbound call.

Fintech

Advisor callbacks, video KYC, and fraud-agent verification.

Insurance

An adjuster rings the policyholder to inspect a claim live.

Tutoring & coaching

Ring the student or member into a 1:1 session.

EU hosting for regulated calling apps

Your tokens, triggers, and profiles sit on Pushwoosh hardware, with EU data in Germany under GDPR and BDSG (ISO 27001:2022, HIPAA, SOC 2 Type 1, EU-U.S. DPF). The push travels via Apple, the call via your backend.

Send opaque call IDs, never PII. Payloads are stored by Apple and visible to MDM, so keep names, phone numbers, and case details out of the VoIP push. Resolve the caller inside your app once the call is reported.

Set it up in three steps

Add the module

Add PushwooshVoIP via SPM or CocoaPods, turn on the Voice over IP background mode, and initialize.
Upload your VoIP certificate

In Settings, Configure platforms, connect iOS and select VoIP push notifications, then upload your VoIP Services certificate as a .p12 file on the Production gateway.
Receive and report the call

On an incoming call, your backend sends a VoIP push through the Messages API. The SDK reports it to CallKit and surfaces the call events to your app.

Read the docs

Add native call delivery to your iOS app

Talk to our team about VoIP push for telehealth and regulated calling, or start building on your own.

Book a free demo Start for free

Explore related products

Mobile Push Notifications

Mobile push notifications by Pushwoosh — every-device reach, rich content, precise targeting, cross-channel Journeys and 99% uptime. Turn notifications into loyal, paying users.

High-Speed Push Notifications

From sports updates to breaking news to weather alerts and travel updates, seconds can make a huge difference. Our powerful High-Speed Delivery technology allows sending up to 500,000 push notifications per second!

Pushwoosh API

Offload your app and web messaging to Pushwoosh API. We manage push, email, SMS, and data streams — you build successful products without limits.

In-App Messaging

In-app messaging by Pushwoosh — onboard, upsell, announce and collect feedback right when app users are paying attention. No-code editor, native SDK layouts, per-element analytics. Free to start.

Message Inbox for mobile and web

Message Inbox adds an in-app notification center to your app and website. Silent delivery reaches every user, including the ones who declined push, and saved messages stay available on their own time.

Your data is safe with Pushwoosh

Your data is safe with Pushwoosh. Pushwoosh meets industry standards for online security and is certified by ISO 27001:2022.