Porting Process

Private Beta Notice

The Port Orders API endpoints are currently in Private Beta. Some features may change as we receive and incorporate your feedback. To get invited and start testing the beta version, please send an email to support@flowroute.com.

Porting is the general process for moving your phone numbers from one carrier to another. The Port Orders API is designed to allow Flowroute customers to move their phone numbers from their current service provider to Flowroute. Aspects of this process are mandated by the FCC, while certain parts are specific to your current service provider and whether you are porting a local number or a toll-free number.

Flowroute has created a general process that facilitates porting your numbers in a smooth and predictable manner. You will always know what steps are needed to move forward with the port and we will keep you updated throughout the entire porting process.

  1. Gather List of Porting Phone Numbers

  2. The first step to porting a phone number is to know what phone number you want to port. It is important that you have a clear understanding of what numbers you want to port away from your current service provider and which numbers, if any, will remain with them. Flowroute recommends that you work with your current service provider to outline to them what numbers will be ported, what numbers will remain, and what you want to do with remaining services.

    During this time it is also ideal to ask your current service provider for a customer service record for the porting phone numbers. This is the set of information that you can provide to Flowroute that we will submit on our port request. This information allows the current service provider to approve the port request.

  3. Check Portability for each Phone Number

  4. You can check if a particular number can be ported by Flowroute. The response will automatically separate the submitted numbers based on their portability and group numbers that can be ported on the same order. It is recommended that you always verify the portability of a number before attempting to add a number to a Port Order in order to minimize errors during port order creation.

  5. Create a Draft Port Order

  6. At this point your Port Order will be in the new_order state.

  7. Add End User Service Information

  8. E-sign the Letter of Agency

  9. This transitions you to ready_to_submit.

  10. Flowroute Verifies Porting Information

  11. Flowroute enters the coordinating_with_losing_service_provider state. Flowroute accomplishes the verify_ownership task.

    This may result in the Port Order becoming Blocked, which will require action from you in order to resolve.

  12. Flowroute submits port to current service provider

  13. Flowroute begins approve_lsr.

  14. Flowroute resolves any information mismatches

  15. This may result in the Port Order becoming Blocked, which will require action from you in order to resolve.

  16. Flowroute coordinates a port completion date

  17. Flowroute accomplishes confirm_activation_date. Once we get FOC we enter pending_activation.

  18. Flowroute activates the port

  19. Flowroute accomplishes acquire_ownership and activate_number states. Flowroute enters the completed state.

State Endpoints
  • new_order

    This is the initial state for every Port Order. While in this state, the user has full control over the Port Order, its information, and the numbers present in the Port Order.

  • ready_to_submit

    This state allows the user requesting the Port Order to perform a final review before Flowroute begins working on the order. Once this state is completed, Flowroute will begin coordinating with the Losing Service Provider in order to complete the port.

  • coordinating_with_losing_service_provider

    Flowroute has begun working on the Port Order and is negotiating with the Losing Service Provider in order to gain a firm_order_completion_date for the Port Order. This is the state where most blockers are encountered.

  • pending_activation

    Once Flowroute receives a firm_order_completion_date from the Losing Service Provider, we will transition the order into this state. At this point, no additional intervention should be required from the user in order to complete the Port Order. Also, users may modify the firm_order_completion_date if they need to.

  • completed

    On the firm_order_completion_date, Flowroute will activate the Port and service will transition from the Losing Service Provider to Flowroute. Once this has been completed and Flowroute has verified that the port took effect, we will transition the order to this state.

Task Endpoints
  • create_order

    User creates the Port Order, adds numbers and end user service information to the Port Order, and esigns the LOA.

  • verify_ownership

    Flowroute verifies that the end user information on file with the Losing Service Provider matches the information submitted with the Port Order.

  • approve_lsr

    Flowroute submits the LSR (formal port request) to the Losing Service Provider and gains a firm_order_completion_date.

  • confirm_activation_date

    Flowroute communicates the firm_order_completion_date to the User and prepares the port to complete on the firm_order_completion_date.

  • acquire_ownership

    Flowroute initiates the port and becomes the carrier of record for the porting numbers.

  • activate_number

    A routing update is published to all carriers informing them that Flowroute is now the carrier for the porting numbers.