Article summary
Normalize Thailand +66 phones, distinguish local and visitor records, and govern WS Full Format fields without guessing language or permission.
A Thailand WhatsApp Full Format run must not collapse “+66 phone,” “currently in Thailand” and “prefers Thai” into one label. Tourism, cross-border commerce and expatriate work separate phone country, location, language and buying market. Normalize the phone first, then preserve evidence for every other attribute independently.
Handle the domestic zero in +66 conversion
Retain phone_raw and country_evidence. For a documented Thailand domestic phone, apply the current rule for the national prefix when adding +66. If +66 is already present, remove display punctuation only after validation. Implausible length or range enters manual review rather than a guess from a familiar mobile prefix.
| Record type | Phone handling | Business interpretation |
|---|---|---|
| Thailand local customer | Validate +66 rules | Still needs language and permission evidence |
| Visitor to Thailand | May retain another country code | Do not exclude by code |
| Cross-border worker | Preserve location evidence | Code does not equal time zone |
When Full Format may be justified
Select WS Full Format when an approved analysis genuinely needs activity, avatar, business-account and profile coverage. It returns phone, activity time, active days, gender, age, avatar, skin tone, avatar type, business account and mapped phone. Otherwise choose a narrower task.
Group fields by evidence strength
| Field family | Use | Common misreading |
|---|---|---|
| Phone / mapping | Record association | Permanent identity |
| Activity time / days | Recency observation | Travel location or intent |
| Avatar / business account | Account presentation | Company scale |
| Age / gender / skin tone | Limited coverage study | Verified demographics |
Do not upload itinerary or order data
AIPUSH accepts TXT with one normalized phone per line. Stay dates, flights, orders, names and language remain inside the business and reconnect through contact_id after Excel returns. Convenience is not a reason to expand task scope.
Give visitor lists a shorter validity period
A phone from one trip inquiry or temporary event should not remain indefinitely in a contact queue. Store purpose, valid_until and opt_out_at, and stop relying on activity observations when the period ends. A future trip requires new user action or permission evidence.
Manage language preference independently
+66 does not prove Thai preference, and a foreign phone does not prove English preference. preferred_language comes from choice, a support conversation or an explicit setting. Do not guess from avatar, name spelling or country code.
Accept Excel by provenance cohort
Report inputs, returns, missing fields and mapping collisions separately for local customers, visitors and cross-border workers. Combining them into one average “activity rate” hides differences in formatting rules and retention periods.
Profile observations cannot determine service treatment
Age, gender, skin tone and avatar type may be unknown or wrong. They must not determine denial of service, pricing, identity or sensitive targeting. Preserve raw returns, coverage, observation date and role-based access. Never fill blanks from an image.
Stop conditions for the Thailand run
Unexplained provenance, conflicting country rules, unreconcilable mapping, expired permission or opt-out stops a record from marketing. Rich Full Format output cannot repair those prerequisites. A qualified handover separates phone, location, language, permission and task observation instead of celebrating the workbook with the most columns.
