Article summary
Use Zalo activity time and active days to build expiring service queues while managing +84 phones, user IDs, nicknames, unknowns and aging lists.
The operational goal of Zalo Activity Checking in Vietnam is not to divide a list permanently into active and inactive people. It is to create a work queue that ages automatically. Activity observations have a check time, while orders, appointments and support cases have deadlines. Both clocks are needed to decide what the service team should handle today.
Design fields backward from a daily queue
Begin with events requiring work: an order awaiting confirmation, an approaching appointment, an open support case or a requested callback. Each event already has priority and deadline. Zalo activity only orders items sharing the same business priority. Without a business event, recent activity does not create a contact task.
Zalo Activity returns five defined fields
AIPUSH Zalo Activity may return phone, user ID, activity time, nickname and active days. Add batch_id, checked_at, expires_at and result_state in the enterprise staging model so operators know which task produced the observation and when it must stop influencing work.
Queue by the business clock, not only active days
| Queue | Admission evidence | Role of activity | Exit |
|---|---|---|---|
| Due today | Order or ticket approaches deadline | Order records within the same priority | Completion or deadline |
| Scheduled follow-up | User requested or permitted a callback | Assist timing | Completion, refusal or expiry |
| Needs review | ID conflict, unknown or old phone | No automatic order | Human resolution |
| Stay silent | No event or no permission | Not used | A new valid business event |
Route +84 formatting and attribution first
A Vietnam-market list may contain foreign visitors, diaspora customers and international partners. +84 is numbering-plan attribution, not current location. National-looking values without country evidence enter format_review. Do not add +84 to every short value merely to improve a pass rate.
User ID supports association; nickname supports display
Nicknames change, repeat and may contain emoji or multiple languages, so they are not CRM keys. If the user ID and phone relationship changes, preserve both versions under identity_review rather than merging silently. Displaying a nickname also depends on business need and access rights.
Unknown results still need routing
Unknown does not mean inactive. It can result from a format that was never submitted, a field that was not visible, a missing task row or an identity collision. Use not_submitted, not_returned, visibility_unknown and identity_conflict separately so technical blanks do not become claims that a customer left Zalo.
How the daily activity queue refreshes
- Freeze the day’s business-event snapshot.
- Exclude opt-outs, stops and ended purposes.
- Create TXT only for phones where activity can assist timing.
- Import Excel into staging and resolve collisions.
- Generate the day’s queue, then reread event and expiry state tomorrow.
List aging needs two curves
One curve tracks the business event from creation to closure. Another tracks the activity observation from checked_at to expires_at. When the event closes, recent activity cannot continue contact for that purpose. When activity expires but an urgent case remains, handle the case by its deadline rather than withholding service because activity is unknown.
Zalo privacy information argues against indefinite retention
Zalo’s privacy information explains that account and activity information depends on user input, authorization and use of the platform. An enterprise result table likewise needs purpose, access and retention limits instead of copying one nickname or activity observation permanently across systems.
Minimize TXT and zone Excel access
The TXT carries one phone per line and no order, name or ticket content. Data governance may review phone and user ID. A scheduling service can read time fields. Nickname appears only where an agent needs it. Zoned access is safer than distributing the complete workbook to every operator.
A weekly report without “activity-rate worship”
Report event completion, first-response time, unknowns, conflicts, opt-outs and complaints with a denominator by source. Recent-activity share describes a list; it is not a team performance metric or sales forecast. If activity ordering does not shorten service time, reduce its role.
The practical outcome of Zalo Activity Checking in Vietnam is an expiring service queue governed by events and freshness. It does not permanently label people or allow activity to outrank permission, deadlines and human review.
