Platform-hosted evidence must show the end business, not the platform

The requirementstatement

Where consent is collected on a platform, agency, or franchisee surface, the evidence must identify the end business the consumer is agreeing 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: consent artifact branding
Where it liveslayer: Consent flowCONSENT_FLOW
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: TwilioAT&T
When it appliesapplicabilityText: Applies when consent was collected by third party, imported list, franchise or agent and chat.

Why this rule existsrationale

A consumer looking at a form carrying only the marketing platform's branding cannot tell whose messages they just agreed to, so the consent names nobody and the brand that later sends is not the brand they said yes to. This is the honest version of the consent-transfer problem: the form genuinely is the platform's, so screenshotting it as-is feels like screenshotting the opt-in, and nothing on screen tells you it is not.

How to fix itremediation

Re-capture the evidence with the end business's name or logo inside the same frame as the consent control — usually by setting the platform form's header or logo field, or by capturing the branded page the widget is embedded in rather than the bare widget. Done when somebody who has never heard of your platform can name the business from the image alone.

Common mistakespitfalls

Naming the brand in the campaign record does not fix the artifact — the reviewer is judging the picture, not the field beside it.
A franchisee form that names only the franchisor fails the same way as an ISV form: the entity on the artifact must be the entity registered.

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	30506	Yes

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-008The live CTA and the declared message flow must say the same thingBlockingBLOCKING CON-010The three subscriber-management attributes must be declared trueBlockingBLOCKING CON-013Subscriber attributes must agree with the message bodies suppliedBlockingBLOCKING CON-023Evidence URLs must resolve without a loginBlockingBLOCKING CON-024The opt-in URL must serve a certificate that verifiesBlockingBLOCKING CON-027The opt-in URL must land on a page that carries the opt-inBlockingBLOCKING

All consent flow rules

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