The programme must be application-to-person, not personal messaging

JSONMarkdown

The requirementstatement

A campaign must describe application-to-person business messaging, not person-to-person or influencer-to-follower messaging.

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.description + campaign.message_flow
Where it liveslayer
CampaignCAMPAIGN
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
TwilioAWS
When it appliesapplicabilityText
Applies when the use case is NOT SOCIAL.

Why this rule existsrationale

10DLC exists for business messaging with consent behind it. A description reading as a person texting their contacts, or a public figure broadcasting to followers, does not fit the framework — and influencer programmes in particular usually have no per-number consent record at all, because the audience was acquired as followers rather than as subscribers.

How to fix itremediation

Describe the programme as business messaging from the registered entity to consumers who opted in with that entity, and say where those consumers opted in. Done when the description names the business as sender and an opt-in surface as the source of the list. If the programme genuinely is a public figure messaging followers, the SOCIAL use case is the route, not a reworded description.

A compliant exampleexample

Acme Coffee sends order updates and promotions to customers who opted in at checkout — not "I text my followers about new drops".

Notesnotes

Catalog CMP-046 flags the tension with the TCR SOCIAL use case, which Vonage restricts to exactly public figures, platforms and influencers (see CMP-140). Tagged to exclude SOCIAL so the rule does not reject the one use case built for it. SOCIAL is not in USE_CASE_REQUIREMENTS yet, so today the tag documents the carve-out rather than firing.

Rules you will hit next

2 other rules read campaign.description + campaign.message_flow. 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-089Some opt-in must be described somewhereBlockingBLOCKINGOPS-QUIET-HOURS-DISCLOSEDQuiet-hours handling should be disclosed for promotional programmesMediumMEDIUMCMP-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 KBBlockingBLOCKING

All campaign rules

CMP-045 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