The opt-in language must actually say SMS or text message

The requirementstatement

The consent wording must name text messaging explicitly rather than referring generally to being contacted.

Severityseverity: BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
When it bitesphase: Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject: consent disclosure text
Where it liveslayer: Consent flowCONSENT_FLOW
How Ekas settles itdetectability: AI · crawlCRAWL; Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would.
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: TwilioCTIA
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

Consent runs to a channel. Agreeing to be "contacted" or to "receive updates" does not agree to texts, and the carriers reading that wording cannot tell whether the consumer expected a phone call, an email, or nothing at all. Twilio rejects it under a code whose whole description is that the opt-in flow does not explicitly mention SMS — it is a wording defect with a one-word fix that brands miss because they know what they meant.

How to fix itremediation

Put the words "text messages" or "SMS" into the consent sentence itself. Done when the sentence names the channel without relying on the page around it — a heading saying "SMS signup" above a box that says "keep me updated" does not carry it.

A compliant exampleexample

I agree to receive recurring automated marketing text messages (SMS) from Acme Coffee.

Common mistakespitfalls

An email opt-in reused for SMS is the usual source: the wording was written for a newsletter and the channel word was never added.

Provider rejection codescodes

The code you get back when this rule is what failed, and whether that provider lets you resubmit.

Provider	Code	Resubmit
Twiliogen2	30513	Yes

Rules you will hit next

6 other rules read consent disclosure text. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.

CON-080The disclosure must name the programme the consumer is joiningBlockingBLOCKING CON-123Every entity allowed to send must be named in the consentBlockingBLOCKING CON-125Consent must not be claimed on behalf of unnamed partnersBlockingBLOCKING CON-DISC-BRANDConsent disclosure must identify the sending brand by nameBlockingBLOCKING CON-DISC-NOT-CONDITIONPromotional consent must state it is not a condition of purchaseBlockingBLOCKING CON-DISC-PURPOSEConsent disclosure must state the message type or purposeBlockingBLOCKING

All consent flow rules

CON-060 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.