Article summary
Read the four AppShai WhatsApp activity fields without turning them into live monitoring or buyer-intent scores. Confirm time definitions and units before comparing results or setting thresholds.
After downloading a WhatsApp activity result, ask what each column means before deciding which records are “good customers.” AppShai’s task returns phone number, activity time, active days and WhatsApp mapped phone number. This is task output, not live online monitoring or an intent score.
Read the four fields across one row
- Phone number: identify the submitted record.
- Use it to match the result to the source list. Check for spreadsheet truncation before interpreting other columns.
- Activity time: retain the original value and checking date.
- This is the task’s time-related result. Confirm its format, time zone and definition in the current task instructions. Do not automatically equate it with last seen displayed in the app.
- Active days: do not invent a threshold from the heading.
- Confirm the unit, reference point and direction. A value of 7 does not, without a definition, establish a login within seven days. Neither larger nor smaller values can automatically be labelled more active.
- WhatsApp mapped phone: use the documented field meaning.
- Preserve it separately from the input. Do not overwrite the original customer number or infer another contact, verified identity or purchasing intent.
You may record the checking date yourself; that does not promise an additional date column in the service export. Retain blanks as unresolved rather than filling in “inactive.”
The same number in two exports may not be comparable
Suppose two saved results both show 7 under active days. That alone does not establish the same underlying date, nor let you calculate app use without knowing the field definition. Confirm the task instructions and observation times before comparing. This is an illustrative reading example, not a reported customer case.
WhatsApp’s last-seen and online indicators have their own meanings and visibility controls[1]. Those official mechanisms do not define AppShai’s export, establish a privacy bypass or reveal who viewed a profile.
Put activity information into a real decision
If registration is the only missing fact, select a registration task. Consider WhatsApp activity checking when time-related signals would serve an authorized existing-list purpose and the returned values can be explained.
A customer’s question, order stage and selected contact channel are often more useful for deciding how to assist than an isolated activity number. Treat activity as additional context, not a reason to delete a customer or send repeated messages.
See the WA/WS task-choice guide for registration options. For a disputed activity value, give support redacted column headings, original values and task details rather than asking which numerical band contains the “best” customers.
References
- WhatsApp: About last seen and online — official visibility context, not AppShai field definitions.
