Article summary
Separate Gibraltar +350 phones, foreign visitors and cross-border customers before investigating WhatsApp avatar visibility.
A Gibraltar business list containing +350, +34, +44 and other phones is not automatically dirty. Visitors and cross-border customers may retain their original numbers, so preserve business provenance before avatar checking.
Create three customer views
| View | Evidence | Use |
|---|---|---|
| Numbering plan | Original international code | Formatting |
| Service market | Order location | Business |
| Visit/journey | Service date | Expiry |
Do not convert foreign phones into +350
Preserve phone_raw and country_evidence and process each phone under its plan. Project location cannot replace phone evidence.
Avatar describes profile visibility
It does not prove the contact was in Gibraltar or distinguish visitor, local resident and cross-border worker.
Compare blanks by provenance
Report hotel, store, event and legacy CRM separately to locate freshness and formatting issues.
Expire output with the journey
Clear avatar observations and temporary service data at service_end rather than turn one visit into a permanent profile.
Keep journey details out of TXT
Upload one phone per line while order and permission stay in the crosswalk. Excel reconnects through batch_row.
Mapped phones retain market evidence
Even a confirmed relationship does not change phone country or service market automatically. Humans review conflicts.
Do not identify groups from an avatar
Prohibit inference of nationality, ethnicity, language, occupation, wealth or trip purpose.
This Gibraltar page’s role
It addresses profile visibility for visitors and cross-border phones. A separate article handles shared business contact points.
