Article summary
Connect Namibia +264 country-evidence recovery and WhatsApp avatar observation as two stages so guessed phones are not profiled.
The Namibia avatar page should not repeat the Registration page: it starts after country evidence has been recovered and the phone has passed format review. If +264 itself was guessed, a rich avatar result still sits on the wrong row.
Two-stage admission
| Stage | Pass condition | Failure route |
|---|---|---|
| Country and format | Accepted evidence level | country_review |
| Avatar observation | Approved purpose and access | purpose_review |
Do not rerun every phone from stage one
Inherit approved +264 candidates through cohort_id and process only new provenance or rule changes.
Avatar checking answers visibility
It may return phone, business-account observation, avatar and mapped phone. It does not verify country, identity, language or a real-world person.
A return cannot upgrade country_unknown
Even if an avatar returns for a guessed phone, it does not prove Namibia. The country state remains unknown.
Prefer retaining an observation
If avatar_observed and checked_at support the analysis, do not store the original image long term. Give temporary review a shorter delete_after.
Calculate blanks by provenance
Stratify current website, legacy CRM and partner files and separate format failure, limited visibility and task unknown.
Run a mapped phone through country admission
A new relationship does not inherit +264 automatically. Review its own phone and provenance evidence.
Neither stage creates permission
Country confirmation and avatar observation do not create marketing consent. Opt-out remains authoritative.
How the two Namibia pages divide work
The Registration page repairs admission evidence; the avatar page governs image purpose. cohort_id connects them without duplicated copy.
