A port is usually rejected because the details on the request don't exactly match the losing provider's account records: the account name, the account number, the PIN or the service address. Get a copy of the current bill, match every field and resubmit.

The common reasons

  • Name mismatch. The authorized name differs from the account holder, even by a suffix like LLC.
  • Wrong account number or PIN. Many providers have a separate porting PIN from the login password.
  • Address mismatch. The service address on the request isn't the one on file.
  • Number isn't portable. A number on a short contract or a different line type.
  • Pending order. A change on the account while the port runs.
  • Wrong number type. A landline vs a mobile or VoIP number.

A fix list

  1. Pull the latest bill or account page and copy every field exactly.
  2. Ask the losing provider for the porting PIN.
  3. Make sure no other change is open on the account.
  4. Resubmit once, with corrections, and keep the rejection text.
  5. Keep the old service active until the port completes.

Plan texting around the port

While a number is porting, texting can pause. Registration follows the number, so check that your campaign is attached to the number after it lands. Our Twilio number port checklist walks through the full set of steps for that provider, and preserving opt-out history matters before you send a single text from the new account.

Before you move

ItemCheck
Opt-out listExport and import it
Consent recordsKeep them in your own system
RegistrationFile it with the new provider
NumbersList which ones will port

Ready stores opt-outs, and you can check a number with GET /v1/opt-outs/:phone before a send from another tool or after a migration.

The takeaway

A rejected port is almost always a typo with consequences. Match the bill, get the PIN and keep the old service live until the new one works. The migration guide covers the code side.