# CMP-119 — Consent collected on a third-party platform must still name the registered brand

> Consent evidence captured on a third-party platform must show the registered brand as the party the consumer agreed to hear from.

- **Rule ID:** CMP-119
- **Layer:** Campaign (`CAMPAIGN`)
- **Checks:** `opt-in evidence captured on a third-party surface`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** AI vision over a consent artifact (screenshot, scan, MMS media)
- **Fix type:** Supply evidence only you hold
- **Required by:** Twilio
- **Applies:** Applies when consent was collected by third party, social and chat.
- **Canonical URL:** https://ekas.io/rules/10dlc/campaign/cmp-119/

## Why this rule exists

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 it

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 mistakes

- 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 codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio | `30927` | yes |