Article summary
Prepare El Salvador +503 numbers and interpret WS Avatar fields, missing values and mapped-phone collisions without identity inference.
An El Salvador WhatsApp profile-picture check should not be presented as a way to “understand customers from their avatars.” For a +503 list, the controllable work is to validate the eight-digit number structure, preserve provenance, run WS Avatar and store avatar, business-account and mapped-phone results as dated technical fields—not as identity or demographic evidence.
Validate the eight-digit structure behind +503
El Salvador uses country code +503, and ordinary access-network numbers use an eight-digit structure. The ITU-hosted SIGET national numbering plan documents this design. Short codes, freephone numbers and special services should not enter a mobile-contact task merely because they also belong to +503.
Create pass, exception and unproven lanes
| Lane | Condition | Action |
|---|---|---|
| Pass | A compliant eight-digit number after +503 with El Salvador provenance | Candidate for TXT |
| Exception | Truncation, repeated country code, letters or special-service form | Record a specific exception_reason |
| Unproven | Eight digits without country evidence | Return to the customer or order source |
The four core WS Avatar fields
| Field | What it may describe | What it cannot prove |
|---|---|---|
| Phone | The phone associated with this task record | Permanent identity |
| Business account | A task-returned business-account-related state | Business legitimacy or size |
| Avatar | The picture-related result in this run | Holder identity, age, gender or occupation |
| WhatsApp mapped phone | A value for controlled reconciliation | A collision-free universal key |
“No avatar” is not one state
The account may have no picture, privacy visibility may prevent a return, the value may be temporarily unavailable or the task may have encountered an error. Model at least avatar_returned, no_avatar_result, unknown and error. Converting every blank to “no avatar” produces a tidy report at the cost of interpretability.
Govern an avatar reference separately from an image copy
If the output is a URL or another reference value, preserve its real task format and apply access and retention controls. Do not replicate external profile images throughout the CRM and do not derive sensitive attributes from them. An avatar may show a logo, multiple people, a pet or an old image; visual content is not an identity document.
Use the correct upload and return sequence
- Start from a +503 contact subset with a permitted business purpose.
- Remove separators and validate the eight-digit structure.
- Deduplicate while retaining the source-row-to-contact_id map.
- Export UTF-8 TXT with one phone per line.
- Select WS Avatar in AppShai and download Excel after completion.
- Load to staging before any governed CRM promotion.
AppShai accepts TXT only; Excel is the post-task export.
Resolve mapped-phone collisions without overwriting the source
When the source phone differs from the mapped phone, do not replace phone_raw. Create mapping_status and compare previous records. One-to-many, many-to-one or an existing assignment to another contact_id belongs in manual review. Add a mapping to the business view only when provenance, time and relationship are explainable.
Appropriate and inappropriate use cases
The task can support a documented data-quality project involving avatar returns, business-account fields or mapping reconciliation in an authorized list. It is not facial recognition, identity verification, credit scoring or permission for stranger outreach. If the only question is whether +503 phones return WhatsApp registration, use the narrower WS Registration task instead of processing unnecessary picture data.
Do not reduce acceptance testing to a success rate
The report should disclose input rows, compliant +503 phones, exceptions, duplicates, the four avatar states, mapping collisions and check time. Operators can then interpret a blank, while data owners can decide when the observation should be deleted or rechecked.
The value of an El Salvador avatar check comes from explicit boundaries: every eight-digit phone has provenance, every missing value has semantics, every mapping has a collision mechanism and the avatar remains a task-returned field. When one of those controls is absent, the result should not be expanded into a customer profile.
