Google Opens the Dialer to Third‑Party Calling Apps
Google is rolling out a significant Android dialer integration that finally connects third-party calling apps with the native phone experience. Through new APIs built on Android’s telecom framework and the Jetpack Telecom library, developers of VoIP services such as WhatsApp, Telegram, Messenger, and other third-party calling apps can now register their internet calls directly with system dialers like the Google Phone app. Once implemented, these VoIP calls will appear in the same call history as regular cellular calls, instead of being siloed inside each messaging app. This change targets devices running Android 16.1 and above, where a new Calling accounts section in the Phone by Google settings allows users to control which apps can surface their logs. The result is a more unified, native-level experience for anyone who relies heavily on VoIP calling instead of traditional voice minutes.
Unified VoIP Call History Inside the Google Phone App
For users, the biggest benefit of the new Android dialer integration is a unified VoIP call history. Previously, missed internet calls were easy to overlook because WhatsApp call history, Telegram logs, and other VoIP entries were trapped inside their respective apps. You had to remember which service a contact used, open that app, and then hunt through its call list to return a missed call. With integrated call logging, system dialers can now display VoIP call history right alongside standard cellular entries. Tapping a recent VoIP call in the Google Phone app will automatically route the callback through the correct internet calling service, without manual app switching. This reduces friction, saves time, and makes third-party calling apps feel like first-class citizens inside Android’s core communication interface.
How the New Calling Accounts Controls Work
Google is giving users granular control over this new behavior through a revamped Calling accounts interface in the Phone by Google app. On supported devices, this settings page lists third-party calling apps that have opted into the integration and are capable of sharing VoIP call history. Users can toggle visibility on a per-app basis, deciding which services should appear in the main call log and which should remain separate. Behind the scenes, VoIP apps register calls with Android’s telecom framework so they can be treated like regular phone events by the native dialer. When you tap a callback entry in the call log, Android hands the action back to the appropriate VoIP app, preserving its own calling interface while keeping discovery and history inside the system dialer for convenience.
Privacy Controls: Call Log Exclusion for Sensitive VoIP Calls
Alongside unified VoIP call history, Google is adding privacy-focused tools to keep sensitive calls out of the system log. Jetpack Telecom’s updated APIs support a call log exclusion flag that lets third-party calling apps mark specific calls so they do not appear in the native dialer’s history. When enabled, these calls stay completely invisible to the system log and the Google Phone app, even though other VoIP calls from the same service may still appear. This capability builds on earlier Android 16 QPR2 work that allowed internet calls to be hidden but was not widely adopted until now. With official support and documentation, VoIP developers can selectively hide business calls, test traffic, or private conversations while still offering unified, convenient logging for everyday communication.
Bringing Android Closer to iPhone’s Unified Calling Experience
This dialer upgrade brings Android closer to the seamless calling experience long offered elsewhere through unified call history frameworks. Until now, Android users have juggled fragmented histories: cellular calls in the Google Phone app, separate WhatsApp call history, Telegram logs, and other third-party lists. The new integration reduces that fragmentation by making the system dialer a single pane of glass for all voice activity, whether over the network or the internet. While third-party apps still need to adopt the APIs before users see changes, early testing on devices like the Pixel 9 running Android Canary builds shows the model in action. As major VoIP apps roll out support, Android users can expect fewer missed callbacks, less app-switching, and a calling experience that feels coherent across every service they use daily.