Article summary
Prepare Tunisia +216 phones for WS Avatar, then separate logos, portraits, blanks and business-account results without replacing supplier due diligence.
A Tunisia WhatsApp avatar check can organize image state in an existing supplier or customer list, but it cannot perform supplier due diligence. A logo does not establish a legal company, a portrait does not identify an authorized officer, and a blank image does not prove a fake account. Treat output as a review clue, not an automated credit decision.
Verify provenance before +216 formatting
Preserve phone_raw, country_evidence, source and contact_id before cleaning. Remove presentation characters and validate +216 plus the national significant number under the current Tunisia plan. Country or length conflicts go to an exception queue; a French or Arabic name is not country evidence.
| Input condition | Action | Cannot establish |
|---|---|---|
| Reliable +216 structure | Candidate for TXT | Current location |
| Local digits only | Require country evidence | Automatic +216 assignment |
| Duplicate phone | Retain the deduplication crosswalk | Same legal company |
WS Avatar returns four fields
The AIPUSH task exports phone, business-account result, avatar and WhatsApp mapped phone. It does not return company registration, beneficial ownership, payment history or contracting authority. Corporate, banking and contract evidence remain necessary.
Classify avatar observations without overclaiming
| Observation | Permitted record | Follow-up evidence |
|---|---|---|
| Brand logo | Image-type clue | Website and legal entity |
| Portrait | Avatar visible | Authorized contact confirmation |
| Product / shop | Business-context clue | Catalogue and contract |
| Blank | Unknown state and date | No automatic rejection |
Keep supplier records out of TXT
AIPUSH accepts TXT with one phone per line. Company name, tax ID, quotation, language and review notes remain inside the business. Reconnect returned Excel through contact_id rather than uploading the complete supplier table.
Place the business-account field correctly
The field describes an account-type result returned by the task. It does not prove scale, credit, verification or delivery ability. Procurement may store it as a contact-channel observation, while admission decisions rely on independent documents.
Do not compress every blank to false
Not returned, not visible, processing error and explicitly no image remain separate with checked_at. If import converts all four to “no avatar,” a rerun cannot explain change and supplier triage becomes unfair.
Mapped phones trigger relationship review
One input with several mappings, one mapping shared across suppliers, or a mapping that conflicts with expected +216 structure opens mapping_conflict. The newest return never overwrites a supplier-provided phone automatically.
Language is not encoded in an avatar
Tunisian business may use Arabic, French or another language. preferred_language comes from choice or evidenced communication, not automatic inference from image text, name or country code.
Accept the batch on reviewability
Deliver +216 format pass rate, avatar coverage, business-account results, blank categories, mapping collisions and observation date. The check reduces work only when procurement can see what still requires verification; a falsely certain score does the opposite.
