Article summary
Deliver Sudan +249 WhatsApp avatar results as observation states and timestamps by default, opening images only for controlled short-term review.
After a Sudan +249 avatar task, ordinary sales teams usually need a workflow state, not an image. Distributing original images with Excel expands sensitive inference and uncontrolled retention.
Design delivery by role
| Role | Visible by default | Not visible by default |
|---|---|---|
| Sales | Necessary operating state | Original avatar |
| Data operations | Unknown and timestamp | Customer identity context |
| Controlled review | Temporary thumbnail | Permanent export |
Define the state dictionary first
Document avatar_observed, not_observed, visibility_limited, task_unknown and format_exception. Ban subjective labels such as “good avatar” or “real person.”
Keep +249 phone evidence independent
Preserve phone_raw and country evidence. A returned avatar cannot validate Sudan assignment or current location.
Do not use images for identity verification
Do not automatically compare photographs with names, faces or external records, and do not infer ethnicity, religion, health, politics or wealth.
Keep customer profiles out of TXT
Upload one phone per line while name, order and permission stay internal. Excel reconnects through batch_row into staging.
Temporary review needs a ticket
Image access requires review_ticket, purpose, viewer and delete_after. Remove temporary copies when the review ends.
Handle mapping separately
Mapped phones stay out of the sales table. A dedicated role reviews conflicts, and mapping cannot change permission automatically.
Measure successful minimisation
Count image views, unresolved tickets and on-time deletion rather than treating download volume as value.
The Sudan default
Deliver a state, not an image. Only a specific, necessary and short-lived human review creates an exception.
