Article summary
Prepare Swiss +41 numbers for a WhatsApp activity task, interpret activity time and active days, and build auditable cohorts without equating online presence with consent or message reads.
A Swiss WhatsApp activity result should describe a time-bounded observation, not become a permanent label attached to a customer. The WS activity export contains activity time and active days alongside number-mapping fields. Those values become useful only after +41 formatting, source reconciliation, a stated screening date and a business-defined review window are documented.
Direct answer: use activity time and active days to build review cohorts that fit a specific campaign or CRM cycle. Do not merge those task outputs with WhatsApp’s public “online,” “last seen” or read-receipt concepts, and do not treat any activity result as permission to send marketing.
Place the Swiss domestic prefix correctly
Switzerland uses country code +41 and domestic trunk prefix 0. The Federal Office of Communications explains that the trunk prefix is not part of the international number. Most fixed, mobile and value-added national numbers contain nine digits. A domestic mobile presentation such as 079 123 45 67 therefore becomes +41 79 123 45 67 internationally.
| Source representation | Digits-only working copy | Control |
|---|---|---|
| 079 123 45 67 | 41791234567 | Remove domestic 0 and add 41 |
| +41 79 123 45 67 | 41791234567 | Remove presentation characters only |
| 0041 79 123 45 67 | 41791234567 | Normalize the international access notation |
| 41 prefix with unexpected length | Exception | Do not pad or truncate automatically |
See the Swiss E.164 numbering plan and OFCOM’s assigned-number resources.
The activity task returns four specific fields
AppShai documents phone number, activity time, active days and mapped WhatsApp phone number for WS activity screening. The product description does not require an article to speculate about the underlying algorithm. Store the returned values with the task date and source-list version so that future comparisons have an auditable baseline.
| Field | Storage approach | Question supported |
|---|---|---|
| Phone number | Text | Which upload row produced this result? |
| Mapped WhatsApp number | Beside the source value | How does the returned number relate to the source? |
| Activity time | Original result plus task date | What time value was returned in this batch? |
| Active days | Numeric value with documented cohort rules | How should the list be grouped for a stated review? |
Online, last seen and the exported task values are separate layers
WhatsApp defines “online” as having the application open and connected to the internet, while noting that this does not mean a message has been read. People can also limit who sees their last-seen and online information. Read WhatsApp’s last-seen and online guidance for those platform-level definitions.
Do not assume that AppShai derives its fields from one named public signal. Activity time and active days are documented task outputs. WhatsApp’s help material serves a different purpose: it demonstrates why public presence, delivery, reading, replying and consent must not be collapsed into one “active user” claim.
Define the review window before assigning a cohort
There is no universal number of days that makes a person “highly active” for every business. An appointment reminder, a long-term customer reactivation and a quarterly database review operate on different timelines. Write the operational date and cohort thresholds into the analysis before looking at the distribution.
| Use case | Window design | Next control |
|---|---|---|
| Upcoming customer event | Short review period tied to the event date | Confirm permission and message expectation |
| Historical customer reactivation | Compare several active-day bands | Run a limited test rather than a full-list send |
| Quarterly CRM maintenance | Retain current and prior task results | Review change instead of deleting from one snapshot |
| Source-quality assessment | Compare activity and unknowns by acquisition source | Investigate the data source, not individual recipients |
Language must come from the customer record
A Swiss contact list may contain German, French, Italian and English communication preferences. Neither country code +41 nor an activity value identifies the language a person wants to receive. Keep language preference as an independent field supported by customer choice, prior communication or a legitimate regional record.
A sensible sequence segments lawful business purpose and language first, then examines activity within those groups. Reversing that order can produce a technically tidy list that sends the wrong language to the right telephone numbers.
Execute the TXT-to-Excel process and reconcile results
- Preserve the original CRM data and create normalized +41 and exception columns.
- Write the reviewed telephone numbers to a TXT file, one number per line.
- Choose WS activity screening on AppShai WhatsApp Number Checker.
- Export the Excel workbook when processing finishes; Excel and CSV are not accepted upload substitutes.
- Reconcile the phone and mapped-phone columns before applying cohort rules.
- Record the task date, thresholds, unknown count and source-list version.
If the project also needs registration, picture or demographic fields, confirm those purposes separately or decide whether the wider WS full-format task is justified.
Activity screening does not create marketing permission
A returned activity time or active-days value supports list analysis only. It does not prove that the person agreed to receive a business message, that a future message will be delivered, or that the recipient will read or answer it. Consent source, opt-out status and communication purpose belong in the CRM or consent-management process.
Maintain two separate controls: an activity cohort from the screening task and a contactable status based on the business relationship and permission evidence. A record moves to a communication queue only when both satisfy the current use case.
How often should a Swiss activity list be checked?
The useful interval depends on how quickly the list changes and why it is being reviewed. A short campaign can follow its own operating window, while a long-lived customer list may need less frequent snapshots. Record the screening date and the time range used on every run.
Before comparing two exports, confirm that the +41 format, list source and screening conditions are consistent. A changed result describes two different observations; it should not become a permanent “active user” or “inactive user” label.
