Article summary
Repair legacy Mexican +52 1, 044 and 045 notation before WS Activity, keeping format cleanup, activity observations and permission separate.
A Mexico WhatsApp Activity project should search for legacy +52 1, 044, 045 and 01 notation before searching for “dormant users.” When one phone survives in both old and current forms, direct checking creates duplicate tasks, reconciliation collisions and a distorted activity rate.
The post-2019 ten-digit rule
Mexico’s IFT explained in its 2019 unified dialing announcement that fixed and mobile national numbers moved to uniform ten-digit dialing, removing 01, 044 and 045. The former 1 after +52 for international calls to mobiles was also removed.
Build a legacy-repair dictionary
| Historical input | Normalization target | Control |
|---|---|---|
| +52 1 + ten digits | +52 + ten digits | Confirm 1 was the legacy mobile marker |
| 044/045 + ten digits | +52 + ten digits | Preserve raw value |
| 01 + fixed phone | +52 + ten digits | Verify area code |
| Ten digits without country evidence | Exception | Do not assume Mexico |
Deduplicate after normalization
The same customer may have +521… and +52… rows. Create canonical_phone, identify candidate duplicates and retain source_rows, first_seen and last_seen. Silent deletion can break historical orders and permission evidence.
What WS Activity actually returns
The fields are phone, activity time, active days and WhatsApp mapped phone. They do not identify Mexican state, current time zone, holder or purchase intent, and they cannot prove that every legacy repair belongs to the same person.
Accept Excel by repair path
| Cohort | Report | Warning |
|---|---|---|
| Native +52 | Return and missing rates | Range-rule defect |
| Legacy 1 removed | Mapping collisions and duplicates | A real leading digit removed |
| 044/045/01 removed | Area-code completeness | Wrong length |
| Manual exceptions | Excluded from task | Keep out of denominator |
AIPUSH receives only the final TXT
Put one normalized phone per line without customer name, state, order or permission. Internally retain contact_id, phone_raw, repair_rule and TXT hash. Load returned Excel into staging before reconciliation.
Activity time is not the user’s time zone
Mexico spans several time zones and a +52 phone may roam. Do not infer working hours or location from activity. Schedule communication from a user address, explicit selection or actual service region.
A mapped phone does not replace the master
When mapping differs from input, store relationship_type, observed_at and batch_id. One-to-many, many-to-one and legacy-chain conflicts need review. The newest return never overwrites CRM automatically.
Legacy repair does not renew legacy permission
Changing +521… to +52… repairs notation; it does not extend consent collected years ago. Marketing still depends on provenance, WhatsApp scope, purpose, time and suppression.
The real measures of batch success
Legacy detection, reversible deduplication, rule exceptions, activity coverage, mapping collisions and observation date are more useful than one “activity rate.” Once the format layer is explainable, the activity denominator becomes credible.
