Campaign auto-renewal must be set deliberately

The requirementstatement

The autoRenewal setting must be chosen deliberately — true renews monthly, false deactivates at cycle end.

Severityseverity
MediumMEDIUMUsually survives review, but lowers your trust score or invites a manual look you would rather avoid.
When it bitesphase
Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject
campaign.auto_renewal
Where it liveslayer
OperationalOPERATIONAL
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
TCR
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

Left unconsidered, this setting either bills you monthly forever or silently deactivates a live campaign at the end of its cycle, taking your traffic down with no rejection to explain it. It is one of the few settings whose default choice has an ongoing cost either way.

How to fix itremediation

Set auto-renewal true for an ongoing programme so it does not deactivate mid-flight, and false only for a genuinely time-boxed campaign you intend to end.

A compliant exampleexample

Ongoing marketing programme → autoRenewal: true.

Rules you will hit next

Other operational rules at the same severity. A registration is judged as a whole, not rule by rule.

All operational rules

OPS-161 is one of 139 operational 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.