Conductor makes porting a breeze by automating your interaction with the porting team when submitting project ports:

  • Automatic mapping of temporary numbers to port-in numbers.
  • Generate LoA's that are able to be signed by the customer.
  • Automatic Salesforce case creation and port package submission.
  • Case status updates (visible inside the porting queue in Conductor).
  • Toll-free number support.

Porting Flow Overview

  1. Numbers added to Conductor are automatically carrier "dipped" to verify portability to RingCentral.
  2. Next, numbers are categorized into carrier groups for you by common carrier for easy collection of required details, i.e. BTN, authorized person, service address, etc...
  3. Once the required details have been collected and a port package is created, an LoA document is generated containing all of the necessary content.
  4. After the customer signs the LoA documents in the port package, hitting the submit button will automatically create a Salesforce case with the porting team.
  5. Updates or changes to the status of the Salesforce case are displayed in the porting queue.

Port Packages

Port packages are wrappers that contain carrier groups and their corresponding LoA's. Port packages allow you to select which carrier groups in the workspace should be part of the package to provide flexibility for phased porting activities across multiple sites.

Create a Porting Package

To create a porting package in Conductor, select the workspace and then hit the Port Package button located above the datatable.

Choosing Carrier Groups

Numbers are categorized into carrier groups for you based on the service provider information obtained during the dipping process.

  • Numbers are grouped by common losing provider.
  • You can choose to include all or only some of the carrier groups in a porting package, allowing you to port some carrier groups now and some carrier groups later to accommodate phased porting activities.
  • Additionally, you can create your own custom carrier groups for maximum flexibility when grouping numbers for porting.

Group Details

Before you can generate the LoA documents, the group details for each carrier group must be provided.

The required information can be provided by navigating to one of the groups by clicking on its badge above the datatable and then hitting the Group Details buttons to provide the required information. Alternatively, you can access the group details through the porting queue by clicking on the package and hitting the Edit Details button next to the carrier group(s).

If these details are not provided accurately, your port request may be rejected and could delay the go-live date of your customer.

Port Package Desired Port Date

Confirm the date you would like for your port request to complete.

  • Must be a minimum of 15 days from the current date (porting lead-time).

Port Package States

TODO

Creating LoA Documents

To generate the LoA documents, navigate to the porting queue and click the Create LoA button next to the porting package.

Customer Signature for LoA Documents

Only customer users can sign the LoA's inside of Conductor. The customer can follow the link that Conductor posted to the activity feed when the LoA documents were created, or alternatively login, go to the porting queue, click on the Sign LoA button and provide an e-signature.

Submitting Port Packages

Once all LoA documents have been signed the porting package is ready to submit to the porting team. To submit your package, simply click on the Submit button next to the package in the porting queue.

Submitting your package automatically creates a Salesforce case and attaches all of the relevant information to the case for the porting team to complete the project port request. Any changes or updates the porting team makes to the status of the case are reflected inside of Conductor's porting queue.