Restrict Incoming/Outgoing Calls not enforced on Android 10+: feature limited to Android 9 and below

Android

When you apply a Blueprint with call restrictions enabled, devices running Android 10 or higher do not enforce the policy and calls proceed as normal.

Why this happens

Google removed the telephony APIs that device management platforms use to block calls, starting with Android 10. Because Esper's call restriction feature depends on those platform-level APIs, it cannot enforce incoming or outgoing call restrictions on Android 10 or higher — regardless of device manufacturer or Esper Agent version. This is an Android OS limitation, not a misconfiguration.

Step 1: Confirm your device's Android version

1. Open the Esper Console and go to Devices & Groups.
2. Select the affected device by name.
3. Open the Device Info tab.
4. Check the OS Version field.

Step 2: Follow the path for your Android version

Android 9 or below — feature is supported

1. Go to Devices & Groups → [Device Name] → Blueprints and confirm that a blueprint containing call restriction settings has been applied to the device.
2. Check the Blueprint sync status on the device tile — it must show In Sync for the policy to be active. A Pending or Out of Sync status means the policy has not yet applied.
3. Go to Esper Software Updates and confirm the Esper Agent is on the latest available version, as older Agent versions may not enforce call restrictions correctly.
4. Test the restriction by attempting an outgoing or incoming call on the managed device.

Verify: The call should be blocked immediately in line with your policy. If the sync status shows In Sync and the Agent is up to date, restrictions should be active within a few minutes of blueprint application.

Android 10 or higher — feature is not supported

There is no workaround within Esper for standard Android or AOSP builds. The call restriction feature cannot be used on these devices and no configuration change will restore it.

Samsung devices only: Samsung's proprietary Knox APIs may provide call restriction capabilities on Android 10 and higher for certain Samsung models. This is separate from Esper's built-in call restriction feature. Check your device documentation or contact Samsung to confirm whether Knox-based call restriction is available for your specific model.

If this doesn't resolve it

If your device runs Android 9 or below and call restrictions are still not being enforced after confirming Blueprint sync status and Agent version, contact Esper Support. Include the following when you reach out:

• Device model and Android OS version
• Esper Agent version (visible under Device Info)
• Screenshot of the Blueprint sync status
• Description of the call restriction policy you applied and the behavior you observed

Still need help?

If you're unable to restrict incoming or outgoing calls on devices running Android 10 or higher, please submit a support ticket and include your device's Android version and the specific call restriction policy you attempted to apply.