A toll-free contact needs a full first and last name
The requirementstatement
The toll-free registration contact must be an authorised representative's full first and last name.
- 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
- tfv.contact_first_name + .contact_last_name
- 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
- Infobip
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Name a real person who is authorised to act for the business, first and last name in their own fields. Done when both fields hold a person's name rather than a role or a department.
A compliant exampleexample
contact_first_name: Jane · contact_last_name: Doe
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Infobip | 10000 | Yes |
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-165 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.