Article summary
Assign a use window, expiry state and recheck trigger to Lithuania +370 WhatsApp Activity observations instead of treating old Excel as a permanent audience label.
A WhatsApp Activity result is not a permanent list attribute; it is an observation with a check time. A Lithuania +370 project should decide the supported action and validity window before upload. Otherwise an old Excel file can continue pretending to describe the present.
Define the business clock first
| Clock stage | Data state | Permitted action |
|---|---|---|
| Not checked | unknown | No activity ordering |
| Inside window | current_for_purpose | Use in approved queue |
| Outside window | expired | Historical evidence only |
| Purpose ended | delete_or_aggregate | Remove person-level temporary data |
Derive the window from the action
Support-backlog ordering, short campaign follow-up and long-term customer research require different time granularity. Write the next action first, then decide whether activity time and active days are needed. Do not collect them merely because the task exists.
+370 controls phone entry only
Preserve phone_raw and create an international candidate from reliable country evidence. The numbering plan does not prove residence, citizenship or language. A Lithuania customer using a foreign phone keeps that phone’s original code.
Treat Excel fields as observation events
WhatsApp Activity may return phone, activity time, active days, business-account observation, avatar and mapped phone. Append checked_at, task_version and source_batch to each row. A later run must not silently overwrite an earlier observation.
Expired does not mean inactive
When the use window ends, the state becomes expired rather than inactive. Expiry says the evidence no longer supports a current decision; it says nothing about what happened to the phone afterward.
Design minimisation into an EU list
The organisation should assess purpose, necessity, transparency, access, retention and data-subject rights for its circumstances. If registration observation is enough, do not add activity fields. Seek qualified advice where the processing basis is uncertain.
TXT and result workbooks have different lifetimes
TXT contains one phone per line and is cleared under the execution process. The internal crosswalk retains only reconnection data. Returned Excel enters restricted staging; after expiry, delete person-level files or retain only aggregates that cannot identify a person.
When a recheck is justified
Recheck only when a new, specific and approved decision exists and the prior result has expired. Do not scan the entire database on a calendar merely to “keep data fresh,” because that phrase is not an unlimited purpose.
The final action for a Lithuania workflow
Add four fields to the task ticket: purpose, checked_at, valid_until and delete_after. They prevent long-term misuse more effectively than a headline activity hit rate.
