Article summary
Separate North Macedonia +389 phones, name transliteration and WhatsApp avatar observations without using spelling similarity to verify identity or language.
A North Macedonia +389 list may contain several valid name transliterations, but similar spelling plus an avatar still cannot verify a real-world person. Phone reconnection, display names and identity decisions require separate layers.
Three fields cannot become each other’s primary key
| Field | Can support | Cannot support |
|---|---|---|
| phone_key | Task deduplication | Personal identity proof |
| transliterated_name | Agent display | Automatic merge |
| avatar_state | Visibility observation | Name verification |
+389 belongs only in the phone layer
Preserve phone_raw and country_evidence. A country code does not determine citizenship, community, language or identity.
Keep multiple blank-avatar states
Store not_observed, visibility_limited, task_unknown and format_exception separately. Never guess an image from a name.
Review mappings with business evidence
Orders, user confirmation and internal contact_id may support human review. Facial resemblance or transliteration similarity cannot be the sole basis.
Version transliteration
Keep original text, transliteration rule and version for search and display only. A rule change must not silently rewrite historical identity.
Names stay out of TXT
The execution file has one phone per line. Name, language and permission stay in the private crosswalk, and Excel reconnects through batch_row.
Prohibit group inference from avatars
Do not infer ethnicity, religion, politics, wealth, occupation or language, and do not label a visible avatar as a high-quality customer.
Human review needs a reason code
Confirmation, rejection and unresolved conflict each record evidence_code so “looks similar” cannot become an unauditable decision.
The North Macedonia outcome
Transliteration supports reading, avatar describes visibility and stable internal keys perform reconnection.
