Article summary
Understand what WS activity time and active days can support, why both need a check timestamp, and why neither proves intent, consent, availability or account ownership.
WhatsApp Activity Checking records a platform activity observation at a point in time. Its two central fields—activity time and active days—need a reference timestamp, time-zone rule and expiry. Without that context, a number in Excel looks precise while saying very little.
Begin with the AIPUSH output
WS Activity may export phone, activity time, active days and mapped WhatsApp phone. It does not return conversation text, purchase intent, reply probability or marketing permission. Registration and profile tasks answer different questions.
Activity time is an observation, not an appointment
The field describes an observed platform state according to the task’s available granularity. It does not mean the person is online now, saw your message or is available to talk. Preserve the original value and its source time zone.
Active days needs a reference instant
| Data item | Required companion | Failure if missing |
|---|---|---|
| activity_time | Source zone and precision | Wrong calendar day |
| active_days | checked_at | Number cannot be reproduced |
| mapped phone | Input phone and review state | Incorrect CRM merge |
| freshness label | Versioned threshold | Permanent “active” status |
Why two runs can differ
Real activity changes, the check time moves and visibility can change. Compare runs with the same normalization, task version and time logic. A difference is not automatically an error; an unexplained schema or mapping change is a reason to investigate.
Convert time zones only in the display layer
Store an unambiguous UTC value plus source metadata. Render local business time for users, but do not overwrite the source field. When only a date is available, document its limited precision instead of inventing hours and minutes.
Create a decay policy
Define current, aging and expired states from the actual operational cycle. Once expired, the observation stops affecting prioritization. Refresh only a necessary, permissioned subset near a decision rather than running the entire CRM repeatedly.
Do not mistake activity for intent
A frequent WhatsApp user may have no interest in your offer; an infrequent user may be a committed customer. Commercial intent comes from first-party events such as a reply, quote request or order. Keep the signals in separate dashboard columns.
Do not mistake activity for permission
Consent and suppression have authority over activity. An opted-out phone remains blocked even when recently active. Likewise, an unknown-source phone cannot enter a campaign because the platform appears reachable.
Accept the batch with transparent counts
Report unique input, format exceptions, returned observations, unknowns, mapping conflicts, freshness states, checked_at and delete_after. This gives operators a useful time-sensitive input without pretending that activity reveals the person behind the phone.
