Article summary
Understand WhatsApp activity time, active days and mapped phone fields—and why these observations cannot directly represent an overseas customer’s purchase intent.
WhatsApp Activity Checking organizes activity-related observations available for a phone at the time of a check. It is not an “overseas customer purchase-intent detector.” AIPUSH WS Activity returns phone, activity time, active days and mapped WhatsApp phone. Using those fields to assist service ordering may be reasonable, but jumping from “recent activity” to “ready to buy” skips the business evidence in between.
Give activity a deliberately narrow definition
Activity is a timestamped observation, not a permanent identity. It depends on check date, visibility, account relationship and return state. Store activity_checked_at with the result and assign a use-by rule. Once expired, the observation stops influencing order instead of remaining indefinitely as a CRM label.
Activity and intent come from different evidence
| Signal | Can support | Cannot support alone |
|---|---|---|
| Activity time or active days | An observation for this check window | Budget or product need |
| Quote request, cart or reply | Specific business interest | A completed sale |
| Explicit contact permission | Allowed channel and message category | Unlimited frequency |
| Order or support ticket | An existing transaction or service relationship | Interest in unrelated offers |
Why a recently active person may have no demand
The person may be talking with family, handling unrelated work or reading a group. They may have bought elsewhere, have no current need or simply lack time to reply. Platform activity has no inherent causal link to the organization’s offer. Converting it into intent creates precise-looking lead scores that cannot be explained.
An overseas queue needs a business event
A defensible order starts with an event: a person submitted an inquiry, a support ticket approaches its deadline, an order awaits confirmation, an appointment is near or the user requested a call. Activity can assist sequencing inside one event queue. It must not pull people with no relationship or permission into marketing.
A two-by-two matrix is more honest than one score
Cross business event present/absent with activity observation current/unknown. Current activity plus an event may move a record earlier. An event plus unknown activity still follows its service deadline. Current activity with no event creates no contact. Neither signal means silence. This matrix prevents activity from deciding whether contact is allowed.
A mapped phone is a relationship conflict, not a bonus
If the mapped WhatsApp phone differs from the input, pause automatic write-back. Retain input_phone, mapped_phone, checked_at and conflict_reason, then consult customer confirmation or order records. Writing the mapped phone’s activity directly onto the original CRM contact can combine two people’s data.
WhatsApp policy puts permission before activity
The WhatsApp Business Messaging Policy says a business may contact people after they have supplied their mobile number and opted in to subsequent WhatsApp messages, and that stop, block and opt-out requests must be respected. A recent activity observation satisfies none of those conditions and cannot revive withdrawn permission.
Test scheduling value instead of claiming accuracy
Within an already permitted queue sharing the same business event, predefine two ordering approaches and compare time to first response, service completion, opt-outs and complaints. Report sample size and unknowns. Do not turn one small difference into a universal claim. If activity ordering does not improve service, remove the added complexity.
TXT and the permission ledger are different assets
Upload one phone per TXT line. Permission source, allowed message category, business event, time zone and stop state remain in an internal ledger joined by contact_id. Returned Excel first enters staging. Only records passing both permission_state and event_state can move into the relevant service queue.
Maintain three independent expiries
- Activity expiry: after the defined window, it no longer changes ordering.
- Business-event expiry: after the order, appointment or ticket ends, contact for that purpose stops.
- Permission expiry or withdrawal: the relevant message category is blocked immediately.
Refreshing an activity observation cannot extend the business purpose or permission automatically.
What an operational dashboard should show
Display total event-queue size, unknown activity fields, mapping collisions, response time, opt-outs and complaints—not only an “active-user percentage.” When operators see uncertainty and negative feedback, they are less likely to expand checks and contact merely to improve an attractive ratio.
WhatsApp Activity Checking works best as a perishable scheduling signal. Real customer intent still comes from inquiries, orders, conversations and stated needs. Whether contact is allowed remains governed by permission, business purpose and stop state.
