Article summary
Turn mixed export-sales phones into a governed WhatsApp workflow without confusing registration or activity with permission, company fit, purchasing authority or intent.
For an export-sales team, WhatsApp Number Checking is a list-quality control—not a shortcut from a trade-show spreadsheet to mass messaging. Registration, activity and profile observations can reduce operational uncertainty, but they cannot establish consent, purchasing authority or product demand.
Begin with provenance, not platform status
Separate website inquiries, existing customers, distributor referrals, purchased lists and badge scans. Record event, date, collector, stated purpose and country evidence. A phone without a defensible source remains quarantined even if it is technically valid.
Normalize international phones without inventing digits
Preserve phone_raw and generate phone_e164_candidate under a versioned country rule. Ambiguous local notation, extensions and country conflicts enter exceptions. Do not add the event’s country code to every local-looking value; exhibitors and visitors may use numbers from elsewhere.
Choose the narrowest WS task
| Business question | AIPUSH task | Returned scope |
|---|---|---|
| Is an account observed? | WS Registration | Phone, registration status |
| Is there a recent activity observation? | WS Activity | Phone, activity time/days, mapped phone |
| Is a profile picture observable? | WS Profile Picture | Phone, business status, avatar, mapped phone |
| Need the defined wider schema | WS Full Format | Activity, profile, avatar and business fields |
Registration does not equal permission
“Registered” is a platform-state observation at check time. Permission requires an appropriate collection notice, channel and purpose, with a usable opt-out. A badge scan or business card may permit a requested follow-up in context; it does not automatically authorize indefinite promotional broadcasts.
Activity does not equal buying intent
A person can use WhatsApp frequently while having no interest in the product. Rank commercial opportunities using first-party evidence such as a quoted project, requested specification, replied question or active order. Use activity only as a limited operational timing input inside a permitted cohort.
Keep TXT minimal and the CRM authoritative
The upload contains one phone per line as TXT. A private crosswalk holds lead ID, company, market, source and permission. Excel returns to staging; mapping collisions and shared company phones receive review rather than automatic contact merging.
Design a humane follow-up sequence
Identify the company and event, explain why the message is relevant, make the first message useful, and provide an easy stop path. Cap frequency across sales representatives so the same contact is not approached from several regional teams.
Measure stages independently
Report formatting yield, registration observations, valid permission, replies, qualified opportunities and opt-outs as separate denominators. That reveals whether the problem is bad collection, stale data, weak relevance or an overly aggressive cadence instead of blaming the Number Checker.
