Article summary
Choose LINE, Zalo or Viber from customer evidence and pilot outcomes, then compare each platform’s actual number-checking tasks without inventing interchangeable fields.
Do not choose LINE, Zalo or Viber only from a claim about what is popular in a country. Channel priority should come from contact choices, existing support evidence and a small pilot. Phone country, language and platform preference are different fields. Number checking returns task observations; it does not replace market research.
Inventory channel evidence first
By country, customer type and source, count explicit platform selections, existing conversations, meaningful replies and opt-outs. Search interest and download figures can provide context but should not dictate sending share. Cross-border customers may use a platform associated with another market.
The actual task matrix
| Platform | Available tasks | Key limit |
|---|---|---|
| LINE | Registration, Gender and Age | AIPUSH has no LINE Activity task |
| Zalo | Registration, Activity, Gender and Age | Fields differ by task |
| Viber | Registration, Activity, Gender and Age | mid and offline time appear only in applicable tasks |
Registration is the most comparable task
Registration centers on phone and registration result across the three platforms, supporting a platform-state inventory for an authorized existing list. Registration on several platforms does not mean a person wants messages on all of them.
Activity schemas cannot be compared as one metric
| Platform | Activity-related export | Comparison limit |
|---|---|---|
| Zalo | User ID, activity time, nickname, active days | Platform-specific observation |
| Viber | Active days, mid, user offline time | Different schema |
| LINE | No task | Registration cannot substitute for activity |
Profile tasks are not market selectors
Nickname, gender, age, avatar, skin tone and avatar type may be missing or unrelated to the holder. They cannot decide which country is “more valuable” or automatically choose language. Use customer behavior and service need.
Run a three-platform pilot
Sample people from the same source who have explicit permission for the relevant platform. Keep content, benefit and time window comparable. Measure meaningful reply, first-contact resolution, opt-out and complaint—not registration alone.
Use a separate TXT batch per platform
AIPUSH accepts TXT with one phone per line and exports Excel for the selected platform task. Give every platform its own batch_id and crosswalk; never collapse all results into one “valid phone” column.
Preserve the user’s preferred channel
Store preferred_channel, channel_source, confirmed_at and fallback_channel. Checking updates platform_observation only and never overwrites an explicit choice. When one platform is unavailable, do not automatically switch to another.
Separate language, market and phone country
preferred_language comes from choice or conversation, market from the business relationship and phone_country from phone evidence. Independent fields support travelers, diaspora, cross-border workers and multilingual customers without guessing.
When to expand platform investment
Scale when a platform repeatedly produces better service or qualified opportunities in a defined segment without higher opt-outs or complaints. A higher registration rate indicates possible coverage; it does not yet establish business value.
