No fake-prize, impersonation or advance-fee patterns

The requirementstatement

Campaign content must not promote fake prizes, impersonated brands and advance-fee solicitations.

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.sample[] + campaign.message_flow
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: Hard stopHARD_STOP; Not remediable. Resubmitting will not help, and anyone offering to fix it is selling you a rejection.
Who requires itauthorities: Twilio
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

These three patterns share a mechanism — manufacture a reason the recipient is owed something, then extract a payment or a credential to release it — and Twilio screens them together because they are what its fraud code was written about. They are separated from general deception because they are recognisable by shape rather than by verification: nobody has to establish what the business really does to know that a prize nobody entered for is not real. The registration-time signal is often the brand record itself, where the details do not match anything a search would find.

How to fix itremediation

Remove any sender identity other than the registered brand, any prize claim with no promotion behind it, and any payment asked for before a benefit is delivered. Where you act for a named principal, say so in the description and register under a brand that matches what the recipient will see. Done when the sender name in every sample is the brand on the registration.

Provider rejection codescodes

The code you get back when this rule is what failed, and whether that provider lets you resubmit.

Provider	Code	Resubmit
Twiliogen2	30959	No

Notesnotes

Twilio 30959 is "a permanent disqualification from A2P 10DLC messaging" — the rejection ends the account's route, not just the campaign, so this must never be surfaced as something to edit and resubmit.

Rules you will hit next

6 other rules read campaign.description + campaign.sample[] + 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.

MSG-137No unsolicited bulk messagingBlockingBLOCKING MSG-161SHAFT screening covers every campaign field, not a sample of themBlockingBLOCKING MSG-164No underage, non-consensual or illegal sexual themesBlockingBLOCKING MSG-170No content promoting, glorifying or inciting violenceBlockingBLOCKING MSG-182No explosives, fireworks or pyrotechnics contentBlockingBLOCKING MSG-183No weapons that are not legal in all fifty statesBlockingBLOCKING

All message content rules

MSG-245 is one of 122 message content rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.