The three subscriber-management attributes must be declared true

The requirementstatement

The subscriberOptin, subscriberOptout and subscriberHelp campaign attributes must each be set true, and the HELP declaration must have a keyword set behind it.

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.subscriber_optin + subscriber_optout + subscriber_help
Where it liveslayer: Consent flowCONSENT_FLOW
How Ekas settles itdetectability: DeterministicDETERMINISTIC; Settled in code from the values you submitted. No model involved, no judgement call, same answer every time.
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: TCRPlivoTwilio
When it appliesapplicabilityText: Applies when the use case is NOT M2M.

Why this rule existsrationale

These attributes assert that the programme collects consent, honours opt-outs and answers HELP, which is the baseline claim a campaign makes about itself. Leaving any of them false or unset contradicts every other field in the submission and is a fast, mechanical rejection — Plivo will not even accept the API call. They are also what a carrier relies on when a complaint lands, so declaring HELP with no keyword configured is a claim you will be held to and cannot meet.

How to fix itremediation

Set all three attributes true, declare at least one HELP keyword, and make sure the claims are real — opt-in evidence attached, opt-out keywords honoured by your platform, and a HELP reply configured. Done when the declaration matches what your platform actually does.

A compliant exampleexample

subscriberOptin: true · subscriberOptout: true · subscriberHelp: true · help_keywords: HELP, INFO

Notesnotes

Three catalog rows, one declaration block: CON-010 (opt-in) is universal except M2M; CON-011 (opt-out) additionally exempts 2FA, which the check applies rather than the applicability tag, since only part of the rule is exempt; CON-012 (help) is universal. The registry spells that use case TWO_FACTOR_AUTH; the catalog spells it 2FA. CON-012 also requires a HELP reply body behind the keyword set — that half is CON-HELP-BACKED, so this rule stops at the keyword set to avoid reporting the same missing message twice. Whether HELP is really answered at runtime is UNDETECTABLE_PRE_SUBMISSION and is not claimed here.

Rules you will hit next

One other rule reads campaign.subscriber_optin + subscriber_optout + subscriber_help. 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-175Subscriber attributes must be true where the API accepts nothing elseBlockingBLOCKING CON-008The live CTA and the declared message flow must say the same thingBlockingBLOCKING 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-010 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

The three subscriber-management attributes must be declared true

Why this rule existsrationale

How to fix itremediation

Notesnotes

Rules you will hit next

Reading the rules is the easy part.