Article summary
Handle Djibouti’s move from six- to eight-digit numbers, then review the ten WS full-format fields, data-minimization decision and Excel acceptance checks.
The main country-specific risk in Djibouti WhatsApp full-format checking is legacy data. Djibouti uses country code +253 and moved from a six-digit to an eight-digit national plan in 2012. Old six-digit CRM records must not receive two guessed digits.
Separate current-looking and legacy records
| Raw shape | Interpretation | Disposition |
|---|---|---|
| +253 plus eight national digits | Looks consistent with the newer plan | Retain raw value and normalize |
| 253 plus eight digits | May be a digit-only key | Confirm with source country |
| Eight domestic digits | Requires Djibouti evidence | Add 253 only when evidence is reliable |
| Six-digit legacy value | May predate the 2012 change | Repair from historical range evidence or quarantine |
Why the numbering migration cannot be guessed
ITU records show that Djibouti adopted an eight-digit closed plan from March 2012, with different added digits by service and area. See the ITU Djibouti numbering change. Without the old service type and period, padding can create a different subscriber number.
The ten WS full-format fields
AIPUSH WS full format lists phone number, activity time, active days, gender, age, avatar, skin tone, avatar type, business-account field and WhatsApp-mapped number. Ten columns do not mean that all ten are necessary for the project or present for every record.
Make a minimization decision first
If the question is registration only, choose a registration task. If it concerns activity, the activity service has a narrower schema. Full format fits a justified multi-field project with explicit access, purpose and retention controls. Convenience is not a reason to keep profile data indefinitely.
Create a legacy-number repair sheet
- Raw phone value and record year
- Source system and country evidence
- Historical service type or carrier documentation
- Migration rule and authoritative reference
- Number before and after repair
- Human reviewer and disposition
Test the TXT before processing
Submit only numbers that passed the eight-digit and country-evidence checks. Keep source IDs locally and put one phone number on each TXT line. Include a small set of known current numbers and repaired legacy examples in the pilot so the team can test both normalization paths.
Review three kinds of Excel conflict
The first is a difference between submitted and mapped numbers. The second is one phone key linked to several CRM contacts. The third is missing or contradictory profile-related output. Preserve original values and send each conflict to review; never let a bulk script overwrite them automatically.
Completion criteria for a Djibouti batch
- Current eight-digit and legacy six-digit values are separated.
- Only evidence-supported records enter TXT.
- The selected task matches the ten expected headers.
- Input, return and join counts reconcile.
- Unknown fields remain unknown.
- Permission and opt-out controls apply before use.
- The full-format workbook has a deletion date.
Numbering history determines whether the input is credible, the WS task determines what is returned, and company governance determines permitted use. Keeping those layers separate prevents “more fields” from becoming a false definition of quality.
