Article summary
A +64 prefix supports number normalization, not a current-carrier claim. Compare New Zealand numbering, number portability and WS Activity fields to build defensible customer-service cohorts.
A New Zealand contact sheet often turns three independent clues into one story: a prefix is treated as the current carrier, then recent WhatsApp activity is treated as purchase intent. Each leap exceeds the evidence. A sound New Zealand WhatsApp activity review keeps +64 formatting, number portability and platform recency in separate columns.
Evidence boundary: the numbering plan helps validate a telephone representation; portability warns that historical allocation may not identify the current network; activity fields describe a dated screening observation, not message reading or commercial interest.
Compare the four signals before building a segment
| Signal | What it can support | What it cannot establish |
|---|---|---|
| +64 international representation | The number is written within New Zealand’s plan | The holder is currently located in New Zealand |
| Historical prefix allocation | An original service category or allocation clue | The present provider after porting |
| Activity time or days | Recency evidence returned in this job | Reading, replying or buying intent |
| Registration status | A platform-registration result | Recent use of the account |
New Zealand does not use one universal phone length
An ITU operational bulletin published the New Zealand dialling plan updated in July 2025, listing different internationally diallable groups and lengths beneath country code +64. The industry Number Administration Deed site points users to that plan from its official numbering resources page. It is therefore unsafe to force every +64 record into one fixed-length mask.
Domestic representations ordinarily include a leading zero. International conversion removes that trunk zero before adding +64, so a domestic mobile beginning 02… becomes +64 2…. Validate the remaining length against the current service range instead of padding or truncating a value to fit an old spreadsheet formula.
Portability breaks the prefix-to-carrier shortcut
The New Zealand Commerce Commission describes local and mobile number portability as a service that lets customers change telecommunications providers while retaining their telephone number. Its 2025 portability review notes that local and mobile portability services have been regulated since 2001.
A prefix table can still help classify a number’s structure or original allocation. It should not populate a “current carrier” field as if no port had occurred. Where carrier information is genuinely required, use a dedicated, dated carrier source and store the lookup date.
Choose the task from the business question
| Decision needed | Relevant service | Expected evidence |
|---|---|---|
| Which records return as WhatsApp-registered? | WS Registration | Phone number and registration status |
| Which authorised contacts have a visible recent activity record? | WS Activity | Phone, activity time, activity days and mapped number |
| Which carrier serves the number now? | Neither | A separate carrier lookup with a date |
| Who agreed to receive marketing? | Neither | Consent and opt-out history |
This distinction avoids selecting the service with the most columns while asking it to answer a different question. Registration and activity are separate states and should never share one Boolean CRM field.
Normalize the +64 list without destroying the source
- Preserve the raw telephone value and the country-source field.
- Remove presentation spaces, brackets and hyphens.
- When the value is confirmed as domestic, remove the trunk zero and add +64.
- Validate its group and permitted length against the current plan.
- Deduplicate on the normalized representation and quarantine exceptions.
- Export only the number column to TXT, one number per line.
A domestic 021… entry and its +6421… counterpart should converge on the same comparison key. Keep transformations out of the raw column so a later reviewer can see exactly what was changed.
Assign a job to each returned WS Activity column
On the AppShai WhatsApp Number Checker, choose WS Activity, upload the TXT list and download the Excel output. Use phone number as the join key, retain activity time as source evidence, use activity days for ordering and send a differing WhatsApp mapped phone number to identity review.
Add the screening date and source-list version in the organisation’s own staging table. When a later run is required, append a new observation or save it in a history table. Overwriting the prior values removes the only way to understand change.
Design recency around the service cycle
An after-sales case may care about a short interval, while a business renewal can use a longer period and an education campaign may follow an intake calendar. Define those windows before running the analysis. Missing visibility remains unknown; it should not be filled with zero days.
| Relationship | Basis for the window | Constrained action |
|---|---|---|
| Open support case | Case SLA and last customer response | Continue through the channel the customer selected |
| Current order | Dispatch and delivery dates | Send information tied to the order |
| Long-term account | Contract or repurchase cycle | Combine recency with consent and account-owner notes |
| Unknown provenance | No reliable cycle | Do not contact; restore source evidence first |
Online does not mean your message was read
WhatsApp’s official online and last-seen guidance says that online means the app is open and connected to the internet, but it does not mean that a message has been read. Visibility is also affected by privacy choices, contact relationships and blocking.
Use activity output for prioritization inside the measured batch. Evaluate communication performance with the organisation’s own delivery, reply, case-resolution and order events, subject to platform rules. A screening field is not a substitute for an engagement analytics system.
Review portability, recycling and mapped numbers in order
First confirm that the normalized +64 value is valid. Next identify the screening date. Then compare any mapped number with the authorised source record. When a carrier field conflicts with an old prefix table, portability is a plausible explanation rather than immediate proof of an error.
Telephone recycling is another reason to avoid identity assumptions. WhatsApp’s recycled-number guidance notes that providers commonly reissue numbers and explains how prior account information can appear. Merge customer records only after direct confirmation or another reliable business event.
Delivery standard for the data team
- Validate +64 values under the current NAD/ITU plan instead of forcing one length.
- Keep raw number, normalized number and exception reason together.
- Do not write a current carrier solely from the prefix.
- Use TXT for the number input and retain all four WS Activity Excel fields.
- Archive job date, window definition and list version.
- Preserve unknown observations and review mapped values.
- Obtain communication authority from customer records, not from activity output.
Once format, carrier and recency stop impersonating one another, +64 data becomes far more useful. The numbering plan makes the identifier consistent, portability limits overconfident enrichment, and a dated activity job supplies a bounded signal for customer support and list governance.
