The described opt-in method must match the evidence supplied
The requirementstatement
The collection method described in the message flow must be consistent with the artifact and the website.
- 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
- campaign.message_flow + consent artifact
- Where it liveslayer
- Consent flowCONSENT_FLOW
- How Ekas settles itdetectability
- AI · formAI_FORM
- A semantic question about what you wrote: whether a description matches a use case, whether a name looks like a filed entity. Judged by a model against written criteria.
- 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
- TCRTwilioBandwidth
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
A mismatch between the description and the evidence reads to a reviewer as either carelessness or misdirection, and both get rejected. It also usually means one of your real collection surfaces is undocumented and therefore unaudited.
How to fix itremediation
Make the flow describe the same method the evidence shows. If you genuinely collect consent several ways, describe each one and attach evidence for each — partial evidence is what triggers the mismatch.
A compliant exampleexample
Consent is collected two ways: (1) the web form at acmecoffee.com/signup [screenshot attached], and (2) verbally at our counter using the attached script.
Rules you will hit next
5 other rules read campaign.message_flow + consent artifact. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
CMP-065A hosted artifact is required when the opt-in is not publicly crawlableBlockingBLOCKINGCON-040The consent basis must be an explicit opt-in, not an implied oneBlockingBLOCKINGCON-ART-001An artifact proving consent collection must be attachedBlockingBLOCKINGCON-KEYWORD-CTAKeyword opt-in requires the advertised call to actionBlockingBLOCKINGCON-VERBAL-SCRIPTVerbal opt-in requires the documented scriptBlockingBLOCKINGCON-017An offline opt-in still needs a findable business behind itHighHIGH
CON-FLOW-METHOD-MATCH is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.