Bold claim: Google Fi is reshaping how you use web-based calls and messages, and the change is bigger than it appears. Here’s a clear, beginner-friendly rewrite of how the new Web Calls and RCS system from Google Fi works, what’s changed, and what you should expect as it rolls out.
Google Fi’s latest update shifts calling and voicemail onto a dedicated web page while moving RCS messaging handling to Google Messages for web. In October, Google Fi announced it would “update web calls and messages,” which is now realized through a new Fi web page and an updated Messages for web integration.
Previously, Fi users who wanted to access texts, calls, and voicemails from a computer or tablet lacked full RCS support. You could make calls, send texts, and check voicemail from web interfaces, but RCS features weren’t available in that setup, as they relied on the older web experience.
The new system introduces a separate fi.google.com/webcalls portal for calling and voicemail, while RCS-empowered texting continues to ride on the existing Messages for web experience. The two pieces are connected but live in different places: web calls exist on fi.google.com/webcalls, and texting remains at messages.google.com/web. This setup is currently Android-only and does not extend to iOS.
In practice, this means you’ll find two main web surfaces for Fi usage:
- Web Calls: a page to initiate phone calls and access voicemail on devices signed into your Google Account (tablets and laptops included). It also provides web notifications for incoming calls and new voicemails.
- Messages for web: the central hub for texting, including RCS conversations, which brings richer media and features to web-based messaging.
Google describes the experience as tightly linked: web calls synchronize with your Messages for web, so you can seamlessly pick up conversations back in text as you continue them on the web. Crucially, even when the physical phone is offline, you can still make and receive calls through the web page while signed in.
What to know about the nuances (as documented by Google Fi):
- Deleting a call from web history does not sync that deletion across other devices.
- Deleting a voicemail from web removes it from all synced devices.
- The web interface does not support bulk deletion of calls or voicemails.
- If Google Fi was activated recently on your Android device, there may be a 24-hour delay before web calls activation works.
Enabling RCS requires a separate, user-initiated process within the Fi setup. Specifically, you must stop Google Fi sync first, then toggle RCS on within Google Messages settings:
1) Open Google Messages on your device.
2) Tap your profile picture or initials in the top-right, then go to Messages settings.
3) Choose Advanced, then Google Fi Wireless settings, and Sign in to your Google Fi account.
4) Select your Fi account.
5) In the RCS prompt, choose Turn off.
6) Tap Sync conversations.
7) At the bottom, select Stop sync & sign out.
8) Confirm Stop syncing when prompted.
A few practical takeaways:
- The separation of web calls and web text creates a two-portal workflow. You’ll switch between fi.google.com/webcalls for calls/voicemail and messages.google.com/web for text conversations. Expect a familiar design language across both interfaces, with notifications for calls and voicemails on the web.
- RCS on web remains tied to your Messages on the web experience, so richer media and features are accessible there, even as calls and voicemails live on a dedicated web page.
- If you rely on RCS for enhanced chats, ensure you follow the sign-in and stop-sync steps to enable it within Fi.
If you’re evaluating whether to adopt the new web calling experience, consider your devices, your workflow (do you mostly text or also need robust voice features on a computer?), and whether you use iOS or Android. For Fi users on Android who frequently switch between devices, this update can streamline cross-device conversations, though it introduces a bit more navigation across two web surfaces.
What’s your take on the split between web calls and web messaging? Do you prefer a single unified web interface, or is a two-panel approach easier to manage across devices? Share your experience and opinions in the comments.
