Article summary
Explain why phone format, service location and WhatsApp registration must remain separate when Svalbard appears inside the +47 context.
A +47 phone can be processed under the Norway numbering environment, but the prefix alone cannot label it a Svalbard customer. An island business cohort needs location evidence such as an order, accommodation, service address or user self-report.
Three evidence types answer three questions
| Evidence | Answers | Cannot answer |
|---|---|---|
| +47 | Numbering plan | Island location |
| Order location | Service market | Phone registration |
| Registration task | Registration observation | Permission |
Create a location_evidence field
Store evidence type, source and date. “Country=Norway” alone is insufficient to create a Svalbard label. Preserve location_unknown where proof is absent.
+47 cleanup does not change location
Keep phone_raw and create candidates separately. Passing format admits a phone to checking, not to an island-customer segment.
Keep Registration narrow
TXT contains one phone per line and Excel returns phone plus registration observation. It does not prove present location, organisational affiliation or willingness to receive messages.
A small list needs coarse reporting
If crossing location, provenance and service type leaves very few records, report counts or combine groups to reduce re-identification risk.
Temporary service expires by date
Tourism, research and project service all have end points. Registration observation cannot turn a temporary contact into a permanent marketing audience.
A mapped phone cannot fill location
Route mappings to relationship review. Even when the person relationship is confirmed, retain existing location evidence rather than inferring place from the new phone.
How this differs from a Norway guide
The issue is not explaining +47 again; it is location evidence inside a shared numbering context. Without island proof, no island conclusion should be produced.
