Registration fields must not contain emoji
The requirementstatement
No campaign registration field may contain an emoji character.
- 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.* (all text fields)
- Where it liveslayer
- CampaignCAMPAIGN
- 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
How to fix itremediation
Remove emoji from the registration fields. They are allowed in live message traffic, but not in the registration record itself.
A compliant exampleexample
Acme Coffee sends weekly promotional offers to customers who opted in at checkout.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| TCR/DCA | 6103 | Yes |
Notesnotes
Rules you will hit next
2 other rules read campaign.* (all text fields). 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-EMOJI is one of 94 campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.