Article summary
Myanmar +95 resources change over time while WS Full Format returns a broad schema. Manage rule versions, 09 conversion, task minimization and Excel governance.
A Myanmar WhatsApp full-format project carries two distinct risks. National numbering resources can change as operators and authorities update allocations, while Full Format returns a substantially broader schema than Registration or Activity. Do not mechanically prepend +95 to every record beginning with 09. Preserve the rule version, verify country provenance and confirm that the ten-field output will change a defined decision.
+95 transformation needs evidence and a version
| Input form | Processing principle | Required record |
|---|---|---|
| Domestic mobile beginning 09 | When Myanmar evidence exists, remove the domestic leading zero and add +95 | Raw phone, country evidence, rule version |
| International +95 9… | Remove separators and check current resources | Normalization time |
| 9… without country code | Do not infer Myanmar from length | Exception reason |
| Fixed line or unknown range | Handle under the applicable numbering-plan rule | Number type and source |
Why a prefix table cannot be permanent
The ITU compilation of Myanmar +95 numbering updates contains multiple notices adding and withdrawing resources. A prefix table that was correct at one point can therefore become stale. Store rule_version and normalized_at. Send a record that fails the current rule to review rather than forcing it into a valid-looking form.
The WS Full Format schema
| Group | Fields | Primary governance issue |
|---|---|---|
| Identification and mapping | Phone, WhatsApp mapped phone | One-to-many collisions |
| Activity | Activity time, active days | Recency and observation date |
| Profile-related | Gender, age, avatar, skin tone, avatar type | Unknown values and use boundary |
| Account | Business-account field | Does not verify the business |
Ask whether Full Format is necessary
If the question only needs phone and registration state, choose WS Registration. When activity time and active days are required, WS Activity is narrower. Avatar or gender/age questions have their own tasks. Every extra field creates missing-value semantics, access controls, retention work and misuse risk. Full Format is not a default “best version.”
Use two tables to create the TXT upload
The internal source table retains contact_id, phone_raw, country_evidence, source and permission_scope. The upload table outputs only validated phone_normalized values, one per line. AppShai accepts TXT only; names, addresses, orders and marketing notes do not belong in the upload. A controlled batch mapping reconnects the TXT to the source without carrying unnecessary information.
Evaluate coverage before profile distributions
- Reconcile input, output, duplicate and exception row counts.
- Calculate non-missing and unknown rates by field.
- Report activity, avatar and age/gender coverage separately.
- Test mapped phones for one-to-many and many-to-one collisions.
- Sample against phone_raw and the transformation log.
- Confirm authorized users and deletion date.
If age is present for only a selected subset, calculating an overall age distribution first creates selection bias.
An avatar is not demographic proof
A picture may not depict the account holder, may contain several people, may be a logo or may be stale. Preserve skin tone, avatar type, age and gender according to the task’s original value and unknown state. Do not fill gaps through casual visual review or AI guesses, and never use such fields as identity proof, a service-denial feature or sensitive targeting evidence.
Put time on every observation
Store at least task_name, batch_id, checked_at, rule_version and source_file_hash. When new and old runs disagree, retain both and let a governed view select the current observation. A mapped-phone collision should stop automatic promotion. This design separates numbering-plan change, account-state change and processing error.
The qualified endpoint of a Full Format project
A successful delivery is not the fullest possible Excel sheet. It is an explainable data package: which phones became +95 under which rule, coverage for each of the ten fields, records that remained unknown or conflicted, authorized uses and deletion schedule. When the team only needs a narrow answer, returning to a smaller WS task is usually more professional than collecting additional columns.
