Article summary
Telecom line status and Viber registration are separate layers; compare their four combinations, fields, reassignment risks and permission boundaries.
Viber Registration is not a synonym for “empty-number detection.” Empty-number validation usually describes whether a telecom line is allocated, disconnected or reachable. Viber Registration describes a platform state returned in the current run. The layers can disagree and change at different times.
Use a two-dimensional view
| Telecom line | Viber registration | Possible situation |
|---|---|---|
| In service | Registered | Both layers have positive evidence |
| In service | Unregistered | Usable line without a platform account |
| Disconnected / unknown | Historically registered | Timing or reassignment |
| Unknown | Unknown | Insufficient evidence |
Viber Registration has a narrow scope
AIPUSH Viber Registration exports phone and registration result. It does not return SIM state, carrier, portability, billing or voice/SMS reachability. Product copy must not call it a carrier empty-number test.
When telecom validation is required
Voice calling, SMS delivery and base-list hygiene require lawful, appropriate carrier or telecom evidence. Use Registration to organize Viber platform state. If both are performed, retain provider and observed_at separately and never overwrite one with the other.
A TXT format defect is not a negative state
| Result | Class | Count as unregistered? |
|---|---|---|
| Explicit negative | Platform observation | Yes, for this run |
| Blank / unknown | No definitive answer | No |
| Phone-format failure | Input error | No |
| Unreconciled row | Pipeline error | No |
Upload one phone per line and retain the source
AIPUSH accepts TXT only. Normalize by country rule while retaining phone_raw, contact_id, country_evidence and rule version internally. A phone damaged by spreadsheet scientific notation is not an empty number.
Reassignment changes the person
A discontinued phone may be assigned to a new holder. A new in-service or Viber registration state does not prove continuity with the old CRM contact. Reconfirm the relationship before reactivating a long-dormant phone.
Platform state has an observation date
Registration, deletion and phone changes alter results. Preserve batch_id, checked_at and TXT hash. When runs conflict, investigate time and input rules rather than using the latest value to erase history.
Activity is a third question
Choose Viber Activity for active days, mid and user offline time. It is still not telecom reachability or contact permission. Do not collapse all three into a single “valid phone” label.
Permission is a fourth question
A phone that is in service and registered on Viber may still lack messaging permission. Provenance, Viber scope, purpose and opt-out determine contact. Explicit suppression has final veto power.
A minimal decision tree
- For voice/SMS line information, use telecom evidence.
- For Viber registration, use Registration.
- For Viber activity observations, use Activity.
- For marketing eligibility, use the permission ledger.
Do not leave one “valid” column in the report
Show telecom_status, viber_registration, viber_activity and permission separately with source, date and unknown reason. Independent layers reveal where the actual defect belongs.
