Article summary
Distinguish phone-format and telecom issues from Viber registration and activity results, then route each outcome to the correct cleanup queue.
“Invalid Viber number” can describe at least three unrelated problems: the phone record is malformed, the number is not returned as registered on Viber, or the registered account lacks an activity value the analyst expected. A single invalid label hides the cause and makes later correction impossible.
The solution is a routing model. Each stage asks one question and sends the row to a named next queue.
The result-routing table
| Observed condition | Correct label | Next queue |
|---|---|---|
| Country code or length cannot be normalized | Input format unresolved | Source-data repair |
| Telecom source identifies a number problem | Telecom-status result | Carrier/data-steward review |
| Viber registration task returns not registered | Viber not registered | Channel-planning decision |
| Registration exists but activity field is unavailable | Viber activity unknown | Activity exception |
| Result cannot join to source | Reconciliation failure | Processing repair |
| Permission is absent or withdrawn | Policy suppressed | No activation |
Fix syntax before asking a platform question
Normalize the phone number with reliable country context, remove presentation characters and deduplicate exact keys. Do not use Viber registration checking to diagnose a missing country code. A malformed input cannot produce a trustworthy platform conclusion.
Store raw and normalized values separately. Rows that require a guessed country should remain in the repair queue.
Use registration checking for registration
The AIPUSH Viber registration task returns phone number and registration status. That result describes the selected Viber check; it does not establish whether the mobile subscription is active, who owns it or whether contact is permitted.
Process the prepared numbers as TXT and preserve the Excel result with its task and date. Label the CRM column viber_registration_result, not valid_number.
Use activity checking only for a defined timing question
The Viber activity service returns phone number, active days, MID and user offline time. These fields can support relative grouping inside an authorized cohort. They do not guarantee a reply and should not be used to fill a missing registration result by inference.
Keep unavailable activity in its own category. Zero, blank and processing failure may have different meanings.
Profile-related fields form a separate risk class
The Viber gender-and-age service can return skin tone, gender, nickname, activity fields, MID, avatar counts and types, age and avatar. Select it only when those fields serve an approved purpose. It is not the next automatic step after registration.
Limit row-level access, preserve unknown states and avoid making identity or high-impact decisions from profile classifications.
Merge Excel results through a staging layer
- Import phone-number columns as text.
- Apply the same normalization used for the outbound TXT.
- Join results to source IDs without overwriting the raw number.
- Assign each unmatched row to the routing table.
- Append task, run date and result as a new observation.
- Apply permission and suppression before producing an activation list.
Report the funnel, not one “valid rate”
A useful cleanup report shows source rows, format-qualified rows, unique TXT lines, Viber-registered results, activity-known rows, successful joins and policy-eligible records. Each number has a different denominator and answers a different question.
For example, a low activity-known share may reflect field availability rather than an inactive audience. A low format-qualified share points to source-data quality, not Viber adoption.
Write each denominator beside the percentage so later readers cannot mistake one stage for another.
The final naming rule
Give every status a platform and layer: phone_format_unresolved, telecom_invalid, viber_not_registered, viber_activity_unknown, result_unmatched or policy_suppressed. Avoid the universal word “invalid.”
Clear naming allows the right team to fix the right problem. Data stewards repair source values, the Viber task supplies platform observations, analysts reconcile fields, and the business owner decides permitted use. None of those jobs should silently replace another.
