Article summary
Turn Indonesian 08 domestic phones and +62 international records into an auditable list before running a WhatsApp registration check.
An Indonesia WhatsApp registration project most often fails before upload. CRM records, trade-show forms, distributor lists and ecommerce orders may contain domestic 08 notation, international +62 notation, spaced numbers or values damaged by spreadsheet scientific notation. If the raw value is discarded during cleanup, a later “not registered” result may simply be a formatting defect.
Assign a provenance grade before normalization
| Grade | Country evidence | Action |
|---|---|---|
| A | The customer selected Indonesia and the phone uses 08 or +62 | Transform with a versioned rule |
| B | The order or store is Indonesian but the phone shape is unusual | Clean, then review a sample |
| C | Only an 08 prefix exists; no country field | Do not classify as Indonesia automatically |
| D | The country field conflicts with +62 | Quarantine for accountable review |
How domestic 08 and international +62 coexist
For a mobile record already supported by Indonesia evidence, the domestic trunk zero is normally not retained after +62. The transformation concept for “0812 …” is therefore “+62 812 …,” not “+62 0812 ….” Prefix shape alone cannot prove the country, so phone_raw must remain available.
Do not collapse the transformation into one phone column
Keep phone_raw, country_evidence, phone_normalized, normalization_rule and normalized_at. This allows the list to be regenerated when the rule changes. Overwriting the source phone makes it impossible to locate where an extra zero, missing country code or truncation entered the pipeline.
Use an exception table instead of guessing digits
| Exception | Likely cause | Action |
|---|---|---|
| +6208… | Domestic trunk zero was retained | Return to the source value and recompute |
| Value displayed as E+11 | Spreadsheet scientific notation | Recover from a text source; never guess truncated digits |
| One phone appears on several rows | Separate orders or contacts | Deduplicate the task input while retaining business relationships |
| Length or range mismatch | Wrong country or entry error | Write a specific exception_reason |
An external plan validates structure, not identity
The International Telecommunication Union’s Indonesia national numbering plan resource is one authoritative reference for +62 structure. A production system should still retain its own rule version and monitor newer notices from the responsible authority. A structurally valid phone is not proof of current assignment or WhatsApp registration.
Create a TXT file fit for the AppShai task
- Select a contact subset with documented provenance and a permitted purpose.
- Remove whitespace, hyphens, parentheses and invisible characters.
- Transform domestic 08 and +62 only when country evidence supports it.
- Leave uncertain records in the exception table rather than uploading them.
- Export UTF-8 TXT with one phone per line.
Names, orders, addresses and customer tiers should not travel with the phone list. AppShai accepts TXT only and exports the corresponding Excel workbook after the task finishes.
WS Registration answers a narrow question
WS Registration and WS Fast Registration center on phone and registration result. They do not provide recent activity, avatar, age/gender, permission or purchase intent. When business-account and mapped-phone fields are genuinely required, evaluate WS High-Precision Registration instead of assuming the basic task contains those columns.
Diagnose an unexpectedly high negative rate
Do not immediately conclude that the acquisition source is poor. Group results by source, normalization_rule and original notation. Compare +6208 mistakes, missing-country records, scientific-notation sources and clean +62 inputs. If the anomaly concentrates in one transformation path, correct that rule and rerun only affected records rather than repeating the entire CRM export.
Load registration observations into CRM safely
Import Excel into staging, add task_name, batch_id and checked_at, and reconnect records to contact_id through the task map. Missing, task error, unrecognized and explicit not-registered remain distinct. Preserve older observations and let a dated view expose the current state. An opt-out always overrides the technical registration value.
The quality standard for an Indonesia +62 project is not that every row looks valid. It is that every row can explain its original value, transformation basis, check time and stop condition when evidence conflicts.
