Article summary
Understand French Guiana WhatsApp number formatting across +594, 0594 and 0694 notation, with masked examples and a practical pre-check for full-format screening.
The most common French Guiana phone-format mistake is assuming that a French overseas territory must use metropolitan France’s +33 country code. French Guiana retains +594 for international numbering. Within the French dialling environment, the same territory is also represented by ten-digit national notation such as 0594 for fixed lines and 0694 for mobile phones.
A WhatsApp list should normalize those representations before checking. Otherwise, the same contact may appear twice under different notation—or a +594 phone may be silently converted to the wrong country.
Does French Guiana use +33 or +594?
It uses +594 for international telephone numbering. France’s electronic communications regulator, Arcep, lists +594 for French Guiana, alongside +590 for Guadeloupe, +596 for Martinique and +262 for Réunion in its official overseas-numbering overview.
Administrative country and calling code are therefore separate data concepts. A useful CRM model can hold territory=French Guiana, administrative_country=France and calling_code=+594. One generic country column often cannot express all three correctly.
How 0594 and 0694 become international notation
| Source notation | Interpretation | International candidate |
|---|---|---|
| 0594 ** ** ** | French national notation for a Guiana fixed line | +594 594 ** ** ** |
| 0694 ** ** ** | French national notation for a Guiana mobile | +594 694 ** ** ** |
| +594 594 ** ** ** | Explicit international fixed-line notation | Keep +594; do not add a zero |
| +594 694 ** ** ** | Explicit international mobile notation | Keep +594; do not add a zero |
| +33 694 ** ** ** | Country-code and overseas prefix conflict | Route to review; do not guess |
The asterisks are masked examples, not working test numbers. In national notation, the first zero is a dialling prefix and is not carried into the +594 candidate. The following 594 or 694 digits remain part of the number.
Why a bulk “replace 0 with +594” rule fails
A France-oriented customer file can include metropolitan +33 phones, French Guiana, Martinique, Guadeloupe, Réunion and completely unrelated international contacts. A 0594 or 0694 pattern can support a candidate, but it should not override explicit country information or repair a truncated value.
Use evidence in this order: explicit international code, a territory selected by the user, documented acquisition source, and only then a number-pattern candidate. Postal code, language and surname are not proof that a phone belongs to French Guiana.
A +594 number is not a live location signal
From 1 January 2023, Arcep merged French Guiana’s seven former elementary numbering zones. The regulator’s numbering-plan announcement is another reason not to treat an old fixed-line prefix as precise present-day location.
Even when the format is unambiguous, +594 establishes a numbering-plan relationship, not where the contact is standing now. Mobile users, workers abroad and shared company numbers separate numbering origin from current location. Language must also come from an expressed preference; +594 does not guarantee French preference.
A cleanup sequence for mixed France and overseas data
- Preserve phone_raw as text. Stop spreadsheets from removing plus signs or initial zeroes.
- Separate explicit international codes. Identify +594, +33, +590, +596 and +262 before interpreting national notation.
- Transform national notation with provenance. Convert a 0594 or 0694 value only when the source supports French Guiana, and record the reason.
- Quarantine conflicts. Do not let software choose silently when the country field, calling code and pattern disagree.
- Deduplicate after normalization. National and international representations can share one check, while the original business records remain intact.
This order prevents two opposite errors: checking the same phone twice because it has two representations, and moving a metropolitan or foreign phone into +594 merely because a prefix looked familiar.
Five formatting failures require five different repairs
- Replacing the text 0594 with +594: a blind substitution can duplicate 594 or change the expected length. Parse the complete national structure.
- Prepending a code to an existing +594 value: identify international notation first so +594 is not concatenated twice.
- Turning every France record into +33: an administrative-country field cannot override an overseas territory’s calling code.
- Confusing +592 and +594: +592 is Guyana; +594 is French Guiana. Similar names do not mean a shared numbering plan.
- Deleting the source before deduplication: keep phone_raw so two representations can be proven equivalent.
The Guyana/French Guiana distinction is especially important when a source contains only “Guiana.” Return to the country selection, address or commercial record; do not change a calling code from an operator’s translation alone.
Classify a transformation as explicit, supported, candidate or conflict
explicit-international means the source already contains +594. converted-with-provenance means 0594 or 0694 agrees with reliable territory evidence. candidate-only has a plausible pattern but insufficient origin. conflict means the country field, calling code and structure disagree. Only the first two categories proceed automatically; the others remain reviewable.
Full Format is a second decision, not part of normalization
Normalization creates a checkable candidate. If the business only needs registration status, a WS Registration task is narrower. Use the AppShai WhatsApp Full-Format Number Checker when the approved workflow genuinely needs activity, avatar, profile, business-account and mapping observations together.
The Full Format Excel output can include phone, activity time, active days, gender, age, avatar, skin tone, avatar type, business status and mapped WhatsApp phone. “Full” describes the available field set, not a guarantee that every cell is populated. Profile observations cannot establish citizenship, preferred language or current location.
Three questions catch the remaining attribution errors
Can every +594 candidate be traced to an explicit international value or its original 0594/0694 notation? Are country conflicts still visible in a review queue instead of overwritten? Does the business system store numbering territory, customer market and current location separately?
If all three answers are yes, the list has moved beyond cosmetic formatting. If not, a successful WhatsApp task may still be feeding a geographic attribution error back into the CRM.
