Article summary
Start with +265 country evidence and mixed-list cleanup, then accept WS Full Format activity, profile, avatar and business fields without inferring mobile-money capacity.
A Malawi WhatsApp Full Format check does not “complete every customer profile” for +265 phones. It accepts timestamped activity, profile, avatar, business-account and mapping observations returned by the defined WS task after phone provenance is established. Nulls remain null, and no field may be expanded into income, mobile-money ability or personal credit.
Establish where +265 came from
The ITU maintains a Malawi national numbering-plan entry. A business still preserves country_evidence for every record, such as a form country choice, contract or explicit dataset description. Filename, personal name and language cannot prove Malawi origin.
Preserve three columns during cleanup
| Column | Content | Purpose |
|---|---|---|
| phone_raw | Original input | Audit and recovery |
| phone_normalized | +265 candidate under current rule | Task input |
| format_state | Passed, exception or review | Prevents guessed digits |
Do not add one code to a mixed source
An export-sales file can combine local Malawi customers, diaspora, neighboring-country phones and temporary contact points. Separate source strata first. Conflicting country evidence or suspect length enters exception. Passing format shows only that parsing was possible; it says nothing about telecom service, WhatsApp registration or the original holder.
What Full Format Excel may contain
AIPUSH WS Full Format may include phone, activity time, active days, gender, age, avatar, skin tone, avatar type, business-account observation and mapped WhatsApp phone. “Full” names this defined set. It does not promise a value in every cell or include chat, balance, payment and purchase intent.
Accept by field family
| Family | Acceptance | Limit |
|---|---|---|
| Activity | Time format, observation date, nulls | Expires |
| Profile | Unknown, applicability, stratified coverage | Not identity truth |
| Avatar | URL/null, type and people count | Does not prove holder |
| Business account | Encoding and coverage | No trust guarantee |
| Mapped phone | One-to-many/many-to-one collisions | Never overwrites CRM key |
TXT carries phones only
The upload is one phone per line as TXT and contains no name, location, order, mobile-money information or permission. An internal crosswalk stores batch_row, contact_id, raw value and normalization version. Excel rejoins through that crosswalk rather than row order.
Mobile money is another data domain
If a Malawi use case needs payment method, evidence comes from the company’s order, payment callback or customer choice. +265, activity, avatar, skin tone and business-account observations cannot establish mobile-money use, balance, income or ability to pay.
Small cells need re-identification protection
Crossing region, age and avatar type can make a small group identifiable. Aggregate reports use minimum cell sizes and combine tiny strata. Marketers do not receive individual profile exports, and high-impact decisions never use inferred attributes.
Activity observations need a lifetime
Store checked_at and refresh_after and stop ranking use after expiry. Recheck only a small set near a decision while purpose and permission remain valid. Do not rerun the entire database merely to keep a workbook visually current.
Evidence that acceptance is complete
Record unique input, exceptions, returns, unknowns, field coverage, collisions, task version, allowed use and deletion date. The value of Malawi Full Format is an explainable set of wider observations—not an illusion of complete customer wealth and identity.
