The live CTA and the declared message flow must say the same thing

The requirementstatement

The consent wording quoted in the message flow must be the wording actually printed on the live opt-in surface.

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: campaign.message_flow vs live opt-in page
Where it liveslayer: Consent flowCONSENT_FLOW
How Ekas settles itdetectability: AI · crawlCRAWL; Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would.
What the fix involvesfailureClass: Fix the fieldRETRY_FIELD; A better value in the form fixes it. Ekas can rewrite it and re-check.
Who requires itauthorities: BandwidthTwilioTCR
When it appliesapplicabilityText: Applies when consent was collected by web form, checkout, account settings, third party, chat, social and email.

Why this rule existsrationale

The flow is the brand's account of the consent and the page is the consent itself, so where they differ the page wins and the registration describes something that does not happen. It is rarely dishonest: the flow was written from the disclosure the team intended to ship, and the page was changed afterwards by someone who never saw the campaign record.

How to fix itremediation

Copy the consent sentence off the live page into the message flow verbatim, rather than paraphrasing it. Where the page is the thing that is wrong, fix the page first and then quote it. Done when the quoted sentence and the printed one match word for word.

A compliant exampleexample

Customers opt in at https://acmecoffee.com/checkout by ticking an unchecked box reading: "Text me Acme Coffee offers and rewards updates." — quoted exactly as printed.

Common mistakespitfalls

Tidying the punctuation or capitalisation while copying is enough to read as a different disclosure to a reviewer comparing them side by side.

Notesnotes

The catalog classes this DETERMINISTIC, and it would be, given a crawl that says WHICH page each block of text came from. The registry carries one undifferentiated websiteText, so a string comparison cannot tell "the CTA was reworded" from "we fetched the homepage and the CTA is at /checkout" — and failing a compliant registration for the second is the worse error. Authored as judged until the crawler carries a per-page map; both audits the catalog asks for (CON-009) fall out of the same comparison.

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-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 CON-034The business name on the artifact must match the registered brandBlockingBLOCKING

All consent flow rules

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