Porting: Google Voice number to RingCentral?

  • 1
  • 1
  • Question
  • Updated 4 years ago
  • Answered
  • (Edited)
Porting: Google Voice number to RingCentral - a three ring circus

I have attempted to port my Google Voice number out to RingCentral (USA) 3 times. 

The first time (7June) RingCentral informed me that there was a "Freeze" on the account probably because it was locked. (Not so, I paid for unlocking the phone number hours before submitting the porting request one week earlier).

The second time (14June) RingCentral informed me that the "Information you provided does not match the information on file with your current service provider". (I provided the info exactly as advised by the Google Voice forum.)

The third time (20June) RingCentral informed me that it "could not be completed because the account with BANDWIDTH.COM:979E - NSR/1 has been INACTIVE or CANCELLED even though your line is still working."  (Seriously? What the hell does that mean?)

RingCentral points the finger at Google telling me to "call them" and ask for help. RingCentral reps in the transfer department have no clue that there is no telephone answering customer service staff at Google Voice.

A call to Bandwidth.com's support center (Bandwidth.com/contact) gets a pleasant & willing-to-help (but other wise an unable-to-make-anything-happen) response. They confirm being Google's provider of numbers and bulk phone lines but they only act as the 'non intervening' middle man who receives the porting requests and hands them over to Google (and then passes along the response without alteration).

So, has anyone had success in porting a Google Voice number to RingCentral?

(I see that Allan Thygesen, VP of Global Sales and Operations for Google now sits on RingCentral's Board of Directors - so if they can make the high level connection, how about making a connection at the ground level?!?)
Photo of Nest Rebuilders, Inc.

Nest Rebuilders, Inc.

  • 70 Points
  • Frustrated

Posted 4 years ago

  • 1
  • 1
Photo of Danno

Danno, Champion

  • 29,612 Points 20k badge 2x thumb
I've ported three GV#s this year - all without a hitch.  Porting can be tricky.  Just keep in mind 'usually' any rejects come from the "port from" carrier.  In any case, just wanted to let you know porting GV#s to RC is a reality.
Photo of Matt Cillo

Matt Cillo, Number Transfer Specialist

  • 120 Points 100 badge 2x thumb

I understand that the porting process can be frustrating, and unfortunately it does not always go as smoothly as we would like.

In case you have not seen it, Google does provide instructions on the port out process on their site.

Addressing the issues that you have been having with porting from Google:

After paying the unlock fee to Google Voice, it actually takes a full 24 hours for the unlock to completely process.  I am not sure why Google does not make this more clear as if you submit your request before that it will still be rejected.

For the second submission, did you enter the number you were porting as the Account Number and your Google Voicemail PIN in the PIN/Passcode field?  If not, that is probably what caused the issue.

As for the most recent, I couldn't find any information about Google automatically closing an account once the number has been unlocked, so I am not sure what is going on there.  It is true that Google does not provide phone support (which makes an issue like this more difficult than it should be), but a quick search here seems to provide a lot of useful information.

If you can't find an answer there, you can start a new topic and a Google representative should be able to quickly assist you.  I'm not sure from your response but if you can't actually log into your Google Voice account, please fill out this form.

Unfortunately since these are account related issues on Google's side, there is nothing we can do on our side until this is resolved.  Once Google gets this straightened out, we should be all set to continue the porting process.  Hope this helps!

Photo of Kim

Kim, Alum

  • 44,004 Points 20k badge 2x thumb
Our porting team has updated me, "the issue has been resolved and the number will port to RingCentral on 7/11/2016."