Samples must not be framed as test, demo or machine-to-machine traffic

The requirementstatement

Sample messages and the campaign description must describe real messages sent to real subscribers, not test traffic, demonstrations, or machine-to-machine signalling.

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.description
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: AWS
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

10DLC is a production registration: the throughput and the trust that come with it are granted on the basis that a person receives each message and consented to it, so a campaign that says it is for testing is asking for a production route to carry something that is not production traffic. Developers land here honestly, registering during integration with exactly the samples their test harness sends — and reviewers cannot tell that from a sender who intends to keep the campaign in test framing indefinitely, so they refuse it.

How to fix itremediation

Replace the samples with the messages the campaign will send once it is live, and rewrite the description so it names the real audience and what they will receive. Done when nothing in the submission would still be true if the word "test" were the point — a reviewer should not be able to tell you registered during integration.

A compliant exampleexample

Acme Coffee: your order #4471 is ready for pickup at our Mission St store until 6pm today. Reply STOP to opt out, HELP for help.

Common mistakespitfalls

Registering a throwaway campaign to test the integration and a real one later does not work either — the test campaign is refused on this rule, so the integration has nothing to test against.

Provider rejection codescodes

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

Provider	Code	Resubmit
AWS	CAMPAIGN_NON_COMPLIANT_CONTENT_NON_SUBSCRIBER	Yes
AWS	NON_COMPLIANT_USE_CASE	Yes

Rules you will hit next

6 other rules read campaign.sample[] + campaign.description. 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-045Samples must not impersonate another organisationBlockingBLOCKING MSG-175Content must not invade privacy, defame, or otherwise cause harmBlockingBLOCKING MSG-177Content must not depict or facilitate substance abuseBlockingBLOCKING MSG-179Alcohol content must not be aimed at people under the drinking ageBlockingBLOCKING MSG-209A charity programme may not run games of chance or recurring donationsBlockingBLOCKING MSG-DECEPTIVEContent must not be deceptive, misleading, or impersonatingBlockingBLOCKING

All message content rules

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