The disclosure should say which number the messages come from
The requirementstatement
The call-to-action should state the phone number or short code the programme will send from.
- Severityseverity
- MediumMEDIUMUsually survives review, but lowers your trust score or invites a manual look you would rather avoid.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- consent disclosure text + campaign number set
- Where it liveslayer
- Consent flowCONSENT_FLOW
- How Ekas settles itdetectability
- AI · crawlCRAWLAI · visionVISION
- Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would. Needs the pixels: a screenshot of the opt-in surface, a scanned paper form, an MMS attachment.
- What the fix involvesfailureClass
- Fix the websiteTERMINAL_WEBSITE
- The fix lives on your site. No amount of rewording the form clears it.
- Who requires itauthorities
- CTIAT-Mobile
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
An unrecognised number is the most common reason a legitimate message gets reported as spam. Telling the consumer at signup which number to expect is what lets them recognise the first message instead of blocking it, and it is the cheapest protection a programme has against its own delivery rates.
How to fix itremediation
Add the sending number or short code to the consent block, and update it if you change numbers. Where you send from a pool, say so and name the range or the short code rather than listing every number. Done when the consumer knows what will appear on their screen.
A compliant exampleexample
Messages come from short code 55512. Msg frequency varies. Msg & data rates may apply.
Common mistakespitfalls
- Publishing a number you later migrate away from is worse than publishing none — treat the disclosure as something to keep current, not to set once.
Notesnotes
Graded MEDIUM, matching the catalog. CTIA lists it as element (2) of the call to action but no provider rejects on it alone, so it is surfaced as an improvement rather than a blocker.
Rules you will hit next
Other consent flow rules at the same severity. A registration is judged as a whole, not rule by rule.
CON-063Labelling the consent control "optional" pre-empts the gating rejectionMediumMEDIUMCON-101"Free" must not be used loosely in the call to actionMediumMEDIUMCON-DISC-NO-POPUPTerms must not be presented only in a pop-upMediumMEDIUMCON-RECORD-FIELDSConsent records must capture the required fieldsMediumMEDIUM
CON-090 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.