Purpose
This KB outlines the end-to-end process for provisioning long codes and toll-free numbers in the V5 portal. The primary objective of this procedure is to ensure accurate setup of customer-requested numbers, alignment with campaign requirements, and synchronization with platform configurations.
Scope
This KB applies to the Support agents responsible for assigning and provisioning numbers in the V5 portal for all customer accounts.
This procedure is applicable to both the Leased and BYON numbers.
Procedure
Check if the request is for the BYON or Leased Number
1. Leased Numbers
To Lease, the numbers, refer to Number procurement (LC, TFN, International, Shortcode, Alpha code, Canadian number)
Ex Customer Requests: Procure Numbers, Order Numbers
2: BYON (Bring Your Own Number) Numbers
From Account ID: 1 (Aerialink), check if the number is already assigned to any account by searching the number in the search box.
Below image shows the number is already assigned to the account, so if it is provisioned to one of the customers accounts who submitted the support ticket, provide the details and ask if any changes are required.
But if the number is provisioned to a different customer account, then inform the customer that number cannot be provisioned.
Step 1: LOA Verification
Special Case – State Farm Accounts
-
For State Farm BYON numbers, follow these rules when deciding on LOA requirements:
-
Check the NNSR (NetNumber Service Registry):
If the number shows no conflict in NNSR →
proceed with provisioning without requesting an LOA.
Route the number through Aerialink normally.If the number has a conflict (i.e., it is already assigned to another provider) →
request an LOA from State Farm and attach it to the NNSR ticket before routing.
-
In future conflicts:
If another party later raises an NNSR ticket to overwrite a number, contact State Farm again to obtain a new LOA confirming ownership.
-
Reporting visibility:
State Farm receives a daily “Health Audit” report showing any overwritten or newly routed numbers. They will reach out if something appears unapproved.
-
Note: This exception applies only to State Farm accounts only. For all other customers, continue following the standard LOA verification process.
For All Other Accounts – Standard LOA Process:
a. Check the List of the Numbers provided.
b. Make sure the date is within the 30 days and the Authorized Signature mentioned in the LOA shared by the customer in the ticket.
- Navigate to the V5 portal using the following link: https://mb-portal.aerialink.net/codes
- Switch to the customer account using the switch account functionality as shown below.
Step 2: Navigate to Code Management
- On the left Nav menu, go to:
Codes > Code Management - Click on the ‘+’ (plus) icon to begin the number provisioning process.
Step 3: Enter Number Details
On the new page, complete the required fields using the information provided by the customer:
Step 4: Finalize and Create Codes
- After verifying all fields, click “Create Codes” to provision the numbers and assign them to the designated campaign.
Provisioning Details:
Special Case – AMN Healthcare Accounts (ID - 146, 364)
All AMN healthcare long codes should be published with espid 'E0B4' (NetNumberID - 103637)
FOR Long Code
| Field | Description / Selection |
| Codes (Requested Numbers) | (Requested numbers) |
| Connection | As requested by the customer |
| Code Type | - LC/TFN - Leased → If procured/Leased - LC/TFN - BYON → If shared by customer via LOA |
| Code Source | - Inteliquent → If leased - Aerialink Text Number (offnet) → For BYON |
| Item Code | LC-NA |
| Number | (Leave blank) |
| ESPID |
- E136 (for Longcode) - E0B4 for all AMN Healthcare long codes |
| TON | International |
| NPI | 1 (Keep NPI value always 1) |
| Provider | - P2P-1 – Syniverse (for Longcode) |
| Campaign ID | As requested by the customer |
For TFN
| Field | Description / Selection |
| Codes (Requested Numbers) | (Requested numbers) |
| Connection | As requested by the customer |
| Code Type | - LC/TFN - Leased → If procured/Leased - LC/TFN - BYON → If shared by customer via LOA |
| Code Source | ONVOY Network (Sponsored)→ For TFN |
| Item Code | LC-NA |
| Number | (Leave blank) |
| ESPID | -E19B (for TFN) |
| TON | International |
| NPI | 1 (Keep NPI value always 1) |
| Provider | -A2P-US/CAN - ZipWhip (for TFN) |
| Campaign ID | N/A |
For ShortCode
| Field | Description / Selection |
| Codes (Requested Numbers) | (Requested numbers) |
| Connection | As requested by the customer |
| Code Type | SC US/CAN |
| Code Source | CSCA, Common Short Code United States |
| Item Code | SC-USA-DEDICATED-VANITY |
| Number | (Leave blank) |
| ESPID | CSCA |
| TON | International |
| NPI | 1 (Keep NPI value always 1) |
| Provider | A2P-US/CAN-2 – mGage Primary SMS |
| Campaign ID | N/A |
Note: The Provider field should show the company or vendor that supplies or leases the ShortCode.
For Alpha Code
| Field | Description / Selection |
| Codes (Leased Numbers) | Alpha codes are always leased numbers |
| Connection | As requested by the customer |
| Code Type | ALPHA Leased |
| Code Source | AlphaNumeric Defined (A2P INTL Only), any provider |
| Item Code | AN-INTL |
| Number | (Leave blank) |
| ESPID | NA |
| TON | Alphanumeric |
| NPI | 0 (Keep NPI value always 0) |
| Provider | Where the Alpha code is leased |
| Campaign ID | N/A |
Note: The Provider field should show the company or vendor that supplies or leases the Alpha Code.
If the leasing source changes (for example, Kaleyra/mgage/TATA communication provider), the Provider field must be updated accordingly.
Step 5: Add Numbers to 10DLC portal (This step is only applicable to the customers who use 10DLC portal to create the campaigns)
-
To link numbers for customers campaigns, which are shared in 10DLC portal (https://platform.aerialink.net/). Open our 10DLC portal and switch to 10DLC account as per below screenshot.
-
Switch to the customer’s account and click on 10DLC option shown in the image
- Again, click on the 10DLC portal link and login with the V4 Credentials.
- Once switched to 10DLC account > search customer account and again hit switch to customer sub-account as per below screenshot.
- Once switched on the top left side click 10DLC > campaigns > search campaign and click on it.
- Once inside the campaign, add the numbers to the box shown below and click on submit
Step 5: Confirmation
- In the 10DLC portal, verify that all requested numbers have been successfully assigned and are showing a Success status for both A&T - T-Mobile
In Postman, using OSR lookup/ Get Publish Status check if the code is linked to the campaign and has the A2P context attribute, as shown below.
Additionally, ensure provisioned_id is Aerialink and nnid is 102738
Also, using the Syniverse Tmobile Campaign Lookup endpoint in the SDG verify if the code is in “ADDED” status as shown below.
Resolution
Once codes are created:
- Confirm that the numbers have been successfully provisioned and linked to the campaign.
- Using the AL-Provisioning Request Complete macro in Zendesk, notify the customer that the numbers are now active and ready for use.
Notes
- Double-check customer input for accuracy (e.g., Campaign ID, Connection Type).
- For any discrepancies or further troubleshooting with provisioning, escalate to the Tier2 team.
Comments
0 comments
Please sign in to leave a comment.