Who can say yes to licensing failed-port records? A decision tree for telecom systems consultants

Short answer

Introduce the provisioning director first, as the person who convenes the conversation and can explain how failed ports are worked, then the CEO, who can authorize a licensing discussion. The tree splits on who created each record: the provider's own orders, tickets and notes sit with its CEO; CSR copies and rejection notices came from the other carrier; customer account details carry CPNI duties; reseller work may belong to a wholesale contract. A platform administrator has access to all of it and authority over none.

Visual briefFull-size diagram
A left-to-right tree that starts from failed-port records and splits four ways: the provider's own orders, tickets and notes light up through the provisioning director to the CEO; other-provider CSR copies route to counsel; customer account details route to CPNI limits; reseller records route to the wholesale contract.
The green path is the introduction. The amber branches are decided by counsel and SourceX's rights review, not by the partner.

This tree belongs to the number porting failure resolution guide. It answers one narrow question: once you know a provider kept its failed-port history, whose yes starts the conversation.

Sorting a failed port by who created each record

One rejected business port, worked to activation, leaves records written by at least three different hands. Sort them before thinking about people, because the creator usually decides which branch of the tree a record follows.

Record in the port fileWritten byBranch of the tree
Original port order and each supplementThe provider's provisioning teamProvider-owned: CEO decides
Service desk ticket and analyst notesThe provider's support staffProvider-owned: CEO decides
Corrected submission and activation confirmationThe provider, on its order platformProvider-owned: CEO decides
Customer service record copyThe losing carrierOther-provider: counsel reads the terms
Rejection notice and reason codeThe losing carrierOther-provider: counsel reads the terms
Account holder name, address, account numberThe end customer, held by the providerPrivacy limits: CPNI and de-identification
Orders placed for a reseller's customersThe provider, on a wholesale client's behalfContract: wholesale agreement decides

Do not add the national porting database as an eighth row. Its administrator restricts the NPAC to authorized users for permitted purposes, so its contents are not any single provider's to put on the table.

Walking the tree from port desk to signer

Follow the questions in order. Stop at the first person who answers yes to branch 4.

  1. Does this person work ports or administer the platform? Port analysts, the order platform administrator and a migration consultant answer yes. They can tell you record classes, years and counts. Ask who runs provisioning.
  2. Does this person run provisioning? Usually the provisioning director. Ask them to convene, to bring in the CEO, and to say whether the order platform is being replaced. They become your working contact.
  3. Is the provider independent, part of a group, or in a wind-down? A group may hold authority at the parent. A provider closing down acts through its board; the board resolution guide shows how a board names who handles data assets.
  4. Can this person commit company records to an agreement? The CEO. This is the introduction.
  5. Has counsel heard about the other-carrier records and the wholesale clients? If not, the sponsor should bring counsel to the first call.

A common slip is treating branch 2 as the end of the tree. The convener's enthusiasm is necessary and not sufficient.

Branches where counsel or another party decides

Three branches turn amber, and the partner's job on each is to note that the branch exists, not to resolve it.

Other-carrier documents. The CSR copy and the rejection notice explain why a port failed, so they are central to the story. They also originate with the losing provider and may be governed by porting or interconnection agreements. Whether copies can sit in a licensed set is a legal reading.

Customer account details. Every order names the account holder and describes their lines. The FCC's CPNI rules, grounded in Section 222, oblige carriers to keep that customer information confidential and restrict sharing it without the customer's approval. A licensing decision cannot override those duties, so stripping or de-identifying these fields is settled by counsel first.

Reseller and wholesale work. When a provider sells lines through resellers, a third party sits between it and the end customer. Orders it placed for a reseller's customers may be governed by that wholesale contract. Note which share of rejected ports were wholesale, if the director knows; leave the rest to review.

Two providers, two answers (Illustrative)

Two fictional providers show how the same tree lands on different people. Neither describes a real company or deal.

Tree question320-person regional business voice provider610-person fiber provider owned by an infrastructure fund
Who describes the records?Port desk lead and platform administratorOrder management manager
Who convenes?Provisioning directorVice president of network operations
Who can say yes?CEO, with general counselFund-appointed CEO, after the board is informed
Other-carrier documentsCopies kept in a shared mailboxCopies stored on the order platform
Wholesale shareSmall, two reseller clientsLarge, a wholesale arm with its own contracts
Likely starting scopeThe provider's own orders, supplements and ticketsSame, minus wholesale orders until contracts are read

The fund-owned provider is not distressed because its owner is weighing a data decision; licensing records is an ordinary choice for a healthy business, as the answer on whether selling data means a company is failing explains.

Open until SourceX's rights review

When the right executive agrees to talk, say plainly what nobody knows yet:

  • Inclusion: which record classes and which years can be licensed once porting, interconnection and wholesale terms are read.
  • Privacy work: what customer information must be removed or de-identified.
  • Demand: whether AI labs and data users want failed-port histories when SourceX reviews them.
  • Terms: whether any offer is made.

The provider needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English. Partners sign the Channel Partner Agreement before submitting introductions. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, and only one partner is credited per company. Why data rights matter explains why the review comes before any offer. When you know the signer, record them in the failed-port referral brief template; the cross-system map shows which systems the convener will be asked about. Other sectors with similar record chains are on the industries hub.

Next step

Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

Once your convener has brought in the CEO and counsel knows about the other-carrier and wholesale records, register as a partner, check the provider on who qualifies and read the program terms before you make the introduction.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardYour 25% of the actual supplier payout. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

The migration consultant can see every port order. Why not introduce them?

Because seeing a table is not owning it. A systems consultant or platform administrator can describe what is stored and for how long, which is useful, but only the CEO can commit the provider's records to a licensing discussion.

Can the provider include the rejection notices it received from other carriers?

Nobody can say before counsel reads the porting and interconnection terms. Those notices originate with the other provider, so the partner records that they exist and leaves the inclusion question to the rights review.

Does the provisioning director ever sign?

Only if they are also the CEO, which happens in some small providers. Otherwise the director convenes and the CEO signs.

Sources

  1. refer.sourcex.si/terms
  2. fcc.gov/enforcement/areas/privacy
  3. numberportability.com/about/npac

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 90% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment