Transactional campaigns must contain no promotional element
The requirementstatement
A campaign declared transactional or informational must have no coupon, offer, upsell, or promotional content in its samples.
- 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.sample[] + campaign.usecase
- Where it liveslayer
- Message contentMESSAGE_CONTENT
- 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
- TCRTwilioBandwidthAWS
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
Transactional use cases receive better throughput and lighter filtering precisely because they are not marketing. A single coupon inside an otherwise transactional set means the campaign obtained that treatment under a false description, which is why one offending sample is enough to reject.
How to fix itremediation
Remove promotional content from transactional samples, or move the campaign to MIXED and collect promotional-grade consent.
A compliant exampleexample
ACCOUNT_NOTIFICATION: "Acme Coffee: your payment of $24.50 was received." — no offer attached.
Common mistakespitfalls
- A discount code appended to an order confirmation converts the whole campaign into marketing.
Rules you will hit next
3 other rules read campaign.sample[] + campaign.usecase. 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-141Sample count must meet the minimum for the declared use caseBlockingBLOCKINGMSG-155Sweepstakes content requires the sweepstakes use caseBlockingBLOCKINGMSG-SAMPLES-USECASESample messages must match the declared use caseBlockingBLOCKINGMSG-008Opt-in confirmation must be 20–255 charactersBlockingBLOCKINGMSG-009HELP reply must be 20–255 charactersBlockingBLOCKINGMSG-011Opt-out confirmation must be 20–255 charactersBlockingBLOCKING
MSG-152 is one of 122 message content rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.