A2P 10DLC rule registry
A valid brand and a valid campaign can still be refused as a pair. These rules cover the coherence between the two records: the entity type against the use case, the brand website against the campaign’s consent claims, the display name against the sender identification in the samples.
A SOLE_PROPRIETOR brand must register its campaign under the SOLE_PROPRIETOR use case; standard campaign types are unavailable to that tier.
The CHARITY use case is restricted to a NON_PROFIT brand holding verified 501(c)(3) tax-exempt status.
The POLITICAL use case must sit on a NON_PROFIT brand carrying external political vetting recognised by both AT&T and T-Mobile.
Public-safety and emergency use cases are not available to a SOLE_PROPRIETOR brand.
referenceId is mandatory — not optional — on both the brand and the campaign for the sole proprietor tier.
A campaign must not be submitted until the brand reaches an approved, verified identity status.
A PUBLIC_PROFIT brand must complete its Authentication+ two-factor identity step before a campaign is created against it.
A SOLE_PROPRIETOR brand may hold exactly one campaign, and that campaign exactly one telephone number.
Each sample must contain the registered brand name or DBA, matching the brand record rather than a marketing alias.
The CTA / message-flow field must name the brand, matching the registered Brand or DBA.
The HELP auto-reply must contain the registered brand name.
The registered brand name, the brand website, and what the campaign says it sends must be coherent.
The campaign description must name the registered legal name or the registered DBA.
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.