What is a Snap Port?
A Snap Port transfers phone numbers from one platform (e.g., Aircall, JustCall, or HighLevel) to Aloware when both platforms use Twilio as their carrier.
The process has two (2) simple steps:
Request your current provider to release the numbers back to Twilio.
Transfer those numbers from Twilio to Aloware.
The Snap Port process typically takes 24-48 business hours after your provider approved the release, ensuring a smooth and hassle-free transfer. There is no fee for porting numbers unless specified by your current provider or the losing carrier.
To provide more depth, note that the initial phase of the Snap Port process involves obtaining provider approval, which typically spans 24-48 business hours. Following approval, the actual porting, where numbers are transferred, usually completes within 1-2 hours, ensuring minimal downtime.
How to submit a snap port request
Start the porting request
Go to Account > Number Port to begin the process; this option is available to both billing admins and admins.
Click Start Port-in Request.
Fill in the Aloware port-in request form:
Company name
First name, Last name
Email address
Job title
Losing carrier - enter the name of the company that currently holds the phone number (s) being requested to port into Aloware.
Prepare required documents
To authorized and verify your Snap Port request, you will need to provide the following:
Letter of Authorization (LoA) - fill out and sign the LoA document, then upload it. This form is required to authorize the transfer.
List of numbers - provide the coplete list of phone numbers you want to port.
Supporting documents - include proof of ownership, such as:
A recent utility bill or invoice that shows you own the numbers.
A CSR (Custom Service Record), if requested.
Earliest port date - select the earliest date you authoirze your numbers to be moved into Aloware.
This date cannot be changed once the request is submitted to your losing carrier. It represents the soonest time your company is prepared to transition.
A2P 10DLC compliance acknowledgements
Confirm the following by checking the boxes in the form:
You understand that an approved A2P 10DLC campaign is required to use messaging in Aloware.
You understand that carriers may not immediately onboard your numbers into your approved A2P 10DLC campaign, which could cause temporary outbound SMS failures.
Work with your current provider
Request number release - ask them to release your numbers back to Twilio.
Obtain a ticket ID - once the release is received, your provider will issue a ticket ID or confirmation number. This serves as proof that your request has been initiated.
Submit the necessary documents
Now that you have everything ready, click the Submit button, Aloware support will take care of verifying all the details:
Submit the ticket ID - this is important for the Snap Port process.
Completely filled out and signed LoA and supporting docs.
Verification and submission
Once you have shared all the required information, here's how Aloware handles the next steps:
Aloware will review to ensure everything is correct.
Aloware submits a formal Snap Port request to Twilio, including:
The ticket ID or confirmation number
The full list of numbers to be ported
The destination account SID (if applicable)
When these steps completed, Aloware coordinates with Twilio for final approval and execution of the port. You will receive updates along the way to ensure the process is seamless and your phone numbers are transitioned smoothly.
What happens next?
Twilio reviews and coordinates with the losing carrier
Once Aloware submits the Snap Port request, Twilio reviews the information and coordinates with your current provider (the losing carrier). The losign carrier's confirmation is required for the port to proceed. Twilio will then notify Aloware once the release is approved.
Scheduling the port
After the release is approved, Aloware support will contact you ro confirm your preferred date and time for the port. Twilio's role here is to coordinate the schedule, but the losing party's approval is what ultimately allows the process to move forward.
Note that this approval flow applies only to Snap Port requests, not to manual or regular port. The actual proting process typically takes only 1-2 hours to complete once the scheduled time arrives.
Completion of porting
Twilio will notify Aloware when the transfer is complete. Aloware will assign the ported numbers to your account, ensuring that they are ready to use.
Final verification
Once the numbers are assigned, voice and SMS functionality are tested to ensure everything is working correctly. Your Customer Service Manager (CSM) will provide you with a final confirmation that the porting process is complete.
Additional Snap Port considerations
Number onboarding
After port approval, number onboarding, the process of registering numbers with an approved messaging service through the Mobile Network Operator (MNO), can take up to 10 days. This step ensures SMS functionality complies with regulations and business requirements.
Testing after porting
Once the port or setup is complete, the Aloware CSM will test both voice calls and SMS functionality to ensure your numbers are fully operational.
They will also monitor the Twilio Console for logs to identify any potentional issues or confirm successful setup.
If any errors occur, they will address them promptly to prevent disruptions before you launch campaigns.
Turn-around time
The Snap Port process typically takes 24-28 business hours to complete after the losing carrier approves and Twilio confirms the transfer.
Once approval is received, Aloware will work with you to accommodate your preferred schedule for the port.
However, it is important to note that the 24-48 hours mentioned specifically applies to obtaining provider approval. Once this phase is complete, the actual porting itself generally takes about 1-2 hours, depending on scheduling and any pre-existing arrangements.