LINE Number Checker Pitfalls: TXT Preparation, Task Choice, and Excel QA

When a LINE number-checking result “looks wrong,” locate the defect in input, task choice, return structure or interpretation. Frequent causes are damaged TXT phones, confusion between Registration and Gender/Age, and missing values converted to “no.” AIPUSH currently has no LINE Activity task, so neither the workflow nor the article should invent one.

Failure 1: the spreadsheet changed the phone

Scientific notation, lost prefixes and altered trailing digits can corrupt input before TXT is generated. Store phone columns as text and preserve phone_raw. If the source workbook already changed digits, applying text format afterward cannot reconstruct them.

Failure 2: the country code was guessed

LINE spans several countries whose domestic prefix rules are not interchangeable. Normalize only records with country evidence. Missing country, implausible length or area-code conflict belongs in exception_queue. A string that merely resembles a Japanese phone is not evidence.

Symptom	Possible cause	Inspect first
Many records return nothing	Country-code or digit corruption	phone_raw and rule version
Row count shrank	Silent deduplication or blanks	Unique TXT lines
Results cannot join to CRM	Inconsistent key	contact_id crosswalk

Failure 3: the wrong LINE task was selected

LINE Registration returns phone and registration result. LINE Gender and Age may return phone, user ID, nickname, gender, age, avatar, people count, avatar type and skin tone. There is no LINE Activity service, so do not promise activity time or active days.

Failure 4: a profile task was chosen because it has more columns

If the decision needs registration only, collecting nickname, avatar or demographic observations expands risk and interpretation work. Age, gender and pictures may be unknown or unrelated to the account holder. Choose a task from the decision—not from its column count.

Failure 5: the TXT contains headers and notes

AIPUSH accepts TXT with one normalized phone per line. Do not include a “phone” header, name, country note or comma-separated CRM row. Record encoding, row count, unique count and hash after generation, then upload that frozen artifact.

Failure 6: every blank became false

State	Correct storage	Wrong treatment
Explicit unregistered	Task-returned negative state	Merge with blank
Missing / unknown	Preserve reason or absence type	Automatic false
Processing error	Error code and batch	Count as unregistered

Failure 7: returned Excel overwrote the master

Load the workbook into staging, add batch_id, checked_at and task_name, and join normalized phone to contact_id. Review one-to-many, many-to-one and unmatched rows. A returned user ID or nickname should not become a CRM master key without governance.

Failure 8: platform fields were mistaken for permission

LINE registration, user ID and profile observations do not establish consent to marketing. Contact still requires provenance, channel scope, purpose and opt-out evidence. A new check never revives an explicit suppression.

A ten-minute acceptance checklist

1. Input is a one-phone-per-line TXT.
2. The country rule has evidence and a version.
3. The task exactly answers the question.
4. Input and return counts reconcile.
5. Missing states retain their meaning.
6. Excel reconnects without overwriting the master.
7. The report clearly states that no LINE activity field exists.

The goal is not zero exceptions. It is an accountable destination for every exception.