Article summary
Separate the shared +44 plan, Isle of Man market evidence and WhatsApp profile observations instead of turning the code into identity.
Writing country=United Kingdom whenever a phone begins +44 distorts an Isle of Man list at the first step. The Isle of Man operates within the shared +44 numbering environment. The numbering-plan field may be common, but business market requires address, order or self-report. WhatsApp profile observation is a third layer and cannot backfill geography.
A shared calling code needs a relationship model
| Field | Evidence | May +44 create it? |
|---|---|---|
| number_plan | Numbering rule | Yes, +44 environment |
| market | Order, address, self-report | No |
| language | User choice | No |
| profile_observation | Checking task | No |
Preserve provenance before deciding Isle of Man
Keep phone_raw, source_file, source_row and market_evidence. A source with a documented Isle of Man address may support a market label. A bare +44 phone remains market_unknown; an area-code guess cannot replace customer evidence.
Accept phone format and profile output separately
Formatting exceptions enter a phone queue, while age, gender and avatar nulls enter a profile queue. Mixing the two turns parsing failure into profile missingness and distorts percentages in a small market.
A mapped phone is not a master identity key
WS Gender and Age may return phone, age, gender, avatar and mapped WhatsApp phone. A mapping needs source and observation date. One-to-many or changing relationships remain conflicts and do not overwrite the CRM primary phone.
Five things +44 cannot establish
- Current residence on the Isle of Man.
- British citizenship.
- English language preference.
- Control by the original phone holder.
- Consent to WhatsApp marketing.
Prevent re-identification in a small batch
An Isle of Man sample may be small. Check minimum cells after crossing location, age and gender; combine age bands or retain an overall aggregate when needed. Person-level avatars and inferences are unavailable to operating roles that do not need them.
Use two keys for the TXT return journey
TXT contains one phone per line, while batch_row and contact_id remain internal. When Excel returns, locate by batch_row and verify against the submitted phone. A disagreement between the two keys enters human review.
The page resolves a classification problem
This is not a method for identifying an “Isle of Man person.” It shows how evidence survives inside a shared numbering system. Profile fields remain in controlled aggregates, while permission and opt-out decide contact independently—making the country page genuinely different from a generic +44 guide.
