Skip to main content

How to submit a snap port request in Aloware

Easily transfer phone numbers to Aloware with Snap Port. Learn the steps, requirements, and timeline for a smooth 24–48 hour port.

Laarni D avatar
Written by Laarni D
Updated over a week ago

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 simple steps:

  1. Request your current provider to release the numbers back to Twilio.

  2. Transfer those numbers from Twilio to Aloware.

The Snap Port process typically takes 24-48 business hours after your provider approves 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.


How to submit a Snap Port request

  1. Start the porting request

    1. Go to Account > Number Port to begin the process; this option is available to both billing admins and admins.

    2. Click Start Port-in Request.

      Start the porting request

    3. Fill in the Aloware port-in request form:

      1. Company name

      2. First name, Last name

      3. Email address

      4. Job Title

      5. Losing Carrier - enter the name of the company that currently holds the phone number (s) being requested to port into Aloware.

  2. Prepare the required documents

    To authorize and verify your Snap Port request, you’ll need to provide the following:

    1. Letter of Authorization (LoA) - fill out and sign the LoA document, then upload it. This form is required to authorize the transfer.

    2. List of numbers - provide the complete list of phone numbers you want to port.

    3. Supporting documents - include proof of ownership, such as:

      • A recent utility bill or invoice that shows you own the numbers.

      • A CSR (Customer Service Record), if requested.

    4. Earliest port date - select the earliest date you authorize 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 complete the transition.

    5. A2P 10DLC compliance acknowledgments – 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.

  3. Work with your current provider

    1. Request number release - ask them to release your numbers back to Twilio.

    2. Obtain a ticket ID - once the release request is received, your provider will issue a ticket ID or confirmation number. This serves as proof that your request has been initiated.

  4. Submit the necessary documents

    Now that you have everything ready, click the Submit button, Aloware support will take care of verifying all the details:

    1. Submit the ticket ID - this is important for the Snap Port process.

    2. Completely filled out and signed LoA and supporting docs.

  5. Verification and submission

    Once you've shared all the required information, here's how Aloware handles the next steps:

    1. Aloware will review to ensure everything is correct.

    2. Aloware submits a formal Snap Port request to Twilio, including:

      1. The ticket ID or confirmation number

      2. The full list of numbers to be ported

      3. The destination account SID (if applicable)

With these steps completed, Aloware coordinates with Twilio for final approval and execution of the port. You'll receive updates along the way to ensure the process is seamless and your phone numbers are transitioned smoothly.


What happens next?

  1. 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 losing carrier’s confirmation is required for the port to proceed. Twilio will then notify Aloware once the release is approved.

  2. Scheduling the port

    After the release is approved, Aloware Support will contact you to 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 porting.

  3. Completion of porting

    Twilio will notify Aloware when the transfer is complete. Aloware will assign the ported numbers to your account, ensuring they are ready to use.

  4. Final verification

    Once the numbers are assigned, voice and SMS functionality are tested to ensure everything is working correctly. Your Customer Success Manager (CSM) will provide you with a final confirmation that the porting process is complete.


Additional Snap Port considerations

  1. 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.

  2. Testing after porting

    Once the port or setup is complete, the Aloware Customer Success Manager (CSM) or Technical Support Representative (TSR) 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 potential issues or confirm successful setup. If any errors occur, they will address them promptly to prevent disruptions before you launch campaigns.

  3. Turn-around time

    The Snap Port process typically takes 24-48 business hours to complete after the losing carrier approves the release and Twilio confirms the transfer. Once approval is received, Aloware will work with you to accommodate your preferred schedule for the port.

Did this answer your question?