Article summary
Prepare Colombian +57 phone lists for WhatsApp Avatar Check, reconcile picture, business-account, and mapped-phone fields, and avoid identity or permission inference.
A Colombia WhatsApp Avatar Check is not a shortcut for finding “precise customers.” It is a defined field task applied to a traceable +57 phone cohort. AppShai WS Avatar Check exports Phone, Business Account, Picture, and WhatsApp Mapped Phone. These fields do not prove identity, age, gender, intent, or contact permission.
Resolve country evidence, local and international notation, punctuation, duplicates, and CRM mapping before the task. Rich picture output cannot repair an unstable phone key.
Direct answer: preserve phone_raw, normalize to a +57 international representation only from confirmed Colombian evidence, create UTF-8 TXT with one phone per line, reconcile Excel by Phone, keep Mapped Phone separate, and treat Picture as a display-related task field.
WS Avatar Check fields
| Field | Correct meaning | Does not establish |
|---|---|---|
| Phone | Input and reconciliation key | Current subscriber identity |
| Business Account | Account-type-related output | Business credentials, size, or trust |
| Picture | Picture-related output | Legal identity, a current personal photo, or permission |
| WhatsApp Mapped Phone | Task mapping field | Permission to overwrite original phone |
| checked_at (internal) | Time context for the result | Permanent state |
Prepare Colombian +57 phones
The ITU-T E.164 international numbering plan explains the international numbering framework, but list normalization must be based on record-level evidence. A Colombia-related contact may use local notation, +57 notation, or a phone assigned elsewhere. Nationality, location, and phone assignment are different facts.
| Raw condition | Rule | Do not |
|---|---|---|
| Explicit +57 | Remove display punctuation and retain country code | Add 57 twice |
| Local notation with confirmed country | Apply the verified transformation | Guess country from a name |
| CRM country conflicts with phone | Send to manual review | Force the CRM country |
| One contact has several representations | Normalize and preserve relationships | Delete lineage |
| Country unknown | Mark unknown | Default to Colombia |
Six-step CRM-to-TXT cleanup
- Limit the cohort to traceable forms, orders, stores, support, or other defined records.
- Preserve phone_raw and contact_id; transformations go into new fields.
- Confirm country_evidence and create phone_normalized.
- Remove spaces, brackets, hyphens, and notes from task input.
- Deduplicate normalized phones while retaining a relationship table.
- Export UTF-8 TXT with one phone per line and no header or labels.
Select WS Avatar Check in the AppShai WhatsApp (WA/WS) Number Checker. The upload is TXT; the output is Excel.
Small-sample acceptance test
| Control | Pass condition | Exception action |
|---|---|---|
| Valid TXT lines | Match task accepted count | Review blanks and illegal characters |
| Phone | Maps to a unique input or documented one-to-many relation | Send to unmatched queue |
| Mapped Phone | Separate column | Never overwrite phone_raw |
| Blank Picture | Retained as blank | Do not convert to unregistered |
| Business Account | Preserved as returned | Do not auto-score business value |
| Batch and date | Connect source TXT and Excel | Block production import if missing |
Reasonable uses of the picture field
- Completeness review: document whether a picture-related value was returned.
- Human support context: provide limited context inside an existing lawful relationship.
- Exception detection: surface blank, duplicate, or unmapped records.
- Governance: decide whether retaining the field is necessary.
- Task selection: distinguish Avatar Check from Registration Check.
A picture should never be the sole basis for identity verification or an automated decision. It can be a logo, a group photo, an old image, or unrelated to the current phone user.
Four common misuses
| Misuse | Why it fails | Alternative |
|---|---|---|
| Picture means real person | The image does not verify the subject | Use an appropriate identity process |
| Business Account means trusted company | The field is not due diligence | Verify business credentials independently |
| Infer age or gender from picture | Unreliable sensitive inference | Use necessary, user-provided data |
| Picture means marketing permission | A display field creates no consent | Check channel, scope, and opt-out |
CRM schema
| Field | Source | Retention rule |
|---|---|---|
| phone_raw | Customer system | Preserve original according to policy |
| phone_normalized | Cleaning process | Carry transformation version |
| wa_avatar_result | Avatar Check Excel | Restrict access; no inference |
| wa_business_flag | Avatar Check Excel | Preserve original meaning |
| wa_mapped_phone | Avatar Check Excel | Separate from input |
| wa_checked_at / batch_id | Internal task record | Expiry and lineage |
| permission / opt_out | First-party evidence | Never modified by checking |
Retention and access
Picture-related fields need stronger minimization than a binary registration result. Define purpose, authorized roles, retention, and deletion before running the task. Do not place Excel exports in public storage. Delete unnecessary copies after analysis.
Frequently asked questions
Do Colombian phones always begin with +57?
The international representation uses country code +57, while business lists may contain local notation, foreign phones, or errors. Confirm from provenance before transforming.
Does a blank picture mean not registered?
No. Privacy settings, task behavior, or an exception may produce a blank. Use the task definition and independent fields.
Can a picture verify a real customer?
No. A profile picture is not identity evidence and does not prove who currently controls the phone.
A reliable Colombia avatar-check workflow is built on phone evidence, reconciliation, and field boundaries. Treat the image as limited task output, not customer truth.
