A number transfer is one of the few consumer requests with a federal deadline attached, and that deadline gets quoted back at people constantly. Someone in Los Angeles moves a 617 number to a new wireless carrier, submitting the request at 11:40 on a Tuesday morning, Pacific time. Wednesday afternoon the old handset still rings, the app shows the transfer as pending, and a support agent says federal rules require a port to finish in one business day.
That reply mixes together two things the rule keeps apart. The one-business-day figure is real, and it is written into the Office of the Federal Register's current text of 47 CFR 52.35, Porting intervals. But the sentence carrying the figure names the transfer types it governs, and a handset-to-handset move between two wireless carriers is not among them. Where the figure does apply, the business day it describes begins on a clock tied to the telephone number rather than to the person holding the phone. Same figure, two readings, and the wrong one turns an ordinary wait into an escalation with nowhere to go.
The Sentence Everyone Quotes, and the Two Words Inside It
The consumer-facing version comes from the FCC consumer guide, Porting: Keeping Your Phone Number When You Change Providers: “FCC rules require simple ports, which generally do not involve more than one line or more complex adjustments to telephone switching equipment, to be processed in one business day.” Read quickly, that lands as a universal promise. Read closely, it is conditioned on the word simple, and it is quiet about which pair of services sits on either end of the move.
The rule supplies the missing half. Paragraph (a) of section 52.35 reads: “All telecommunications carriers required by the Commission to port telephone numbers must complete a simple wireline-to-wireline or simple intermodal port request within one business day unless a longer period is requested by the new provider or by the customer.”
Two categories, named explicitly, and everything the figure covers has to fit one of them. The closing clause matters as well: the interval bends when a longer period is requested by the new provider or by the customer, so a scheduled future due date violates nothing.
Three Kinds of Intermodal Port, and the Transfer That Is Not One of Them
Everything now turns on what intermodal covers, and the section defines the term itself rather than leaving it to industry usage. Paragraph (e)(2) provides that the term “intermodal ports” includes ... “Wireline-to-wireless ports” ... “Wireless-to-wireline ports” ... and “Ports involving interconnected VoIP service.”
Three members are enumerated. A move from a landline or cable-phone account to a mobile carrier is in, a move from a mobile carrier back to a landline is in, and anything touching interconnected VoIP is in. A switch from one wireless carrier to another is not one of the three, and it is not a wireline-to-wireline request either. The verb is includes, not means, so the list reads as illustrative rather than closed; intermodal itself denotes a move between two modes. So the sentence that produces the one-business-day figure reaches past the most common carrier switch in the country.
The Commission described that landscape when it adopted the interval. In the FCC Report and Order FCC 09-41, Local Number Portability Porting Interval and Validation Requirements, paragraph 3 records that “The wireless industry established a voluntary standard of two and one-half hours for wireless-to-wireless ports.” Footnote 34 then draws the line around what the order settled: “In this Order, we do not address whether it is necessary for the Commission to adopt a rule codifying the wireless industry's voluntary two and one-half hour standard for wireless-to-wireless ports.”
So the reference figure for a phone-to-phone switch is two and one-half hours, sourced to an industry commitment rather than to the section that produced the one-business-day number. That is far tighter than a business day. A stalled wireless-to-wireless transfer is therefore not late against the interval in section 52.35 on its second day, and whether any other Commission rule sets one was not checked here. It is stuck on something else, usually validation.
One Business Day Is Not Twenty-Four Hours
For the transfers the interval does reach, the next question is what a business day is made of, and paragraph (a) answers in its own words: “The traditional work week of Monday through Friday represents mandatory business days and 8 a.m. to 5 p.m. represents minimum business hours, excluding the current service provider's company-defined holidays.”
Three constraints hide in that sentence. Weekends are not business days. The protected window is a nine-hour stretch, not a full day. And the holidays that stop the clock belong to the company losing the number, not the company gaining it and not any federal calendar, so checking a stalled transfer against a public holiday list can produce the wrong conclusion.
Then comes the cutoff, which is the part that most often explains an unexpected extra day: “An accurate and complete Local Service Request (LSR) must be received by the current service provider between 8 a.m. and 1 p.m. local time for a simple port request to be eligible for activation at midnight on the same day.” And the consequence of missing it: “Any simple port LSRs received after this time will be considered received on the following business day at 8 a.m. local time.” The section's source line records a 2015 amendment at 80 FR 66480; which sentences it added was not verified here.
A request handed over at five past one on a Tuesday is treated as arriving Wednesday morning and becomes eligible for activation at midnight Wednesday. The same submission on a Friday is treated as arriving Monday morning and activates at midnight Monday. Add one company-defined holiday on that Monday and it lands Tuesday. None of that is a fault, and none of it is visible from the customer's side, which is why the wait reads as a malfunction.
Whose One O'Clock
The cutoff sentence says local time, and a reader naturally supplies the only local time they have, which is their own. The section defines the phrase instead, in the definitions paragraph that sits after the operative language. Paragraph (e)(1) provides that the term “local time” means “the predominant time zone of the Number Portability Administration Center (NPAC) Region in which the telephone number is being ported; and” the enumeration of intermodal ports follows.
The clock belongs to the number. Which region a number sits in comes from the NPAC map. The Number Portability Administration Center's Regions page states that “The U.S. NPAC consists of seven regions that are delineated by state borders as noted below.” The Northeast region is listed as Connecticut, Maine, Massachusetts, New Hampshire, New York, Rhode Island and Vermont. Every listed member observes Eastern time, so the predominant zone for that region is not in doubt.
Apply that to the case at the top. A 617 number is a Massachusetts number, which places it in the Northeast region, which makes the cutoff 1 p.m. Eastern. On the customer's own clock in Los Angeles, that is 10 a.m. Pacific. The request submitted at 11:40 a.m. Pacific arrived at 2:40 p.m. Eastern, past the cutoff. Under the rule it counts as received the next business day at 8 a.m., and the earliest activation was midnight that following day. The transfer was on schedule the whole time the app said pending.
The mistake runs the other way too: a Boston customer moving a California number gets a cutoff of 1 p.m. Pacific, or 4 p.m. on their own clock. Find the state the number belongs to, find its NPAC region, and read the cutoff on that region's clock.
Simple, Non-Simple, and the Four-Business-Day Branch
The word simple carries as much weight as the transfer type, and a four-part test stands behind it. Footnote 5 of FCC 09-41 sets it out: “As the Commission previously has explained, simple ports are those ports that: (1) do not involve unbundled network elements; (2) involve an account only for a single line; (3) do not include complex switch translations (e.g., Centrex, ISDN, AIN services, remote call forwarding, or multiple services on the loop); and (4) do not include a reseller.”
The second and fourth conditions are the ones ordinary consumers trip over. A family plan with several lines on one account is not an account for a single line, so moving one of those numbers is not a simple port. A mobile service bought from a reseller riding on a larger network is a reseller arrangement, which also knocks the request out of the simple category, and plenty of low-cost brands sit there.
Falling out of simple does not remove a deadline; it changes which one applies. Paragraph (d) provides that carriers “must complete a non-simple wireline-to-wireline or non-simple intermodal port request within four business days unless a longer period is requested by the new provider or by the customer.” Four business days, counted the same careful way, with the same weekends and company-defined holidays taken out.
A second four-business-day branch exists for a different reason. Paragraph (c) provides that “Unless directed otherwise by the Commission, any telecommunications carrier granted a waiver by the Commission of the one-business day porting interval described in paragraph (a) must complete a simple wireline-to-wireline or simple intermodal port request within four business days unless a longer period is requested by the new provider or by the customer.” The consumer guide describes a different waiver: “some rural wireline service providers may obtain waivers for the porting requirement from state authorities” and their customers “may be unable to port their number to a new provider.” That is a state waiver of the requirement itself, not the Commission waiver of the interval in paragraph (c).
The Fourteen Fields a Carrier May Require
When a wireless-to-wireless transfer stalls well past two and one-half hours, validation is the usual reason, and the rules limit what can be demanded. The Office of the Federal Register's text of 47 CFR 52.36, Standard data fields for simple port order processing provides in paragraph (a) that carriers “may require only the data” in the two subsections that follow. Paragraph (b) enumerates fourteen standard data fields, beginning with the ported telephone number and the account number, then the zip code, company code, new network service provider, desired due date, purchase order number, version, number portability direction indicator, customer carrier name abbreviation, requisition type and status, activity, telephone number of initiator, and agency authority status.
Two of the fourteen cause most of the trouble, because a mobile account usually displays more than one value that looks like the right answer. The account number field wants the billing account identifier, which on many wireless bills is neither the ten-digit mobile number nor the customer service PIN. Supplying the wrong one produces a mismatch rejection that reads as an unexplained stall.
The passcode is the other one, and it is conditional rather than mandatory. Paragraph (c) reads: “The Passcode field shall be optional unless the passcode has been requested and assigned by the end user.” Once a customer has set a transfer passcode on the account, that field stops being optional and the request has to carry it. Someone who enabled a port-out passcode months earlier and then submitted a transfer without it has handed over an incomplete request, and an incomplete request is not the accurate and complete LSR that starts any clock.
A Check Order That Follows the Rule
Working the problem in the rule's own order keeps the conversation with support on ground that can be settled. Start by naming both ends of the transfer. If both are wireless carriers, the one-business-day figure is beside the point; a transfer sitting well past two and one-half hours is most likely failing validation rather than waiting in a queue.
If one end is a landline, a cable phone line or an interconnected VoIP service, the interval applies, and the useful question is when the old provider received an accurate and complete LSR. That timestamp, not the moment the customer pressed submit in an app, is what the cutoff measures. Ask for it, work out the number's NPAC region, and read 1 p.m. on that region's clock. Then test the request against the definition of simple: more than one line on the account, or a reseller brand in the chain, moves the deadline to four business days without anyone doing anything wrong. Finally, ask which field failed, because the answer has to be one of the fourteen the rules allow, and whether a passcode was assigned on the account earlier.
One point is settled and worth saying plainly to a retention agent: an unpaid balance is not a ground for refusal. The consumer guide states that “Once you request service from a new company, your old company cannot refuse to port your number, even if you owe money for an outstanding balance or termination fee.” The debt survives the transfer; the transfer does not wait on the debt. The same habit of pinning down which event starts a window appears in the walkthrough of counting business days from a dispute notice and in the account recovery timing walkthrough.
When This Doesn't Apply
Geography can make the whole question moot. The consumer guide states that “If you are moving to a new geographic area, you may not be able to keep your current phone number when changing providers.” A rate-center mismatch is a hard stop rather than a delay, and no interval fixes it.
Direction matters too, even inside the covered categories. The same guide notes that “However, porting from wireline to wireless service may still take a few days.” Treat the interval as the enforceable floor and that sentence as the practical range.
Waivers and phase-ins move the figures. Paragraph (c) puts waiver holders at four business days, and paragraph (b) provides that “Small providers, as described in the 2009 LNP Porting Interval Order, must comply with this section by February 2, 2011.” Neither condition is visible from a customer-facing app, so the old provider's identity has to be established before any figure is treated as binding.
Three limits on the research behind this piece are worth stating. The NPAC Regions page publishes region membership by state but not a time zone for each region, so the predominant zone has to be inferred from membership. That inference is clean for the Northeast region, where every listed state observes Eastern time, and reasonable for the West Coast region, which is dominated by California and Nevada. It is not clean for the Western region, whose listed states straddle Mountain, Pacific and Central time, and no predominant zone is assigned to it here. Next, whether a later Commission action or another porting section has since set an enforceable wireless-to-wireless interval was not checked, so a reader relying on the two-and-one-half-hour figure in a formal complaint should verify it first. Last, the 2015 amendment at 80 FR 66480 was not read in its own right, so nothing above rests on which sentences it added; only the current rule language is relied on.
None of this decides a case where the request itself was not accurate and complete. The interval, the cutoff and the four-business-day branches all begin measuring from a valid request in the old provider's hands. A transfer held up by an account number mismatch or a missing passcode has no clock running at all, which is why the field-level question beats the deadline question.
Comments
Post a Comment