Article summary
Empty-number validation concerns telecom-line status, while TG Registration concerns a Telegram account result; their evidence and use are not interchangeable.
“Empty-number detection” and Telegram Registration answer different questions. Empty-number validation usually concerns whether a telecom line exists, is allocated or is usable. TG Registration returns a Telegram registration result in the current task. A line can be active without Telegram, and telecom and platform states may reflect different times.
Separate three systems first
| Layer | Question | Typical evidence |
|---|---|---|
| Telecom number | Is the line allocated, reachable or disconnected? | Carrier / authorized telecom validation |
| Telegram platform | Did this run return registration? | TG Registration |
| Marketing permission | Would the person expect a message? | Provenance and consent ledger |
All four state combinations are possible
| Telecom state | TG state | Reasonable interpretation |
|---|---|---|
| In service | Registered | Both systems have positive evidence now |
| In service | Unregistered | Usable line without platform registration |
| Unknown / disconnected | Historically registered | Timing or reassignment needs review |
| Unknown | Unknown | No forced classification |
Fields returned by TG Registration
AIPUSH TG Registration exports phone and registration result. It is not a carrier HLR query and does not provide SIM state, serving carrier, portability, billing status or reachability. Product copy must not call platform registration an empty-number test.
When telecom validation comes first
Use lawful, appropriate telecom evidence when the goal is SMS, voice or base-list hygiene. When the goal is Telegram platform-state organization, a normalized TXT goes to TG Registration. If both are needed, store two independent observation tables.
TXT preparation still controls quality
AIPUSH accepts one phone per line as TXT. Apply the relevant country code and domestic-prefix rule and retain phone_raw, country_evidence, contact_id and rule version. Scientific notation or a guessed code corrupts both forms of checking.
Do not overwrite one state with the other
Store telecom_status and telegram_registration in separate columns, each with provider, observed_at, batch_id and unknown_reason. Updating one never changes the other automatically.
Phone reassignment breaks identity continuity
A carrier may reassign a phone to a new subscriber. Telecom service and Telegram registration do not prove that the current holder is the old CRM contact. Reconfirm relationship and permission before reactivating a long-dormant record.
Unknown is not an empty number
Format error, task exception, no return and indeterminate state stay separate from confirmed disconnection or unregistered. Calling unknown “empty” exaggerates cleanup and can erase real customer records.
Registration does not permit a private message
Telegram’s official Spam FAQ explains that unwelcome messages to strangers can be reported and restrictions can follow. Platform registration and contact permission are independent gates.
A simple task-selection rule
For line state, use telecom evidence. For Telegram registration, choose TG Registration. For recent activity, use TG Activity and accept its wider schema. For marketing eligibility, consult the permission ledger. Do not let the familiar word “empty” cover four questions.
How to write the acceptance report
List telecom-state coverage, explicit Telegram states, unknowns, format errors, observation dates and sources separately. Only with independent denominators can the team identify whether a defect belongs to the phone line, platform or data pipeline.
