SCA Caller ID Modes
SCA supports different caller identification technologies on iOS and Android. Depending on the selected mode, contacts remain private within SCA or can optionally be shared with the operating system to enable additional integrations such as Siri, CarPlay, Android Auto, or native contact search.
iOS Caller ID Modes:
1. Call Directory Extension (Default)
The Call Directory Extension is the recommended and default caller identification mode on iOS.
Characteristics
Contacts remain private and are not added to the iOS Contacts app.
Other apps cannot access or view these contacts.
Only iOS itself can use the contact information to resolve incoming phone numbers.
Provides caller identification during incoming calls.
Highest level of privacy.
Limitations
Contacts are not available in Siri.
Contacts are not available in Apple CarPlay.
Contacts cannot be searched from the native iOS Contacts app.
Third-party apps cannot access these contacts.
2. Contact Provider Extension ("Share Contacts with iOS") (Optional)
This optional mode allows SCA contacts to be exposed to the iOS Contacts Framework.
Characteristics
SCA contacts become available to the iOS operating system.
Supports Siri contact search and voice commands.
Supports Apple CarPlay.
Contacts remain read-only.
Contacts remain managed by SCA.
If SCA is removed, the shared contacts are automatically removed.
Privacy Considerations
The contacts become available through the iOS Contacts Framework.
Depending on the device configuration, other apps may be able to access these contacts.
On managed devices, administrators can use App Protection Policies and device management policies to restrict access to managed contacts and limit visibility to other managed applications only.
Recommended Use Cases
Siri integration required
Apple CarPlay support required
Native iOS contact search required
More about "Share Contacts with iOS" (CPE) and how to activate it see here.
Android Caller ID Modes:
1. Contact Directory Service (Default)
This is the recommended and default caller identification mode on Android.
Characteristics
Contacts remain private and are not synchronized to the Android contacts database.
Other apps cannot access these contacts.
Only Android itself can use the contact information to identify incoming calls.
Provides caller identification during incoming calls.
Highest level of privacy.
Limitations
Contacts are not visible in the Contacts app.
Android Auto integration is not available.
Contacts cannot be searched from the native Contacts app.
Other apps cannot access these contacts.
Note: SCA automatically selects the most appropriate Android caller identification mode based on the device management scenario and platform capabilities.
2. Sync Contacts to Android Contacts (Optional)
This mode allows SCA contacts to be synchronized to the Android contacts database.
The exact behavior depends on the device management model.
Work Profile Devices
On Android Enterprise Work Profile devices, contacts are synchronized into the work profile only.
Characteristics
Contacts are visible within the work profile.
Business apps inside the work profile can access these contacts according to Android policies.
Limited Android Auto support ⚠️
Supports native contact search within the work profile.
Contacts remain read-only and managed by SCA.
Contacts are automatically removed when SCA is uninstalled.
Privacy Considerations
Contacts remain isolated from the user's personal profile.
The work and personal profiles are separated by Android Enterprise.
Access to the contacts can be controlled through enterprise device management policies.
Note: On Android Enterprise Work Profile devices, SCA must be installed in the Work Profile. SCA automatically synchronizes contacts to the Work Profile contacts database. Contacts remain isolated from the user's personal profile.
Note: Android Auto may not be able to access contacts stored exclusively in the Android Work Profile. Caller identification may still work, while contact search and contact browsing remain unavailable.
Fully Managed Devices
On fully managed Android Enterprise devices (single profile), organizations have administrative control over the entire device. In these deployments, synchronizing contacts to the native Android Contacts app is typically considered acceptable, as the device operates entirely within a corporate-managed environment.
Characteristics
Native Contacts app integration.
Android Auto support.
Native contact search support.
Contact visibility controlled by device management policies.
The organization determines which applications are installed and allowed to access contact information.
Contacts remain read-only and managed by SCA.
Contacts are automatically removed when SCA is uninstalled.
Privacy Considerations
The entire device is under organizational management.
Access to business contacts is governed by corporate security and compliance policies.
This mode is commonly used when seamless integration with native Android functionality is preferred over strict contact isolation.
Recommended Use Cases
Android Auto required
Native Android Contacts integration required
Native contact search required
Fully managed Android Enterprise devices
Work Profile deployments requiring Android contacts integration
Note: If SCA is installed on a fully managed Android Enterprise device (single-profile deployment), contacts are not synchronized automatically. Native Contacts app integration requires enabling Sync Contacts to Android Contacts explicitly by setting ForceSync2LocalContacts_Option = true.
3. Compatibility Mode
Some device manufacturers provide heavily customized Android versions and dialer applications that do not fully support Android's standard Contact Directory Service APIs. Examples may include certain Samsung devices and other vendor-specific Android implementations.
When SCA detects such limitations, it automatically switches to Compatibility Mode to ensure reliable caller identification.
Characteristics
Uses Android
CallScreeningService.Uses an SCA-provided incoming call overlay to display caller information.
Provides caller identification even when the native dialer does not support Android Contact Directory APIs.
Does not require synchronization of contacts to the Android Contacts app.
When Is This Mode Used?
Primarily on unmanaged (Intune MAM-only) devices.
Typically not required on Android Enterprise Work Profile devices.
Typically not required on Fully Managed Android Enterprise devices.
Used only when the standard Android caller identification APIs are unavailable or unreliable on the specific device model.
Typical Use Cases
Samsung devices with dialer compatibility limitations.
Other manufacturer-specific Android variants.
BYOD deployments using Intune MAM without device enrollment.
Note: On some devices using custom dialer apps (e.g. Samsung), installing the Google Phone app from Google Play Store and setting it as the default phone app may allow use of the standard Android Contact Directory Service mode instead of Android Compatibility Mode.
Recommended Configuration
Siri required
Apple CarPlay required
Android Auto required
Work Profile deployment
Fully Managed Android Enterprise
Custom dialer apps not supporting Contact Directory Service (e.g. Samsung) on unmanaged (MAM) devices
Privacy Summary
Default Caller ID Modes
Contacts remain private within SCA.
No contact synchronization to the operating system.
Other apps cannot access contact information.
Provides the highest level of contact isolation.
Contact Sharing Modes
Contacts are exposed to the operating system's contact framework.
Additional integrations become available, including Siri, CarPlay, native contact search, and Android Auto support depending on the Android deployment model.
On managed devices, visibility and access can be restricted through enterprise mobility management policies.
Contacts remain managed by SCA and are automatically removed when SCA is uninstalled.
Recommendation: Use the default Caller ID modes whenever caller identification is the primary requirement. Enable contact sharing modes only when additional platform integrations such as Siri, CarPlay, Android Auto, or native contact search are required.
SCA Desktop (Windows & macOS)
Unlike the mobile versions of SCA, SCA Desktop does not synchronize contacts to the operating system or expose contacts to other applications.
SCA Desktop provides caller identification exclusively for the Microsoft Teams desktop client on Windows and macOS.
Characteristics
Caller identification for incoming calls in Microsoft Teams.
Supports Teams users and PSTN callers when the call is routed through Microsoft Teams (e.g. Teams Phone).
Contacts remain private within SCA Desktop.
Limitations
Caller identification is available only for incoming calls via Microsoft Teams.
Note: Unlike iOS and Android, SCA Desktop does not offer multiple caller identification modes. Contacts always remain within SCA and are never synchronized to the operating system.
Last updated
Was this helpful?