No emoji in any brand field
The requirementstatement
No brand field may contain an emoji or pictograph.
- 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
- all brand text fields
- Where it liveslayer
- BrandBRAND
- 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
- TelnyxTCRTwilio
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Remove the emoji from the named field. Keep it in your social profiles and your message content where it is fine — it is only the registry fields that must be plain. Done when every brand field is plain business text.
A compliant exampleexample
display_name: Acme Coffee — not "Acme Coffee ☕"
Rules you will hit next
2 other rules read all brand 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.
BRD-269 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.