Article summary
Separate French Guiana’s +594 numbering plan, French business context and the contact’s actual market when interpreting a WhatsApp Registration workbook.
A +594 phone can support formatting for French Guiana, but it cannot decide the contact’s customer market for the business. A French operating system, a South American service context, foreign phones and local orders may coexist. Separate these dimensions before a WhatsApp Registration task.
A customer row needs at least four location fields
| Field | Evidence source | Use |
|---|---|---|
| number_plan | +594 and phone rules | Formatting |
| service_market | Order or service location | Operational ownership |
| residence | User self-report | Regional communication |
| legal_entity | Contract and entity record | Responsibility assessment |
Do not convert a French phone into +594
A customer of a French Guiana operation may use +33 or another foreign phone. Preserve phone_raw and country_evidence and convert national notation only when the evidence is sufficient. Business location cannot substitute for phone-country evidence.
Registration answers one narrow question
Upload TXT with one phone per line. WhatsApp Registration returns Excel containing phone and registration observation. It does not prove residence in French Guiana or determine the processing basis for a French legal entity.
Calculate two denominators with two names
A registration rate for +594 phones answers a numbering-pool question. Results for all French Guiana order contacts answer a service-market question. Both denominators may be retained, but they must not be merged into one vague “local user” percentage.
Overseas contexts create duplicate relationships
The same person may provide a foreign phone on an order while WhatsApp returns a mapped phone. Reconnect through batch_row and contact_id. One-to-many and many-to-one relationships enter a conflict table rather than overwriting the master phone.
Give every unknown a reason
Keep format_exception, not_observed, task_unknown and returned distinct. Comparing unknowns by numbering plan, provenance and acquisition date reveals input problems without turning missing data into regional behaviour.
Permission is a separate control plane
Registration observation does not create marketing permission or clear an opt-out. Manage transparency, consent, suppression and deletion under the actual entity and purpose. Obtain professional advice when cross-region responsibilities are uncertain.
How results enter the CRM
Import Excel into staging with checked_at and task_version. Append registration as an event only for a reliable one-to-one relationship. Checker output must not rewrite phone, region, language or permission fields.
The search question this page truly answers
French Guiana WhatsApp Registration is more than “upload +594.” The workflow must preserve three evidence systems—phone region, customer market and operating entity—so its output remains interpretable.
