Article summary
Start with Vietnam +84 cleanup, choose Zalo Registration, Activity or Gender and Age for the actual question, and accept the returned Excel fields correctly.
Zalo Number Checking should not mean running every task against the same Vietnam phone list. It begins with the question the list must answer. Checking Zalo registration, using a recent activity observation to order support work, and conducting permitted aggregate audience research require different tasks and controls. Choosing the wrong task creates more risk than a stray space in a phone number.
First separate +84 attribution from the Vietnam market
The Viet Nam numbering-plan entry maintained by the ITU records +84 and the country’s mobile resources. +84 identifies a numbering plan; it does not prove that the holder is currently in Vietnam. Likewise, a foreign phone entered on a Vietnam form should not be forced into +84. Keep phone_plan_country separate from customer_market.
Preserve the evidence before normalizing
Retain phone_raw and create phone_candidate as a separate value. Convert national notation only when source context supports Vietnam. Values damaged by scientific notation, mixed with extensions or missing digits enter an exception queue. A familiar carrier prefix is not evidence for inventing a missing digit.
Choose one Zalo task for one question
| Business question | AIPUSH service | Actual fields | Does not answer |
|---|---|---|---|
| Is the phone registered on Zalo? | Zalo Registration | Phone, registration status | Will the person reply? |
| What activity observation is available now? | Zalo Activity | Phone, user ID, activity time, nickname, active days | Purchase intent |
| Is approved aggregate profile research feasible? | Zalo Gender and Age | Phone, user ID, activity time, nickname, gender, age, avatar, avatar count, avatar type, skin tone | Verified identity |
Registration supports channel routing
A registration observation can place Zalo among the candidate channels for an existing service relationship. It does not create permission to send marketing. Not registered also does not mean a telecom dead number; the phone may still work for calls, SMS or another platform. Store zalo_registration_observation separately from telecom_validity.
Activity supports timing, not intent scoring
Activity time and active days have a check time and visibility boundary. They may help order service work where contact is already expected, but “recently active” does not mean “ready to buy.” A +84 holder may also be in another time zone, so an explicit contact preference outranks a schedule inferred from country code.
Define prohibited uses before requesting profile fields
Gender, age, avatar, skin tone and avatar type are restricted profile data. Document purpose, permitted viewers, retention and prohibited decisions before processing. Do not use them for employment, credit, insurance, healthcare, outreach to minors or other consequential treatment. Do not extend an avatar into ethnicity, religion, health or income claims.
Zalo’s privacy information supplies a useful boundary
Zalo’s privacy information explains that account details, contact synchronization and activity information depend on what users provide, authorize and do within the service. Receiving a field does not grant unlimited reuse for any purpose or duration. The organization still needs its own lawful basis, purpose limitation and deletion rules.
Let TXT carry only phone numbers
Upload a TXT file with one phone per line and no name, order, city, permission record or conversation. An internal manifest retains input_id, source, purpose, task_type and batch_id. The returned Excel rejoins through input_id. Separate task batches can then receive different access controls and be deleted without damaging the CRM master record.
Preserve unknown and conflict states in Excel
Distinguish returned, unknown, format_exception, expired and mapping_or_id_conflict. An empty field must not become “no.” A changed nickname or avatar should not trigger a customer merge. If a returned user ID conflicts with an existing relationship, quarantine the record before changing a primary key.
Avoid three broken workflows
- Running the widest-field task by default and collecting unnecessary data.
- Converting an activity observation directly into a sales-priority score.
- Treating +84 as proof of location and automatically assigning language, time zone and region.
Use a batch acceptance sheet
The delivery record should state source rows, unique phones, formatting exceptions, selected task, field coverage, unknowns, conflicts, check date, use-by date and deletion date. The owner must be able to explain in one sentence why this task was selected. If the reason is only “more fields are better,” the task needs redesign.
A defensible Zalo Number Checking method does not maximize columns. It aligns +84 evidence, a specific question and the exact Excel fields. Answering only the approved question makes the result easier to use responsibly in a real Vietnam-market workflow.
