Article summary
Separate El Salvador +503 local phones from diaspora records, then validate WS Full Format fields, mappings, missing values and permission.
A customer connected to El Salvador does not necessarily use +503, and a +503 phone does not prove that its holder is currently in El Salvador. Diaspora customers, US +1 phones, cross-border families and local businesses can coexist in one database. Preserve separate evidence for phone country, customer market and contact permission before a Full Format run.
+503 commonly carries an eight-digit national number
Retain phone_raw and country_evidence, then validate the eight-digit structure after +503 under the current El Salvador numbering plan. Do not add an invented trunk zero or force every Spanish-speaking contact into +503. Version range rules and their effective dates.
| Customer context | Phone handling | Market field |
|---|---|---|
| Local El Salvador phone | Validate +503 and eight digits | Confirmed by business provenance |
| Diaspora customer using +1 | Retain the +1 rule | May still relate to the El Salvador market |
| Country conflict | Manual exception | Never guess from language |
Full Format answers a field-coverage question
WS Full Format includes phone, activity time, active days, gender, age, avatar, skin tone, avatar type, business account and WhatsApp mapped phone. It cannot confirm remittance behavior, residence, family relationships, income or purchase intent.
Give four field families different controls
| Family | Acceptance test | Storage |
|---|---|---|
| Phone / mapping | Reconciliation and collision | Relationship table |
| Activity | Coverage and observation time | Expiring observation |
| Avatar / business | Missing states and result | Restricted purpose |
| Demographic-related | Unknown rate and bias | Restricted access |
Keep diaspora and family labels out of TXT
AIPUSH accepts TXT with one normalized phone per line. Name, residence, family link, order and permission remain internal, reconnecting through contact_id after Excel returns. The more sensitive a label is, the less reason it has to travel with the task.
Accept Excel separately by phone country
Report inputs, returns and exceptions for +503, +1 and other codes separately. Do not use every “El Salvador customer” as one phone denominator. This reveals whether failure originated in +503 transformation, an overseas phone rule or source data.
A mapped phone does not rewrite market assignment
A returned mapped phone may have a different country code and belongs in mapping_relation. It cannot automatically move a customer from an El Salvador market to a US market or overwrite customer-provided contact details.
Profile fields cannot identify diaspora status
Avatar, age, gender, skin tone and avatar type cannot prove ethnicity, nationality, immigration status, family relationship or remittance capacity. Unknown stays unknown and is never completed from image or language.
Permission and opt-out form a separate gate
Recent activity and business-account state do not create WhatsApp marketing permission. Every record still needs provenance, channel scope, purpose and suppression. The same opt-out rule applies to diaspora and local customers.
A qualified handover is not one match rate
Deliver the +503 rule version, cross-country-code strata, TXT hash, field coverage, unknowns, mapping collisions, observation date and permission distribution. Full Format supports cross-border customer data only when those differences remain visible.
