Article summary
Identify which Zalo Official Account records can support a phone registration check, and keep ID-only follower records useful for the work they already serve.
Open the follower export and read the column names. If a column contains a user ID, treat it as an identifier even if it is all digits. AppShai's Zalo registration task takes phone numbers. A numeric string that fits in a TXT file can still be the wrong kind of input.[1]
Zalo's OA follower documentation lists the follower identifier separately from information a user shares with the official account.[2] If you have only an identifier, first ask whether the job needs a phone check. Counting followers or replying in an existing OA conversation may already be possible from the OA record.
Read the records you have
The file has only an OA user ID and nickname. Keep it with your OA records. Use the identifier to avoid counting the same record twice. If you need to reply to a customer who has already written to the OA, continue in that conversation. There is no phone input for a registration rate.
A separate order file has a phone number and a customer reference you can link to the OA record. Confirm that the link comes from a real business interaction and that the information can be used for the job. Keep the OA ID and phone number in separate columns. Submit only the complete numbers that need checking. Match each result back by phone number. The OA ID still identifies the follower record.
The two files share a nickname. Leave them unlinked. If three OA followers and one buyer are called Minh, the name does not tell you which records refer to the same person. When the follow-up needs a connection, confirm it through an existing order or conversation. Both files remain usable while the match is pending.
Keep the totals tied to the right population
Imagine an event brought in 100 OA followers, and 40 of them supplied phone numbers the business can use. If you screen those 40, report the outcome for that phone list. Keep the other followers in the OA-only group. Their phone status is unknown, and including them as unregistered would misstate the result.
If the work ends with OA follower or reply counts, stay with those records. Run a registration check when there are usable phone numbers and a real need to know their Zalo status.
Sources
- AppShai Zalo registration check · Phone-number input.
- Zalo Platform Document Hub · OA follower information · Follower identifiers and information submitted to the official account.
