Article summary
Prepare a UK +44 list for WhatsApp activity screening, reconcile mapped numbers, and interpret activity time and active days as dated observations rather than permanent customer labels.
UK WhatsApp activity screening is useful only when the result is tied to a source record, a task date and a defined business window. A +44 prefix does not by itself prove that a record is a mainland UK mobile subscriber, and an activity value does not prove consent, message delivery or future response. The practical goal is to create a reviewable cohort without turning one screening run into a permanent customer attribute.
Direct answer: normalize the telephone list without overwriting its source values, run the WS activity task, reconcile the returned and mapped telephone columns, then apply a documented time window. Keep unknown records separate and date every observation.
A +44 list can contain several numbering contexts
Ofcom administers the UK National Telephone Numbering Plan and publishes allocation data for geographic, mobile and other number ranges. Numbers beginning with 01 or 02 are generally geographic, while the broader 07 space is not a single undifferentiated mobile category. Corporate and location-independent ranges also exist. In addition, the Isle of Man, Jersey and Guernsey participate in the wider +44 environment.
| Available signal | Reasonable use | Unsupported conclusion |
|---|---|---|
| Country code +44 | Create a UK-plan candidate pool | Assume one jurisdiction or current operator |
| Domestic 07 format | Review the relevant range | Treat every 07 number as an ordinary mobile |
| CRM country = United Kingdom | Preserve the acquisition label | Assume the telephone data is correct |
| Activity task result | Build a dated analytical cohort | Infer permission, reading or reply |
Use the current Ofcom numbering resources and its number allocation downloads when a range-level fact matters. Ofcom updates allocation files, so an old prefix should not be treated as permanent proof of the current provider.
Preserve source, normalized and exception values
UK lists commonly mix domestic numbers beginning with 0, international +44 values, 0044 exit-code notation, spaces, brackets and hyphens. Normalize a working value for the task, but never destroy the value received from the CRM, form or partner file. The source value is part of the audit trail.
| Column | Example | Purpose |
|---|---|---|
| original number | 07700 900123 | Retains the original customer-list evidence |
| prepared number | +447700900123 | Creates the task-ready telephone value |
| normalization_action | removed domestic trunk 0 | Explains what changed |
| region_review | UK-plan candidate | Prevents premature geographic attribution |
If a spreadsheet has already converted a long number to scientific notation and the full digits cannot be recovered from the original source, quarantine the row. Adding guessed digits produces a plausible-looking but false telephone number.
What the AppShai WS activity task returns
The current AppShai workflow accepts a TXT file containing one telephone number per line. After the WS activity task finishes, the exported Excel workbook contains four documented fields: phone number, activity time, active days and WhatsApp mapped phone number. Excel and CSV files are not accepted input substitutes.
| Export field | Use | Control |
|---|---|---|
| Phone number | Input/result identifier | Keep it as text and preserve every digit |
| Activity time | Dated task observation | Record task date and time-zone convention |
| Active days | Supports a business-defined cohort | Do not invent a universal threshold |
| WhatsApp mapped phone number | Supports reconciliation | Review differences before updating the CRM |
Picture, age, gender and business-account columns belong to other documented services. They must not be promised in an activity-only export.
Online, last seen and activity screening answer different questions
WhatsApp’s official help material says that “online” means the application is open on the user’s device and connected to the internet. It expressly does not mean that the person has read a particular message. Visibility of “last seen” and “online” can also depend on privacy settings, contact relationships, blocking and temporary connectivity.
Those public interface concepts should not be merged with an AppShai export field. Read WhatsApp’s explanation of last seen and online for the product boundary, then interpret activity time and active days according to the screening task and its recorded date.
Define the cohort before opening the workbook
A recruitment follow-up, customer-support review, event reminder and long-term account-maintenance project do not share the same useful time window. The business should define the period and the lawful purpose before reviewing the results. Otherwise, analysts tend to move the threshold until the cohort has the preferred size.
- Current-review cohort: meets the documented project window and still passes consent and suppression checks.
- Later-review cohort: falls outside the current window but may be retained for a lawful future review.
- Unknown cohort: missing time, irreconcilable mapping or damaged source value; it is not automatically inactive.
Record the source-list version, task date, chosen time zone, input count, deduplicated count, reconciled count and unknown count. A percentage without its denominator and date cannot be compared reliably with the next run.
British Summer Time can change how teams read a timestamp
The United Kingdom moves between Greenwich Mean Time and British Summer Time. There is no need to speculate about the platform’s internal clock, but there is a need to document how the exported timestamp is displayed and how an analytical copy converts it. A London analyst and an overseas operations team can otherwise sort the same events into different calendar days.
Retain the original exported value. If the business needs UTC or a CRM-local time, create a separate calculated column and document the transformation instead of overwriting the task output.
Run the TXT-to-Excel process in a controlled sequence
- Create a working copy of a lawfully held list and retain its source record ID.
- Normalize +44 candidate numbers and quarantine ambiguous regional or damaged records.
- Deduplicate the working values and create a TXT file with one number on each line.
- Select WS activity screening on the AppShai WhatsApp Number Checker.
- Export Excel and reconcile the phone and mapped-phone fields before segmentation.
- Apply the pre-declared time window and report unknown records separately.
If the question is registration rather than activity, choose the documented registration task. If the project genuinely needs several other dimensions, review the purpose before moving to the broader WS full-format service. More columns are not automatically better data.
Activity and contactability belong in separate controls
An activity result does not grant marketing permission. It does not cancel an opt-out, prove a prior relationship or guarantee that a future message will arrive. Keep the screening observation in one field family and the consent, suppression and business-purpose evidence in another.
A record should enter a communication queue only when both the activity cohort and the organization’s contactability rules allow the current use. That separation makes the UK workflow explainable: the screening task describes what was observed, while the CRM explains why the organization may act.
Can an active result be contacted immediately?
Not on the strength of activity alone. Returned activity time or active days does not show that the person agreed to marketing, and it does not override an opt-out, block or the organization’s existing contact restrictions.
Before creating a follow-up list, check where the number came from, the available consent record and the current suppression status. Activity can help organize eligible records, but it is not permission to send a message.
