What you need to know
- Google is removing the ability to make "Google-supported calls" on smart speakers and displays in the UK.
- The change kicks in from sometime in mid-December.
- You'll still be able to make Duo calls on compatible devices.
Google is removing a niche feature on the Nest Audio and other Assistant-enabled smart home devices, the ability to make calls to mobile phone numbers for free. Well, mostly.
You see, currently, Google will let you make voice or video calls with a smart speaker or a smart display if you've got Duo, that part's staying. It also lets you pair your smart speakers to Google Fi, Google Voice, or select carriers in the U.S. and Canada to make calls through your account. That part's also staying. In the U.S, UK, and Canada, it offered the ability to make intra-regional phone calls for free.You could choose to display your phone number if you want to, but it was routed through an anonymous number so you didn't have to. Hence the term "Google-supported." That last one's the bit that going, in the UK at least.
The feature was likely used too little for Google to justify supporting it in the UK, with the country preferring to use VoIP services like WhatsApp or Facetime over traditional phone calls.
A sleek successor to a much loved device, the new Nest Audio brings better sound and more color than the Nest Mini.
I find this a bit frustrating as i’ve recommended the google nest hub max to my parents and some of their friends. They found it useful as while they can use their mobile phones, they werent particularly adept, and using the nest hub max was a no-hassle way of calling shops (and their friends who dont typically use duo) and having the call on speakerphone. I personally still love using my google nest hub max as for me its great, but i won’t be recommending it to others as its hard to know what functionality google will remove next.
Get the best of Android Central in in your inbox, every day!
Thank you for signing up to Android Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.