Article summary
Build a traceable Mauritania +222 WhatsApp Full Format workflow from source registration and TXT row IDs to field-family acceptance in Excel.
The hard part of a Mauritania WhatsApp Full Format project is not the number of columns; it is explaining where every column came from three weeks later. When +222 phones arrive from stores, partners and a legacy CRM, the audit trail must exist before upload.
Begin with a handoff register, not the TXT
Record an owner, acquisition date, business purpose, permitted use and deletion date for each source. Phones with undocumented provenance should not be mixed into a documented pool. A rich returned workbook cannot repair missing authority.
Give each submitted row an immutable position
Preserve phone_raw while removing spaces, duplicated country codes and obvious non-phone characters. Generate TXT with one phone per line and retain batch_id, batch_row and contact_id internally. Customer names and orders do not belong in the upload.
Full Format is not one hit rate
| Field family | Example fields | Independent acceptance question |
|---|---|---|
| Base and activity | Phone, activity time, active days | Is the time basis complete? |
| Profile observation | Gender, age, avatar, skin tone, avatar type | Are unknowns preserved? |
| Account relationship | Business status, mapped phone | Are conflicts isolated? |
Accept Excel through count reconciliation
At minimum, submitted must equal returned plus format_exception plus processing_unknown. Explain every difference. Then calculate missingness for each field family and source rather than hiding a nearly empty family behind one overall “success” figure.
Mapped phones belong in a conflict table
A mapping must not overwrite the CRM primary phone automatically. One-to-many, many-to-one, disagreement with an existing record or missing observation date all enter mapping_conflict with reviewer and decision evidence.
Use narrower access for sensitive observations
Age, gender, avatar and skin-tone observations are not self-reported traits. They must not support identity verification, credit, employment, insurance or differential pricing. If operations needs only an activity queue, it should not receive the profile worksheet.
Store results as events instead of overwriting history
Activity and profile visibility can change. Retain checked_at, task_version and source_batch, then append a new event for a later task. The previous value explains the decision made at that time and should not disappear silently.
Three reasons to pause the whole import
- Source-level format failure differs sharply without an explanation.
- Returned rows cannot reconcile to submitted rows.
- Mapping conflicts cluster while no human review capacity exists.
The final Mauritania handoff
The deliverable is more than an Excel file. It includes a source register, exception table, field-family acceptance record, access scope and expiry date. That is how a +222 Full Format task becomes an auditable data process rather than a one-off screening run.
