Article summary
Philippine customers may keep +63, a local foreign phone or dual SIMs; interpret WS Registration with provenance and time rather than inferring location from country code.
Philippine customers and +63 phones are not identical sets in a WhatsApp Registration project. Overseas workers, seafarers, migrants and cross-border families may retain +63, use a local phone abroad or keep dual SIMs. Customer market, phone country and current location need separate evidence.
Preserve domestic notation during +63 conversion
Store phone_raw and country_evidence, then handle the national trunk prefix under the current Philippine rule to create +63 international notation. NTC numbering material distinguishes the trunk prefix from the national number; fixed and mobile structures should not be forced through one length rule.
| Context | Phone strategy | Do not infer |
|---|---|---|
| Local Philippine mobile | Validate +63 mobile structure | User is currently in the country |
| Worker abroad retaining +63 | Keep phone country and location separately | Send on Manila time |
| Foreign work-country SIM | Apply its actual country rule | No longer a Philippine customer |
| Dual SIM | Version several phones per person | Delete one automatically |
WS Registration provides a narrow answer
The core export is phone and registration result, representing a WhatsApp registration observation in this run. It does not reveal current location, SIM roaming, holder identity, occupation, remittance or contact permission.
Model one person with several phones
Separate contact_id from phone_id and store valid_from, valid_to, purpose, user_confirmed and preferred_for_whatsapp. A customer’s +63 and overseas phone can coexist; the newest import never erases history.
Generate TXT by each phone’s country
AIPUSH accepts one phone per line as TXT. Normalize each country code under its own rule, then process together or in separate batches. Name, employer, location, order and permission stay outside the upload.
Reconcile Excel through relationship state
| Return | CRM action | Prohibited action |
|---|---|---|
| +63 explicitly registered | Append observation date | Infer Philippine location |
| Overseas phone registered | Retain that phone relationship | Replace every +63 record |
| Unknown / error | Exception queue | Write unregistered |
| Repeated phone | Review sharing/reassignment | Merge identities automatically |
Obtain time zone from the user, not the phone
preferred_timezone comes from workplace, service address or user setting and carries updated_at. Do not schedule solely from +63 or guess online time from registration.
Reassignment requires identity reconfirmation
A long-dormant phone may have a new holder. One positive registration result does not prove the old customer remains. Confirm the recipient through an existing secure process before sending order, account or privacy information.
Permission may apply to one phone only
Authorization for service messages to a +63 phone does not automatically cover marketing to a temporary foreign phone. Bind permission to contact_id, phone_id, channel, scope and opt_out rather than copying it across a CRM record.
Do not infer occupation or remittance
“Overseas worker” explains one multi-country-phone context; it cannot be inferred from country code, avatar or registration. Immigration, income, family and financial behavior require independent lawful evidence.
Accept on relationship completeness
Report +63 rule pass, other country codes, multi-phone contacts, explicit states, unknowns, sharing conflicts and observation date. The valuable result is a time-aware customer-phone relationship—not one Philippine registration percentage.
