Help Center

Enabling WhatsApp Inbound Calling

Starting with White-Label Mobile App Release 4.18.0, you can enable the WhatsApp Inbound Calling feature for your branded mobile application. This guide walks you through the configuration steps required, primarily for ensuring compatibility with iOS devices.

To support this feature, your existing white-label app must have specific Apple credentials configured: an Apple Team ID and an APNs Key ID. If your app was built before this release, you will likely need to update these settings before publishing a new version.

Who Should Follow These Steps?

This update is necessary for agencies that:

Already have a published White-Label Mobile App.
Want to enable WhatsApp Inbound Calling for their users.
Have not previously configured their Apple Team ID or APNs Key ID in the app's settings.

Step 1: Update Your Apple Team ID

First, you need to provide your Apple Team ID.

In your agency view, navigate to: Mobile app > Customisation > Distribution > Channels > App store settings > App Store Connection.
Locate the Apple Team ID field.
Enter your 10-character alphanumeric Team ID.

Finding Your Apple Team ID:

Sign in to your Apple Developer Account.
Navigate to Certificates, Identifiers & Profiles > Keys.
Your Team ID is displayed in the top-right corner of the page.
Copy this value and paste it into the corresponding field in your CRM.

In the App Store Connection section, ensure the Issuer ID, Key ID, App Store Account Name, and Apple Team ID are all populated. Click Save Details when finished.

Step 2: Verify Your APNs Configuration

Next, confirm your APNs (Apple Push Notification service) settings are correct.

Navigate to: Mobile app > Customisation > Distribution > Channels > App store settings > Setup Firebase.
Verify that the following items are configured:
- Services.json file
- GoogleService-Info.plist file
- APNs Authentication Key (.p8 file)
- APNs Key ID

Finding Your APNs Key ID:

Sign in to your Apple Developer Account.
Go to Certificates, Identifiers & Profiles > Keys.
Select the APNs key associated with your app from the list.
The Key ID is a 10-character alphanumeric value displayed in the KEY ID column.
Copy this ID and paste it into the APNs Key ID field in your CRM.

Note: You do not need to generate a new APNs key if you already have a valid .p8 file uploaded. Simply ensure the Key ID is entered correctly.

Click Save Details after updating the information.

Step 3: Publish Your App Update

After you have entered and saved all the required credentials:

Save all changes in the CRM.
Generate a new build of your mobile app.
Submit this updated version to the Apple App Store for review.
Wait for approval from Apple.

Once the updated app version is approved and available, the WhatsApp Inbound Calling feature will be active for your users.

Verification Checklist

Before submitting your app for review, confirm the following:

✅ Apple Team ID is populated.
✅ APNs Authentication Key (.p8 file) is uploaded.
✅ APNs Key ID is entered.
✅ Firebase configuration files (Services.json and GoogleService-Info.plist) are present.
✅ The app is built using Release 4.18.0 or later.
✅ The updated version has been submitted to Apple.

Frequently Asked Questions

Do I need to create a new APNs (.p8) key?
No. If you already have a valid APNs Authentication Key configured, you can continue using it. You only need to verify that the associated APNs Key ID is correctly entered.

What if I don't know my APNs Key ID?
You can find it in your Apple Developer Account under Certificates, Identifiers & Profiles > Keys. The Key ID is displayed next to your APNs key.

Do I need to create a new white-label app?
No. You only need to update the configuration for your existing app and submit a new version to the App Store.

Will users need to reinstall the app?
No. Existing users simply need to update to the latest version of the app from the App Store.

What happens if I don't update these settings?
WhatsApp Inbound Calling may not work correctly on iOS devices until the required Apple credentials are properly configured.