Consent collected on a third-party platform must still name the registered brand
The requirementstatement
Consent evidence captured on a third-party platform must show the registered brand as the party the consumer agreed to hear from.
- 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
- opt-in evidence captured on a third-party surface
- Where it liveslayer
- CampaignCAMPAIGN
- How Ekas settles itdetectability
- AI · visionVISION
- Needs the pixels: a screenshot of the opt-in surface, a scanned paper form, an MMS attachment.
- 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
- Twilio
- When it appliesapplicabilityText
- Applies when consent was collected by third party, social and chat.
Why this rule existsrationale
A consumer who opts in inside a marketplace, a social platform or a chat widget is agreeing to hear from whoever is named on that screen. When the screen names only the platform, the consent belongs to the platform and not to the brand sending the messages — which is the consent-transfer problem the framework exists to prevent, arrived at by accident rather than by design.
How to fix itremediation
Configure the third-party surface to name your business in the consent text — most let you set the merchant or sender name — and re-capture the screenshot afterwards. Done when the registered brand name is visible in the same frame as the consent control.
Common mistakespitfalls
- The platform's own branding in the header does not substitute for naming your business in the consent sentence, and a reviewer reads the sentence rather than the chrome.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Twilio | 30927 | Yes |
Rules you will hit next
Other campaign rules at the same severity. A registration is judged as a whole, not rule by rule.
CMP-003Message flow must not begin or end with whitespaceBlockingBLOCKINGCMP-017Every mandatory campaign attribute must be explicitly setBlockingBLOCKINGCMP-024Registration fields must be written in EnglishBlockingBLOCKINGCMP-028Opt-in evidence must be a JPG, PNG or PDF under 500 KBBlockingBLOCKINGCMP-035The description must describe this programme, not messaging in generalBlockingBLOCKINGCMP-037The description must name the business that sends the messagesBlockingBLOCKING
CMP-119 is one of 94 campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.