Opt-in evidence must be the live surface, not a mockup of it

The requirementstatement

The artifact must depict the brand's own working opt-in surface — not stock imagery, a design template, or a mockup of a page that does not exist yet.

Severityseverity: HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
When it bitesphase: Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject: opt-in screenshot vs live page
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: Twilio
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

A designed mockup shows what the brand intends to build, and reviewers approve against what exists. When the campaign starts sending, the real page is whatever was actually shipped, and nobody has ever checked it. Honest brands produce these because the compliance step lands before the launch, which is why the fix is usually a date rather than a design change.

How to fix itremediation

Capture the page as it renders in a browser today, at the URL you submitted, with your own copy and product names in it. If the surface is genuinely not live yet, say so in the campaign description and register once it is — a mockup submitted without that statement reads as an attempt to pass off a plan as a page.

Common mistakespitfalls

A Figma frame and a browser screenshot look similar at a glance; a reviewer spots the missing browser chrome, placeholder copy, and lorem-ipsum product names immediately.

Provider rejection codescodes

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

Provider	Code	Resubmit
Twiliogen1	30909	Yes

Notesnotes

Marked [INFERRED] in the research: derived from AWS's placeholder-text ban on samples rather than published in these words. Cite the underlying obligation — evidence must depict the live consent surface — if a user pushes back on the rule as stated.

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-017An offline opt-in still needs a findable business behind itHighHIGH CON-038Verbally-collected informational campaigns need the mockup and the messagesHighHIGH CON-042The phone field must be optional on a general-purpose formHighHIGH CON-044A required phone field must carry an SMS disclaimer beside itHighHIGH CON-064A kiosk or terminal must not pre-fill the consumer's numberHighHIGH CON-071The decline path must be as usable as the accept pathHighHIGH

All consent flow rules

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