The brand must be verified before its campaign is submitted

The requirementstatement

A campaign must not be submitted until the brand reaches an approved, verified identity status.

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.identity_status + campaign submission
Where it liveslayer: Brand ↔ campaignCROSS
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: TCRAWSTwilio
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

A campaign is judged against the brand as it stands the moment it arrives, so one submitted against an unverified brand is refused — and the refusal names the campaign. Teams then rewrite the description, the samples and the flow, none of which was the problem, and resubmit into the same wall. It happens because the brand call returns 200 with a pending status and looks like success.

How to fix itremediation

Hold the campaign until the brand identity status reads VERIFIED or VETTED_VERIFIED, and sequence the two submissions off the brand status event rather than off a timer. Done when the brand is in a final verified state at the moment the campaign is sent.

Check this yourselfattestation

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

Does the brand read VERIFIED or VETTED_VERIFIED at the moment the campaign is submitted, rather than PENDING?

1Fetch the brand immediately before submitting the campaign and read the identity status — do not rely on the 200 the create call returned, which succeeds while the status is still pending.
2Sequence the campaign off the brand status webhook rather than off a timer, so the campaign leaves only once the status is final.

What wrong looks like: The campaign is refused and the error names the campaign, so the description, samples and flow are rewritten and resubmitted into the same wall — while the brand was the thing that was not ready.

Notesnotes

The wait is at the registry and nothing here shortens it. What the user has to do is order the two submissions — brand first, campaign only once the status is final — because a campaign refused for this reason still consumes a submission and, at some providers, a fee. An UNVERIFIED status is not a brand defect on its own: it is the state a brand sits in while the check runs.

Rules you will hit next

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

XBC-007A public company must finish two-factor identity before any campaignBlockingBLOCKING XBC-001Sole proprietor brands may only run the sole proprietor use caseBlockingBLOCKING XBC-002Charity use case requires a verified 501(c)(3) non-profit brandBlockingBLOCKING XBC-003Political use case requires a non-profit brand with political vettingBlockingBLOCKING XBC-004Emergency and public-safety use cases exclude sole proprietorsBlockingBLOCKING XBC-005Sole proprietor brand and campaign both require a reference IDBlockingBLOCKING

All brand ↔ campaign rules

XBC-006 is one of 13 brand ↔ campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.