When a phone-number transfer stalls, the most useful next step is to obtain its exact status from the receiving provider. A rejected account number, an expired authorization, and a completed port with missing texts call for different fixes. Keep one case record so each correction builds on the last.
Ask which stage has actually been reached
Start with the company receiving your number. Use the status route in your order confirmation or authenticated account. T-Mobile's transfer documentation, for example, describes a transfer-status option and a period when both services may be active. Use your own receiving provider's current instructions.
Scroll sideways to read all columns.
| Status or observation | What to establish | Next step |
|---|---|---|
| Order placed; port status unknown | Was a number-transfer request actually submitted? | Obtain its reference and the line to which the number will be assigned. |
| Pending | Is information missing, validation underway, or a transfer date scheduled? | Ask which party owns the next action and when to check again. |
| Rejected | Which field or authorization failed? | Correct that item through the existing case; ask whether resubmission is needed. |
| Accepted or scheduled | What completion time has been communicated? | Keep old service active and follow the agreed device setup sequence. |
| Reported complete; service incomplete | Which calls or messages fail, and on which line? | Record controlled tests and ask for activation or routing investigation. |
Write down the provider's actual wording. These are practical categories, not universal labels used by every carrier. Keep the old line active while the transfer is unresolved. Avoid initiating another port with a second provider, canceling the first order, or deleting an eSIM unless the responsible support team explains how that action addresses the identified problem.
Correct the identified information
Compare the rejected field with the old provider's current account record. Check account number, account holder, billing ZIP code, and the authorization required for that account type. The handset's telephone number and the billing account number may differ. A family-plan member may also lack the authority needed to generate a transfer PIN.
Use the preparation guide for account authority, transfer PINs, and protection settings. If you generate replacement authorization, tell the receiving provider. AT&T's transfer-PIN instructions state that generating a new PIN invalidates earlier ones; an existing request then needs the current PIN. That is a specific reason repeated PIN generation can complicate a case.
If a security lock blocks a requested transfer, remove it only through the old provider's authenticated process. Keep protection on unrelated lines. If the issue is account ownership, ask for the authorized route; guessing credentials or substituting another person's details can create further failures.
Test the reported-complete number systematically
After the provider confirms completion, use consenting contacts for a small set of checks. Record the date, time zone, direction, service used, and result. Check which SIM/eSIM line is selected on a dual-SIM device before interpreting a result.
- Outgoing call: call a contact and ask which number appears. Record whether audio works in both directions.
- Incoming call: have a contact call the transferred number, preferably from a different network. Note which phone rings and whether voicemail answers correctly.
- Carrier text: send and receive an ordinary SMS where supported. Record the message type; an app chat over Wi-Fi tests a different path.
- Voicemail and messaging registration: set up the new mailbox and confirm the intended number in messaging settings.
If calls work but messages fail, follow the SMS, RCS, and iMessage troubleshooting guide. Tell support if failures are limited to one sending network or one message type. A handful of tests gives a useful symptom pattern, not proof that all routes work.
Follow the new provider's Wi-Fi Calling and emergency-address setup instructions. Keep another way to call during interruptions. Do not place a test call to emergency services merely to check a port.
Give support a short, actionable record
Download the porting case log (plain text). It contains a status-question script, correction history, and test fields. Use line labels and contact aliases; omit passwords, transfer PINs, full account numbers, message contents, and private phone numbers from a shared copy.
A useful escalation says: “The receiving provider reports completion at this time. Outgoing calls work; incoming calls from these two tested networks fail. Here are the case reference, timestamps, and exact failure message.” Ask which team is investigating, whether a correction is required from you, and when the next update is expected.
For a persistent U.S. dispute, the FCC's complaint categories include number portability. Preserve support correspondence and describe the unresolved service problem. For immediate loss of essential communications, pursue the provider's urgent support route and a working alternative while the case is handled.
Explore Number Portability guides and the transfer checklist.