Consent disclosure must identify the sending brand by name
The requirementstatement
The disclosure at the point of consent must name the business that will send the messages.
- 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 · 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
- CTIATCRTwilioT-Mobile
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Put the registered brand name inside the consent sentence itself, not just in the page header or logo. Use the same name you registered — if you registered "Acme Coffee Co, LLC" with DBA "Acme Coffee", either is fine, but a third marketing alias is not.
A compliant exampleexample
By checking this box, you agree to receive recurring automated marketing text messages from Acme Coffee at the number provided. Consent is not a condition of any purchase. Message frequency varies. Message and data rates may apply. Reply STOP to unsubscribe or HELP for help. See our Terms of Service and Privacy Policy.
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-DISC-BRAND is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.