Go Home

Service Agent Help Center

Search for any topics or questions you need help with.

Documents required for porting Google Voice VoIP Numbers

Avatar
Divyanshu Goel
Updated 5 months ago

List of required documents (๐Ÿ“œ):

  1. Unlock confirmation screenshot
    Before we can begin the porting process, your number must be unlocked for transfer.
    Please share a screenshot that confirms your number is unlocked.

    How to unlock your Google Voice number -

    1. Sign in with the Google account linked to the number.

    2. If the number is eligible, click Unlock and complete the one-time payment (if required).

    3. Once unlocked, take a screenshot of the confirmation page (showing the number and unlock status).

  2. Letter of Authorization (LOA) dated within the last 30 days.
    Please download the form, fill all necessary details and submit the form.

  3. Capture a screenshot of the Google Voice settings page that clearly shows -
    a) The Google Voice number you want to port.
    b) The Google Account email address associated with the number.


  4. Porting PIN 
    The porting PIN is a mandatory field during the porting process. For Google Voice numbers, if you do not manually set a PIN when unlocking the number for porting, the last four digits of your Google Voice number will be used as the default porting PIN.


There is no downtime & the number remains active till it is ported to ServiceAgent. It takes anything b/w 2-3 weeks to port the US, and Canadian numbers, depending on the complexity of the port and the time required by the current service provider. Please don't cancel your previous provider's account until the porting is completed. 

 

 

Instruction to fill out the fields on the LOA Form (๐Ÿ“Œ):

Field

Instructions to fill

Additional Comments

Customer Name

The Customer Name is the name of the admin or the owner, and it should appear exactly as it does on the on-file records of the current carrier or the CSR (if the service is under the name of an individual).

 โš ๏ธIncorrect information will lead to rejection

Business Name

Name of the business as mentioned on on-file records of the current carrier or the CSR (If the service is in your company's name).

 โš ๏ธIncorrect information will lead to rejection

Service Address

Please ask your current/losing carrier to provide a Customer Service Record and enter the Service Address mentioned on it. 

 

โš ๏ธIncorrect information will lead to rejection

Account Number

Please ask your losing carrier if the numbers you are porting have an Account Number associated with them and provide the same if applicable 

โš ๏ธMissing information will lead to rejection

PIN

Please ask your losing carrier if the numbers you are porting have a Port-Out PIN associated with them and provide the same if applicable.

โš ๏ธMissing information will lead to rejection

  


Pro Tips (๐Ÿ’ก):

  1. To fill out the LOA form, please get in touch with your current provider and ask them to share your number's CSR (Customer Service Record). This includes the details like name/business name, service address, name of the authorized user to sign the LOA, Account Number and Port-Out PIN (if applicable) associated with your number.

  2. Your LOA must show your actual US/Canadian address for the number(s) to be ported according to the country of the number in the port request. 




โš ๏ธ Important Notes

  • Do NOT cancel your service with your current provider until the port is completed.

  • The number must remain active throughout the porting process.


 

๐Ÿ“ค How to Submit Your Porting Request

Once you have all the required items ready, please email them to:

๐Ÿ“ง help@serviceagent.ai
Subject: Port Request โ€“ Google Voice โ€“ [Your Phone Number]

๐Ÿ” Important: Be sure to send the porting request from your registered email address associated with your ServiceAgent account. This helps us verify your identity and process the request faster.


 

If you have any further questions, feel free to reach out to us at help@serviceagent.ai or via the Support Chat option available within the ServiceAgent application.

Did this answer your question?
๐Ÿ˜ž ๐Ÿ˜ ๐Ÿ˜ƒ