A ported number is a new subscriber

The requirementstatement

A fresh opt-in must be obtained when a subscriber ports their number between carriers.

Severityseverity: MediumMEDIUMUsually survives review, but lowers your trust score or invites a manual look you would rather avoid.
When it bitesphase: After you are livepostFalls due once you are sending: STOP handling, quiet hours, suppression, record retention.
What is checkedobject: subscriber port event against consent status
Where it liveslayer: OperationalOPERATIONAL
How Ekas settles itdetectability: Post-submissionUNDETECTABLE_PRE_SUBMISSION; The subject does not exist yet at submission time: a reply window, an expiring PIN, a queue position. Reported with its deadline.
What the fix involvesfailureClass: Wait on someone elseTERMINAL_EXTERNAL; Needs an external system or a waiting period, such as IRS propagation, a vetting result, or a carrier queue.
Who requires itauthorities: CTIAMMA
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

Porting is one of the routes by which the person behind a number changes without any signal in the brand's own data, and short-code programmes in particular are expected to re-permission across it. Nothing in the sending platform surfaces a port, so a list treats the number as continuously consenting while the handset it reaches may have changed hands entirely.

How to fix itremediation

Where your platform exposes port or carrier-change events, treat one as expiring the consent and re-confirm before the next send. Where it does not, lean on the deactivation feeds and the reassigned-numbers query, which catch most of the same population. Done when a carrier change does not silently preserve consent.

Check this yourselfattestation

No tool can settle this one for you. Here is the check, and what wrong looks like.

Does your provider surface porting or carrier-change events at all?

1Ask. Most do not.
2Where it does, treat a port as expiring the consent and re-confirm before the next send.
3Where it does not, lean on the deactivation feeds and the reassigned-numbers query, which catch most of the same population.

What wrong looks like: Nothing in the sending platform surfaces a port, so the list treats the number as continuously consenting while the handset it reaches may have changed hands entirely.

Notesnotes

A carrier event we never see. What the user has to check is whether their provider surfaces porting at all — most do not, and where that is true this obligation is discharged in practice by OPS-083 and OPS-087 rather than directly.

Rules you will hit next

Other operational rules at the same severity. A registration is judged as a whole, not rule by rule.

OPS-032A help request containing a stop-word is not an opt-outMediumMEDIUM OPS-042Somebody has to own revocations that arrive in conversationMediumMEDIUM OPS-050The opt-out confirmation is worth sending inside five minutesMediumMEDIUM OPS-051Only ask which messages to stop when there is more than one kindMediumMEDIUM OPS-057Log the sends you did not makeMediumMEDIUM OPS-062An opted-out consumer must be able to come backMediumMEDIUM

All operational rules

OPS-089 is one of 139 operational rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.