A legitimately shared number needs a register of who sends on it

The requirementstatement

Where a number or short code is shared under an approved arrangement, documented records of every message sender operating on it must be immediately available.

Severityseverity: HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
When it bitesphase: After you are livepostFalls due once you are sending: STOP handling, quiet hours, suppression, record retention.
What is checkedobject: shared-number sender register
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: Supply evidenceTERMINAL_EVIDENCE; Needs proof only you hold: a screenshot, a recording, a scan of the form people signed.
Who requires itauthorities: T-MobileCTIA
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

Sharing is permitted only where it can be unpicked, and the register is what unpicks it: a complaint about one message has to resolve to one sender within the time a carrier gives you, which is short. Without it a shared arrangement is indistinguishable from the sub-aggregation the previous rule prohibits, and it will be treated as such.

How to fix itremediation

Keep a current list of every sender on the shared number, with the approval that permits the arrangement, somewhere you can produce it the same day. Done when a message can be attributed to a sender without asking anybody.

Check this yourselfattestation

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

If a number you send from is shared, was the arrangement approved — and could you attribute one message to one sender the same day?

1Confirm the sharing arrangement was approved in the first place. An undocumented one is a different and worse finding.
2Keep a current list of every sender on the number, with the approval that permits it, where you can produce it same-day.
3Test it: pick a message and attribute it without asking anybody.

What wrong looks like: A complaint has to resolve to one sender inside the short window a carrier gives you. Without the register, a permitted shared arrangement is indistinguishable from prohibited sub-aggregation and gets treated as such.

Notesnotes

A register inside the operator, and no registration field even says the number is shared. What the user has to confirm is that the sharing arrangement was approved in the first place — an undocumented one is OPS-141, not this rule.

Rules you will hit next

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

OPS-034A programme in another language still owes the English keywordHighHIGH OPS-035The mandatory keywords must work over MMS tooHighHIGH OPS-044Suppression is brand-wide, not per numberHighHIGH OPS-047A state may give you less time than the federal limitHighHIGH OPS-052Silence after a scope question revokes everythingHighHIGH OPS-053A STOP answering a scope question must not be answered with anotherHighHIGH

All operational rules

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