Zalo Number Check Preparation: A Complete List-to-TXT Guide for Beginners

Beginners often focus on how many accounts or settings they need for a Zalo check. The real preparation object is the list: where phones came from, whether country is known, whether formatting is traceable, which task answers the question, and who will use the Excel.

This guide assumes no advanced data-cleaning knowledge. It is designed for export teams preparing their own inquiry, customer, or event records for a Zalo task.

Direct answer: Use a traceable phone list, normalize and deduplicate by country-aware rules, export UTF-8 TXT with one number per line, and validate the task and Excel columns on a sample before scaling.

Turn “check Zalo” into one testable question

Zalo Registration Check returns phone and registration status. Zalo Activity is separate and may return phone, user ID, activity time, nickname, and active days. Demographic checking has a broader field set.

“Find Zalo customers” is too vague. A testable version is: which permissioned phones return a Zalo registration signal at the checked time?

Business question	Evidence required	Role of this workflow
Registered on Zalo?	Registration result and date	Yes
Activity signal?	Activity task fields	Choose separately
May we market?	CRM permission/opt-out	Not created by checking
High-value customer?	Order and need	Cannot infer

Beginner list-readiness table

Object	Ready state	Exception action
List source	CRM, order, form, or documented event	Do not use unknown provenance
Country field	Country/region known per row	Do not infer from length
Phone field	Stored as text, no scientific notation	Return damaged values to source
Permission and opt-out	Purpose, consent, exit traceable	Suppress opt-outs first
Internal ID	Every row returns to source	Create row_id if missing

Zalo is strongly associated with Vietnam, but a cross-border CRM can contain many countries. The platform name does not prove the numbering country of every record.

Create Zalo TXT from a mixed list

1. Step 1: Preserve the source export
   Never edit the only copy.
2. Step 2: Set phone to text
   Prevent digit and leading-character loss.
3. Step 3: Group by country
   Apply the appropriate rule to each group.
4. Step 4: Remove display characters
   Strip spaces, brackets, hyphens, and notes.
5. Step 5: Create normalized value and exception
   Separate unknown country, short code, and extension.
6. Step 6: Deduplicate after normalization
   Keep the CRM-ID mapping.
7. Step 7: Generate UTF-8 TXT
   One phone per line and no header.
8. Step 8: Accept a sample
   Confirm input, task, and Excel fields.

AppShai tasks accept UTF-8 TXT with one phone number per line; Excel is the completed task’s export. Do not place names, email addresses, companies, notes, or a header in TXT, and do not submit CSV or XLSX as the upload file.

Field boundaries among Zalo tasks

Export field	Meaning	Recommended destination	Does not establish
Phone, registration status	Zalo Registration	zalo_registered	Activity or consent
User ID, activity time, nickname, active days	Zalo Activity	zalo_activity_*	Identity proof
Gender, age, picture, etc.	Zalo Demographic	Controlled extended fields	Income, occupation, purchase power
Checked at	Internal task log	zalo_checked_at	Last customer reply

A Registration task should not be expected to include nickname or activity. Task selection, output fields, and CRM columns must match.

Six common beginner blockers

Failure symptom	Likely cause	Investigation order
TXT contains a header	First line is not a phone	Remove header and re-export
One line contains name and phone	Not one-number-per-line	Export phone only
Scientific notation	Wrong spreadsheet type	Return to text source
One country code applied to all	Country assignment wrong	Group by source country
Fewer columns than expected	Wrong task or expectation	Review field definition
Registered rows go straight to send	Permission not checked	Return to CRM eligibility

Keep an unexplained blank or missing row as unknown or pending review. Do not fill gaps with “no,” “not registered,” or zero merely to complete a report. Link the raw TXT, exported Excel, and exception file through the same task ID.

What to accept in the sample

Acceptance measure	Method	Purpose
TXT nonblank rows	Text count	Matches planned sample
Accepted rows	Task record	Find format rejection
Result rows	Excel count	Explain missing/duplicate
Column names/types	Field dictionary	Confirm task
Import matches	CRM-ID sample	Validate mapping

Include normal, duplicate, domestic-format, and exception examples. A sample that contains only clean rows validates an ideal case, not the actual rules.

Deliver Zalo results safely

Deliver a field note before the workbook. Explain which columns came from the task, which were added internally, how blanks behave, and which records still are not eligible for contact. Limit access to staff who need the data.

Data layer	Owner	Must preserve	Must not overwrite
Source list	Business owner	Source, purpose, permission, CRM ID	Check result
Normalized file	Data operator	Raw phone, normalized phone, exception reason	Source record
Task snapshot	Task operator	Task ID, date, service, input/output counts	Previous result
CRM import	System admin	Field dictionary, import batch, rollback file	Permission and lifecycle stage

One-page beginner checklist

• Use a documented business source.
• Store raw phone as text.
• Review missing-country rows separately.
• Normalize before deduplication.
• TXT has no header and one phone per line.
• Task is explicitly Registration, Activity, or Demographic.
• Accept Excel rows, columns, and blanks.
• Permission and opt-out decide contact eligibility.

After preparation, review the current tasks on the AppShai Zalo Number Checker. The essential beginner habit is preserving raw values, documenting exceptions, and stopping automated guesses when evidence is missing.

Frequently asked questions

Must every Zalo-check phone be Vietnamese?

Do not infer country from the platform name. Use list provenance and country fields; process multi-country data in separate rule groups.

Does Registration Check return a nickname?

Under the current field definition, Zalo Registration returns phone and registration status. Nickname belongs to Activity or another separate task.

Can TXT start with a Phone header?

No. Every line, including the first, should contain only one actual phone number.