Port Rejection
From VoIP.ms Wiki
| [quality revision] | [draft revision] |
| Line 1: | Line 1: | ||
| - | + | Please note that a port request starts with your paperwork to us, then we submit your request to our CLEC (CLECs are the actual holder of numbers). That CLEC then submits the port request to losing carrier's (CLEC). At that point the ball is in losing CLEC's court. | |
We then notify you when our CLEC notifies us of a pending porting date (FOC) or a rejection. | We then notify you when our CLEC notifies us of a pending porting date (FOC) or a rejection. | ||
| - | When porting a number rejections are always a possibility. Rejections are different depending on the situation, it can be for information missing or information mismatch. | + | When porting a number rejections are always a possibility. Rejections are different depending on the situation, it can be either for information missing or information mismatch. |
| - | As an '''Important Note''' we must say that all rejections for mismatch information always come from the losing carrier. We wish to have every porting number with us as fast | + | As an '''Important Note''' we must say that all rejections for mismatch information always come from the losing carrier. We wish to have every porting number with us as fast as possible, there is no reason why we should reject any order unless any information is missing. |
| - | In case that your porting order gets rejected, you must contact the losing carrier. The best way to identify the Mismatch and correct it would be to get a CSR (Customer Service Record), which contains the necessary information to complete the request correctly. | + | In case that your porting order gets rejected, you must contact the losing carrier. The best way to identify the Mismatch and correct it would be to get a CSR (Customer Service Record), which contains the necessary information to complete the request correctly. If the losing carrier is not able to provide the actual copy of the CSR, we will need the information as it is listed on the CSR. |
| + | There are many different reasons why a port can get rejected that we can not listed them all. However, we will list the most common ones according to our experience: | ||
| - | |||
| + | '''Abbreviations''' | ||
| - | + | Abbreviations are Not a firm reason for a rejection e.g. Sending "45 St 1St Av" instead of "45 Street First Avenue" will not clear the rejection since it remains the same address. | |
| - | |||
| + | '''Rejection for Mismatch Information (Name, Address, Company Name)''' | ||
| - | + | The info that matters is not the info that your provider has listed for you, but rather the info that is listed on record with your provider's CLEC (upstream carrier). Your VoIP provider uses a CLEC to provide your number and this is the entity where ports take place. The info might be different if you moved and notified your VoIP provider, who in turn did not update the records with their CLEC holding your number. It is also possible in some cases that the CLEC has on file the info of your VoIP provider rather than your address. | |
| - | + | ||
| - | The info that matters is not the info that your provider has listed for you, but rather the info that is listed on record with your provider's CLEC (upstream carrier). Your VoIP provider uses a CLEC | + | |
Also, some resellers refer to the Zip code (or Postal Code) causing the rejection, please note that the only information validated in an address is the street name, street number (Suite/Floor if applicable), sometimes not even the city is validated. | Also, some resellers refer to the Zip code (or Postal Code) causing the rejection, please note that the only information validated in an address is the street name, street number (Suite/Floor if applicable), sometimes not even the city is validated. | ||
| - | ''' | + | '''Account Number, Reseller Mismatch''' |
| - | The account number provided or the reseller name given does not match with what the losing CLEC has on records, even though the information appears | + | The account number provided or the reseller name given on the port does not match with what the losing CLEC has on records, even though the information appears correct on the bill. Remember that sometimes the information on the losing CLEC's end might be different to the one the losing reseller has. For a successful port, we must always match the CLEC's information. |
| - | ''' | + | '''Leaving Stranded Services/Numbers/Features''' |
| - | Sometimes the account with the losing carrier might have some numbers, services or other features which if not mentioned, can cause a rejection. It is important to always mention this information on the Partial Port section and also the actions to be taken | + | Sometimes the account with the losing carrier might have some numbers, services or other features attached to the number to port which, if not mentioned, can cause a rejection. It is important to always mention this information on the Partial Port section (Step 2) and also the actions to be taken. Most carriers will not allow the remaining services to be kept active, in most cases they will have to be disconnected at the time of porting. |
| - | ''' | + | '''Freeze on the Account, Pending Order''' |
| - | This kind of rejection | + | This kind of rejection is very strange, usually there is no further information. The losing carrier only advises our carrier that the order was rejected for pending order. As usual, the customer must contact the losing carrier and have the pending order removed and provide the confirmation number once it has been removed so we may resubmit the order. |
| - | ''' | + | '''More Recent Authorization''' |
| - | Sometimes, even when we already have an FOC date, the losing carrier is able to reject the order, this kind of rejections is called for More Recent Authorization. | + | Sometimes, even when we already have an FOC date, the losing carrier is able to reject the order, this kind of rejections is called for More Recent Authorization. It means that the losing carrier received a more recent authorization than ours to port this number or that the customer contacted the losing carrier and cancelled this request, or that the losing carrier received a request from another carrier more recently. In this case you will also need to contact the losing carrier to verify this and then let us know how to proceed. |
| Line 46: | Line 45: | ||
'''''IMPORTANT''''' | '''''IMPORTANT''''' | ||
| - | Remember that we have limited time to reply to our | + | Remember that we have limited time to reply to our carriers about these rejections. Please have the rejection cleared as soon as possible and reply to us within the next 7 days. Rejections that are not cleared or replied after this time might get automatically cancelled by our system and you will have to start a new order. In some cases a refund is not applicable since carriers are already paid. |
Feel free to contact us if you have any questions about this WikiNote. | Feel free to contact us if you have any questions about this WikiNote. | ||
Revision as of 20:09, 8 May 2013
Please note that a port request starts with your paperwork to us, then we submit your request to our CLEC (CLECs are the actual holder of numbers). That CLEC then submits the port request to losing carrier's (CLEC). At that point the ball is in losing CLEC's court. We then notify you when our CLEC notifies us of a pending porting date (FOC) or a rejection. When porting a number rejections are always a possibility. Rejections are different depending on the situation, it can be either for information missing or information mismatch.
As an Important Note we must say that all rejections for mismatch information always come from the losing carrier. We wish to have every porting number with us as fast as possible, there is no reason why we should reject any order unless any information is missing. In case that your porting order gets rejected, you must contact the losing carrier. The best way to identify the Mismatch and correct it would be to get a CSR (Customer Service Record), which contains the necessary information to complete the request correctly. If the losing carrier is not able to provide the actual copy of the CSR, we will need the information as it is listed on the CSR.
There are many different reasons why a port can get rejected that we can not listed them all. However, we will list the most common ones according to our experience:
Abbreviations
Abbreviations are Not a firm reason for a rejection e.g. Sending "45 St 1St Av" instead of "45 Street First Avenue" will not clear the rejection since it remains the same address.
Rejection for Mismatch Information (Name, Address, Company Name)
The info that matters is not the info that your provider has listed for you, but rather the info that is listed on record with your provider's CLEC (upstream carrier). Your VoIP provider uses a CLEC to provide your number and this is the entity where ports take place. The info might be different if you moved and notified your VoIP provider, who in turn did not update the records with their CLEC holding your number. It is also possible in some cases that the CLEC has on file the info of your VoIP provider rather than your address. Also, some resellers refer to the Zip code (or Postal Code) causing the rejection, please note that the only information validated in an address is the street name, street number (Suite/Floor if applicable), sometimes not even the city is validated.
Account Number, Reseller Mismatch
The account number provided or the reseller name given on the port does not match with what the losing CLEC has on records, even though the information appears correct on the bill. Remember that sometimes the information on the losing CLEC's end might be different to the one the losing reseller has. For a successful port, we must always match the CLEC's information.
Leaving Stranded Services/Numbers/Features
Sometimes the account with the losing carrier might have some numbers, services or other features attached to the number to port which, if not mentioned, can cause a rejection. It is important to always mention this information on the Partial Port section (Step 2) and also the actions to be taken. Most carriers will not allow the remaining services to be kept active, in most cases they will have to be disconnected at the time of porting.
Freeze on the Account, Pending Order
This kind of rejection is very strange, usually there is no further information. The losing carrier only advises our carrier that the order was rejected for pending order. As usual, the customer must contact the losing carrier and have the pending order removed and provide the confirmation number once it has been removed so we may resubmit the order.
More Recent Authorization
Sometimes, even when we already have an FOC date, the losing carrier is able to reject the order, this kind of rejections is called for More Recent Authorization. It means that the losing carrier received a more recent authorization than ours to port this number or that the customer contacted the losing carrier and cancelled this request, or that the losing carrier received a request from another carrier more recently. In this case you will also need to contact the losing carrier to verify this and then let us know how to proceed.
In every case, our Staff will provide as much information as possible to help you understand and clear the rejection.
IMPORTANT
Remember that we have limited time to reply to our carriers about these rejections. Please have the rejection cleared as soon as possible and reply to us within the next 7 days. Rejections that are not cleared or replied after this time might get automatically cancelled by our system and you will have to start a new order. In some cases a refund is not applicable since carriers are already paid.
Feel free to contact us if you have any questions about this WikiNote.
