Article summary
Validate Haiti +509 eight-digit phones and place WS Activity time, active days and mapped phones into CRM without confusing activity with permission.
A Haiti WhatsApp activity project should begin with +509 structure, not an “active customer” label. Haitian national numbers are generally eight digits. After formatting passes, WS Activity still returns a dated platform observation; it does not prove identity, contact permission or purchase intent.
Separate +509 number types
| Type | Structure | Action |
|---|---|---|
| Mobile | Eight digits after +509, checked against current mobile ranges | Task candidate |
| Fixed, VoIP or special service | Uses its applicable range | Do not assume a mobile contact |
| Eight digits without country evidence | Length matches only | Return to provenance |
The ITU-hosted Haiti +509 numbering information records fixed, mobile and VoIP blocks announced by CONATEL and can anchor a rule version.
Four core WS Activity fields
| Field | Use | Boundary |
|---|---|---|
| Phone | Associate the task record | Not permanent identity |
| Activity time | Store a time observation | Not permission |
| Active days | Approved recency grouping | Not purchase intent |
| WhatsApp mapped phone | Support reconciliation | Collisions require review |
Do not hard-code an eight-digit rule forever
Attach a version and effective date to the range table and monitor notices from the responsible authority. Correct length means only that a structure may be plausible; range, country provenance and record integrity still matter.
Preserve business mapping when creating TXT
Clean +509 notation and separators, then export one phone per line. AIPUSH accepts TXT only; names, addresses and orders stay internal. Retain phone_raw, contact_id, source and country_evidence in the company system.
Load Excel into an activity-observation table
After completion, add task_name, batch_id and checked_at to the workbook in staging, then populate whatsapp_activity_observation. Never overwrite the customer master or delete older observations.
Stop on mapped-phone collisions
If one source phone produces several mapped phones, or one mapped phone appears under multiple contact_ids, create mapping_conflict. Automatically choosing the newest value can hide sharing, reassignment or entry defects.
The permission system owns the final decision
A recently active record must not enter marketing when it has opted out or lacks WhatsApp scope. Activity can prioritize an approved service process; it cannot manufacture the basis for contact.
Accept on data quality, not “activity rate”
The report should disclose compliant +509 phones, range exceptions, blanks, mapping collisions, field coverage and observation date. Only with that lineage is a Haiti WhatsApp activity result ready for CRM use.
