Brand contact email must not use a free consumer domain

The requirementstatement

The brand support/business contact email must be on a domain the business controls, not a free consumer mail provider.

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
brand.email
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
AWSTCRSinchBandwidthTelnyx
When it appliesapplicabilityText
Applies when the brand is NOT a sole proprietor.

Why this rule existsrationale

A business-domain email is weak evidence that the registrant controls the business they are registering. Free consumer addresses are the pattern fraudulent registrations use, so several providers reject them outright rather than weighting them.

How to fix itremediation

Use an email address on your business domain (e.g. support@yourcompany.com). Free consumer addresses are rejected for registered entities.

A compliant exampleexample

support@acmecoffee.com

Notesnotes

Sole proprietors are carved out — they legitimately have no business domain. Severity varies by authority (MEDIUM at carriers, BLOCKING at AWS/TCR/Sinch); strictest kept.

Rules you will hit next

3 other rules read brand.email. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.

All brand rules

BRD-109 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.