Article summary
Handle WhatsApp avatar observations for Peru +51 shared household and business phones without binding one image automatically to one customer identity.
A Peru +51 phone may be a household contact, business desk or personal number. One WhatsApp avatar cannot automatically represent one person in CRM. Avatar checking needs a relationship model first.
Four relationship states
| State | CRM handling |
|---|---|
| one_to_one_confirmed | Append observation |
| household_shared | Do not bind personal profile |
| business_contact | Link to organisational contact point |
| relationship_unknown | Keep conflict |
Look for sharing signals first
If one phone maps to several customers, order names or permission states, mark shared. Do not inspect an avatar and choose the person who looks most similar.
+51 supports phone processing only
Preserve phone_raw and provenance. The code does not prove holder, household role, company or location.
Business status is not company certification
A business-account observation describes account type. It cannot validate company legitimacy or the CRM organisation.
Keep avatars out of identity resolution
Do not perform face matching or infer name, age, gender, ethnicity, income or occupation from a photograph.
Household relationships stay out of TXT
Upload one phone per line while household_id, contact_id and permission stay internal. Excel reconnects through batch_row into the relationship table.
Apply stricter control to shared phones
When associated records disagree, one consent does not overwrite another opt-out. A human confirms the applicable scope.
Report phones, not people
The task denominator is unique phones; one shared phone is not counted as several people’s avatars. Person-level statistics require additional reliable evidence.
The Peru boundary
An avatar is an observation about a phone profile, not automatically about a person. Resolve relationship before limited use.
