Editing the brand expires a completed vet
The requirementstatement
A completed vet expires when the brand information behind it changes.
- 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 brand diff vs the vet state
- 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
- TCR
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Batch brand edits and make them before ordering the vet, not after. Where an edit is unavoidable on a vetted brand, budget for re-ordering the vet and expect the cooldown in BRD-221 to apply to it.
Check this yourselfattestation
Ekas flags this from what you submit, but the fact that settles it sits somewhere only you can reach.
Is this brand edit worth losing the completed vet that is pinned to the current record?
- 1Check whether a completed vet is attached before making the edit.
- 2Batch edits and make them before ordering the vet, not after.
- 3Where the edit is unavoidable, budget for re-ordering the vet and expect the three-month cooldown to apply.
What wrong looks like: The expiry is silent. Throughput drops to the unvetted tier and the first anyone knows is a queue building on a send that used to clear.
Notesnotes
Rules you will hit next
Other brand rules at the same severity. A registration is judged as a whole, not rule by rule.
BRD-222 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.