BestMVNO may earn a commission if you click on a link leading to another website. Learn More

Signing up for Google’s Project Fi will Severely Hinder the Functionality of Google Voice

Google Project Fi Logo

By


Do something awesome, share this post with a friend on:



 

Project Fi LogoInvitations for Google's Project Fi wireless service have started going out to some of the people that have requested one.  With the invitations have come a few unpleasant surprises.

The first unpleasant surprise has to do with porting over Google Voice numbers.  If you already have a Google Voice number, Project Fi will give you two options, one is to use your Google Voice number with Fi, and the other is to get new number which will result in you actually losing your Google Voice number.  This is a rather odd decision by Google although perhaps there are some technical issues associated with being able to get a new number while retaining your Voice number.  On the other hand, Google has always prohibited users from having two Google Voice numbers forward to the same phone, so this may be an extension of that policy.

Be informed of the latest deals, plans and promotions from T-Mobile and every one of its MVNO's when you subscribe to the T-Mobile weekly newsletter. No spam and you can unsubscribe at any time!  

If you do choose to port your Google Voice number you'll lose Google Voice legacy (not Hangouts) app functionality and you'll no longer be able to send or receive calls through those apps.  Much of Google Voices functionality such as call forwarding, blocking, and voicemail transcriptions will move over to Fi.  This also means you'll lose support for devices like Obihai which allow you to have a home phone through VoIP.

So what do you think about the changes Google is making in terms of Google Voice and Project Fi?  Will they hold you back from switching over to the new MVNO service?





Category  Google Fi
Tagged  Wi-Fi Calling

Leave A Comment

Do something awesome for BestMVNO, and share with a friend on:


guest
0 Comments
Inline Feedbacks
View all comments