A recurring question in parent forums points to a real mismatch: families troubleshooting a Google Family Link outgoing calls bug often discover the problem has nothing to do with Family Link. Google's published documentation is unambiguous on two points that together explain most of these cases. The question is knowing which layer to look at first.
This matters most for families running a child's Android device through Family Link on a Google Fi plan. Both products touch call and contact management, but at entirely different levels, and the overlap between them is easy to misread when something breaks.
What Google Fi's contact filter actually does and doesn't do
Google Fi offers a family setting called "Only allow calls and texts from phone contacts." The name suggests a general call blocker. It isn't, at least not in the outbound direction.
Under this setting, only numbers already in the child's contacts can reach them by call or text, per Google Fi's family settings documentation. Calls from unknown numbers go straight to voicemail; unrecognized texts are blocked. The child's outbound calls are deliberately left untouched. Plan members can still call or text anyone they want, and any number they contact can call or text them back for up to 30 days, according to the same documentation. The filter is inbound-only by design.
One practical detail that breaks the feature quietly: contact syncing must be active for it to work. Without a synced contact list, the filter has no data to check against, per the same Google Fi documentation. If the setting is on and behaving unexpectedly, confirming sync status in the child's account settings is the first thing to verify.
Google Fi also maintains a blocked-contacts log. Parents can review the number of attempted contacts blocked over the previous 60 days, per Google Fi Help. That data can distinguish between a filter working as intended and one blocking contacts it shouldn't.
Why Family Link blocking outgoing calls isn't something the controls can do
Family Link gives parents meaningful tools: app access controls, screen time limits, content filters, and download approval. What it generally cannot do is set app time limits on system apps like the Phone app. Google Play Help notes that some system apps can't be limited or blocked because they're required for device operation or supervision. A parent who suspects they accidentally disabled calling through Family Link almost certainly did not. The interface doesn't provide a mechanism to do that.
There is one exception that catches families off guard. During downtime, "always allowed" apps remain accessible, but not when a parent manually taps "Lock" in the Family Link app. A manual device lock can make core apps like the Phone app temporarily inaccessible. The gap between "I didn't block calling" and "the phone still won't call" is real, and a manual device lock is where it lives.
Google Fi's family settings and Family Link are also independent control systems. The contact filter, data limits, and call restrictions are configured through the Fi app and operate at the network level. Family Link's controls sit at the device level. The two systems operate independently, with settings managed separately in each app.
Narrowing down the Google Family Link call issue: four checks in order
Google's documentation points to a short list of causes. Running through them in order takes less than ten minutes, and either resolves the problem or narrows it to something worth escalating.
Is the device locked or in downtime? Open the Family Link app and check the child's current device status. A manual lock or active downtime window can leave the Phone app inaccessible regardless of any call-specific settings. Lift the restriction and allow a short delay for the change to reach the device. Changes apply once the device connects to the internet if it's currently offline.
Do all outgoing calls fail, or only specific numbers? This question separates two different problems. If the child cannot call anyone, the cause is most likely device-level: a lock, active downtime, or a system fault. If specific numbers fail and others go through on a Google Fi device, the contact filter is worth examining even though it isn't supposed to affect outbound calls. Confirming it's correctly configured and that contact syncing is active rules it out cleanly.
Contact filter configuration on Google Fi. If the filter is on, verify that contact syncing is also active. If a particular number is consistently failing and isn't saved in contacts, adding it is the fastest short-term fix. One documented override is worth noting: after a child dials 911, the contact-only inbound filter automatically disables for 48 hours to allow callbacks from emergency responders, per Google Fi Help. The setting has exception logic built in, which confirms it's more nuanced than a simple toggle.
Can the child receive calls from known contacts? If incoming calls from contacts also fail, the problem has moved outside Family Link and Google Fi family settings entirely. That points toward a carrier or network fault. Restart the device, verify network connectivity, and contact Google Fi support directly.
What Family Link's contact controls actually cover
Through Family Link, parents can block specific individuals on Google Meet, Gmail, and Google Chat, per Google's family contact guidance. These are app-level blocks within those services only. None of them touch the Phone app or carrier calling.
Family Link also lets parents block Play Store apps, restrict Chrome browsing, and require approval for new downloads. Meaningful controls, but they operate within defined boundaries. The dialer sits outside those boundaries by design, both because it's a system app and because cutting off a child's ability to place calls would create real safety risks.
When the issue becomes worth reporting
If the device isn't locked, downtime isn't active, the contact filter is correctly configured or off, contact syncing is on, and outgoing calls still fail consistently across multiple numbers, Google's published help pages don't account for that combination. That's where reported behavior and documented behavior diverge, though the sources reviewed here don't confirm whether this reflects a known bug.
Google has not publicly identified a Family Link bug related to outgoing call blocking. No official documentation reviewed here identifies a known Family Link bug related to outgoing call blocking.
Two reporting paths exist for families who've cleared every documented check. Feedback submitted through the Family Link app (Account icon, then "Send feedback") goes directly to the product team. If the issue appears carrier-related, the Google Fi app has a parallel feedback channel. Posting in the Android Community support forum, where parents flagged separate unexpected Family Link device-control behavior in June 2025, can help establish whether others are hitting the same problem under the same conditions.
Specificity is what moves a report forward. Device model, Android version, Family Link app version, Google Fi plan type, and a precise description of which calls fail and which succeed give the product team something reproducible to work with.
Google's documentation covers the expected behavior thoroughly. What it doesn't cover is every way the expected behavior can break, which is why families working through this issue are largely on their own.
Comments
Be the first, drop a comment!