Article summary
Follow the Viber send timeline to see how number checking, permission, content, frequency and recall control different risks.
A Viber message may be recallable, but an unwanted outreach event cannot be returned to “never happened.” A notification may have appeared, the recipient may have read or captured it, and brand trust or opt-out intent may already have changed. Most effective controls belong before send.
T-24 hours: establish why the list exists
Verify provenance, authorized sender, purpose, region and suppression. Viber Registration answers whether registration was observed at task time. It cannot convert an unknown-origin list into a permitted audience.
T-2 hours: select the necessary checking task
| Need | Task | Do not substitute it for |
|---|---|---|
| Registration observation | Viber Registration | Permission |
| Recent account observation | Viber Activity | Purchase intent |
| Aggregate profile research | Viber Gender and Age | Identity or high-impact decisions |
T-30 minutes: test content on a small sample
Inspect sender identity, language, links, time zone, frequency and exit path. Active days do not prove that now is an appropriate time to contact someone. A campaign window does not override quiet settings or an organizational frequency cap.
T-5 minutes: lock audience and content together
Only rows with valid permission, matching purpose, no opt-out, available frequency capacity and an approved content version enter the queue. An unknown value stops by default; bulk logic must not silently turn it into yes.
T+0: send is an irreversible event
At submission, record campaign_id, content_version, recipient_ref and sent_at. Even if the platform later permits recall, the organization must acknowledge that a delivery attempt occurred.
T+5 minutes: what recall can and cannot do
Recall may reduce continued exposure. It cannot guarantee that a notification was unseen, content was not copied or a complaint was not formed. It is incident mitigation, not a replacement for audience, permission and content review.
T+1 day: review causes, not delivery alone
- Wrong audience: repair provenance and record joining.
- Wrong permission: stop the purpose and update suppression.
- Wrong content: freeze the template and approval version.
- Wrong frequency: repair the cross-campaign counter.
Where AIPUSH results sit on the timeline
Upload TXT with one phone per line and land Excel in staging. Registration, active days, mid and offline time are pre-send account observations with checked_at. They never overwrite permission or frequency controls.
The most useful metric is not recall success
Measure errors blocked by pre-send rules, unknown rate, opt-out response time and incident recurrence. Viber’s Privacy Policy provides official context for platform data handling, while the organization remains responsible for its own outreach governance.
One operating principle
Treat number checking as one timeline input, permission as the gate, content and frequency as send controls, and recall as last-line mitigation. In that order, a post-send button cannot be used to conceal a pre-send failure.
