Article summary
Compare the actual fields, questions and freshness boundaries of Viber Registration and Activity checks without treating activity as permission.
Viber Registration asks whether a registration observation exists for the phone. Viber Activity asks what activity-related fields are returned for an identified record in this check. Registration supports candidate-channel routing; activity can assist timing inside an existing business relationship. They are not basic and premium versions of one product, and every phone should not run through both by default.
A 30-second choice starts with the decision
If the only question is whether Viber may be a service channel, begin with Registration. If a permitted Viber list already exists and the team needs a current usage observation for support ordering, consider Activity. If the question is whether the phone is disconnected, neither task is a telecom dead-number check.
The field sets define the boundary
| Dimension | Viber Registration | Viber Activity |
|---|---|---|
| Returned fields | Phone, registration status | Phone, active days, mid, offline time |
| Core role | Candidate-channel routing | Freshness observation for an existing list |
| Time metadata | checked_at | checked_at and expires_at |
| Cannot prove | Telecom validity or willingness to receive messages | Purchase intent, identity or future reply |
Scenario one: an order update needs channel routing
For a customer who chose to receive order updates, Viber Registration can help create a candidate route before the organization applies the customer’s channel preference and sending rules. There is no need to collect mid and activity timing to answer a registration question.
Scenario two: a support backlog needs ordering
If every contact in a queue has a valid support ticket, activity may be a secondary ordering input. Urgency, promised deadline and customer request remain primary. Recent activity must not move a routine question ahead of safety, refund or account-access cases.
Scenario three: legacy CRM is not ready for Activity
Old lists commonly lack provenance, permission or a recent phone confirmation. Resolve formatting, duplicates and processing basis first. Running Activity on an unknown-source phone cannot restore permission and does not prove that the number still belongs to the original contact.
mid is not the CRM customer key
Store mid as a platform-related identifier observation rather than replacing contact_id. When one phone appears under several CRM records or the returned relationship changes, create a conflict queue. Update an association only after separate, reliable business evidence resolves it.
Offline time needs visibility and freshness context
Viber’s Privacy Policy describes connection status and activity data as information processed within the service, while visibility depends on settings and use context. Offline time is therefore a task-time observation, not evidence of a person’s daily routine or location.
When a cascade is justified
A “Registration first, Activity for candidates” cascade makes sense only when the decision genuinely needs two evidence layers, the processing basis covers both, and registration can prevent unnecessary downstream work. Define the stop rule and expected reduction first. Do not make two tasks the default merely because both exist.
Evaluate cost by decisions supported
Count how many explainable channel or queue decisions each task enabled and how many observations remained unused because of unknown, expiry or collision. More fields are not automatically more economical. If activity never changes service ordering, continuing to collect it adds no operational value.
TXT is shared, but Excel acceptance is not
Both workflows begin with one phone per TXT line, but their workbooks have different acceptance rules. Registration expects phone and registration status. Activity also validates mid, active days, offline time and freshness. Do not populate one fixed spreadsheet template with fields a task never returned.
A practical selection rule
- Write down the business decision.
- Select the narrowest task that directly supports it.
- Confirm phone provenance, permission and stop state.
- Give every returned field unknown, conflict and expiry states.
- Review whether the field actually changed a decision.
Neither Viber Registration nor Activity is inherently more advanced. The right service uses the fewest fields needed for the current question and can stop using them when evidence expires, conflicts or loses permission.
