Subscriber attributes must be true where the API accepts nothing else

JSONMarkdown

The requirementstatement

On a CSP whose API accepts only true for the subscriber opt-in, opt-out and help attributes, none of the three may be submitted false.

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
CampaignCAMPAIGN
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
Plivo
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

This is a schema rejection rather than a vetting one: the call fails before the campaign exists, so there is no rejection reason to read and no campaign record to inspect. It bites exactly the submissions that are entitled to say false — a two-factor programme relying on the opt-out exemption TCR grants finds that its provider never implemented the exemption.

How to fix itremediation

Send true for all three attributes on this provider, and back each one with real handling — declared keywords and a reply body — rather than leaning on the use-case exemption. Done when the payload carries three true values and three configured behaviours.

A compliant exampleexample

subscriber_optin: true · subscriber_optout: true · subscriber_help: true

Notesnotes

Plivo publishes "Allowed value: true" for all three fields. The provider condition is applied inside the check rather than as a `providers` tag: a tag resolves YES when the submission target is unknown, which would make this rule contradict CON-010's two-factor carve-out on every registration that has not chosen a provider yet. Passing on an unknown target is the honest reading — the exemption is real everywhere except 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.

CON-010The three subscriber-management attributes must be declared trueBlockingBLOCKINGCMP-003Message flow must not begin or end with whitespaceBlockingBLOCKINGCMP-017Every mandatory campaign attribute must be explicitly setBlockingBLOCKINGCMP-024Registration fields must be written in EnglishBlockingBLOCKINGCMP-028Opt-in evidence must be a JPG, PNG or PDF under 500 KBBlockingBLOCKINGCMP-035The description must describe this programme, not messaging in generalBlockingBLOCKING

All campaign rules

CMP-175 is one of 94 campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.

Talk to UsHow 10DLC works