Article summary
Separate +590, mainland French and visitor phones in a Guadeloupe business list, then accept WhatsApp Full Format through evidence-based field zones.
Seeing +590, +33 and other country codes in a Guadeloupe business list does not automatically mean the data is dirty. The mix may represent local residents, mainland French customers and visitors. The harmful shortcut is forcing every phone into +590 and publishing one “local user” percentage.
View the same list as three sets
| Set | Evidence | Use |
|---|---|---|
| +590 phones | Numbering plan | Format acceptance |
| Guadeloupe customers | Order or service location | Business analysis |
| Currently permitted contacts | Consent and opt-out records | Contact control |
Route a multi-code batch before checking
Preserve phone_raw and country_evidence and create candidates under the corresponding numbering plan. Unsupported national notation enters country_unknown. A hotel, event or folder name is not phone-country evidence.
Full Format does not require using every field
If the purpose needs only registration or activity segmentation, age, gender, avatar and skin-tone observations are unnecessary. Select Full Format only when multiple field families jointly support a documented, approved analysis.
Create three zones in the workbook
Give base/activity, profile observation and account relationship separate users and expiry dates. The operating queue should not automatically see profile data, and mapped phones should stay outside ordinary exports.
Expire visitor data with the trip
When the service dates end, reassess any follow-up purpose. Recent activity cannot extend a relationship created by one trip. Registration cannot erase opt-out or create marketing permission.
Explain missingness with a source matrix
Compare format exceptions and field unknowns across local forms, booking platforms, stores and legacy CRM. Differences first indicate collection-process quality, not behaviour by a Guadeloupe or French population.
Never auto-merge a one-to-many relationship
TXT reconnects through batch_row and internal contact_id. If a mapped phone conflicts with an existing record, preserve both pieces of evidence and timestamps for human decision rather than overwriting the source phone.
Publish two denominators
Report the +590 numbering pool and Guadeloupe service customers separately. Readers can then see the difference between phone region and business market. Foreign visitors must not disappear invisibly from the denominator.
What this page helps a team avoid
This is not a country-name replacement Full Format tutorial. It solves the mixed-numbering problem of an overseas tourism market: phones retain their evidential plan, while business market comes from business evidence.
