Vet before the campaign, not after the volume disappoints

JSONMarkdown

The requirementstatement

External vetting should be ordered before registering a campaign that needs material volume.

Severityseverity
HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
When it bitesphase
Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject
the vet record
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
Wait on someone elseTERMINAL_EXTERNAL
Needs an external system or a waiting period, such as IRS propagation, a vetting result, or a carrier queue.
Who requires itauthorities
TelnyxT-Mobile
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

An unvetted brand starts at the bottom carrier tier — a couple of thousand messages a day — and the tier is what the campaign inherits at registration. Ordering the vet afterwards works, but the launch has already been scheduled against throughput the brand does not have, and the vet takes days. The cost of getting this wrong is a missed send date rather than a rejection, which is why nothing flags it.

How to fix itremediation

Decide the daily volume the programme needs, then order the vet if it is above the unvetted floor of roughly 2,000 messages a day. Do it before the campaign is registered, and allow several days for the result.

Check this yourselfattestation

Ekas flags this from what you submit, but the fact that settles it sits somewhere only you can reach.

Does the volume this programme needs exceed the unvetted daily floor of roughly 2,000 messages a day?

  1. 1Do the arithmetic: list size and send frequency against the unvetted cap.
  2. 2If the first exceeds the second, order the vet before registering the campaign and allow several days for the result — the campaign inherits the brand's tier at registration.

What wrong looks like: Nothing is rejected. The launch is scheduled against throughput the brand does not have, and the vet that would fix it takes days that the send date does not allow.

Notesnotes

Whether a vet was ordered is a fact about the account rather than about the registration, so this reports UNCLEAR rather than guessing. What the user has to do is the arithmetic: list size against the unvetted daily cap, and if the first exceeds the second, the vet is a prerequisite rather than an upgrade.

Rules you will hit next

Other brand rules at the same severity. A registration is judged as a whole, not rule by rule.

BRD-006Submit every name line above the address on a multi-line IRS recordHighHIGHBRD-007TCR takes only the first line of the IRS-registered nameHighHIGHBRD-010Take the legal name from the CP-575 or 147C, never a W-2 or W-9HighHIGHBRD-014An acquired business registers the details it filed taxes underHighHIGHBRD-027EIN must be old enough to have propagated to IRS recordsHighHIGHBRD-034Validate a non-US identifier against its home register before submittingHighHIGH

All brand rules

BRD-234 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.

Talk to UsHow 10DLC works