Article summary
Manage WA/WS number checking with four artifacts: job ticket, TXT list, untouched Excel result and controlled CRM update record.
WhatsApp number checking should not begin with “upload a file.” It should begin with a job ticket. A reviewable operation retains four artifacts: the ticket, TXT list, untouched Excel result and CRM update record. If one is missing, the team cannot fully explain where a field came from.
Artifact 1: the job ticket
The ticket identifies list source, business purpose, WA/WS task, expected fields, batch ID, owner and retention period. If the task is unclear, stop; the operator should not choose full format as a default.
Artifact 2: the TXT list
Select phone numbers from the authorized population while keeping internal IDs and permission state locally. Normalize country codes and send ambiguous values to repair. The TXT contains one number per line—no names, emails, notes or header.
Map the question to the output
| Question | Suitable task | Key output |
|---|---|---|
| Registered? | WS registration | Phone and registration result |
| Activity grouping? | WS activity | Activity time, active days and mapped number |
| Avatar or business field? | WS avatar | Business account, avatar and mapped number |
| Age and gender? | WS gender and age | Age, gender, avatar and mapped number |
| Justified multi-field project? | WS full format | Ten activity and profile-related fields |
Artifact 3: untouched Excel result
Save a read-only original immediately and work from a copy. Confirm the batch and headers, and import phone columns as text. Preserve submitted and WhatsApp-mapped numbers separately rather than overwriting one with the other.
Artifact 4: CRM update record
Load results into staging and join with the canonical phone key. Store batch, task, checking date, returned values and exception state. Append observations instead of replacing history, so old and new results remain explainable.
Three stop conditions
- If task and headers differ, stop import.
- If join performance is abnormal, stop the CRM write.
- If permission or opt-out state is unclear, stop activation.
Close the job deliberately
- Reconcile source rows, TXT unique count and Excel results.
- Resolve duplicates, missing rows and mapping conflicts.
- Obtain reviewer approval for CRM changes.
- Confirm a rerun cannot duplicate updates.
- Assign deletion dates to transient files.
- Store a short batch outcome record.
What the workflow does not decide
Registration is not consent, activity is not buying intent, avatar is not identity verification and a business-account result is not corporate due diligence. Keep these decisions in their proper systems.
AIPUSH performs the TXT-to-Excel task. The company’s operations layer controls source, reconciliation, permission and CRM application. The four artifacts make the process repeatable without turning it into a black box.
