Confirm purpose, authority and environment
Decide whether the job checks WhatsApp registration, recent activity or only format and duplicates, because inputs and outputs differ. Confirm lawful data use and applicable privacy and communications rules. Verify connectivity, account authorization and the required one-number-per-line or country-code format.
Prepare and import numbers
Normalize country codes, remove spaces and invalid characters, reject impossible lengths and split very large files into manageable batches. Map phone and optional metadata columns carefully, then preview several rows before submission to prevent a non-phone field from becoming the identifier.
Configure and run the job
Select only the screening options actually provided and needed, set a conservative supported rate, and enable resumable processing or bounded retries when available. Watch progress, success and failure counts. A sudden failure spike can indicate connectivity, systemic formatting errors or provider controls; pause, diagnose and retry at an appropriate rate without changing parameters mid-run.
Interpret and export results
Distinguish registered, unregistered, indeterminate and failed states; indeterminate must not be discarded as unregistered. Preserve original number, state, timestamp and batch ID in CSV or spreadsheet exports. Before permitted outreach, apply internal suppression and opt-out lists and retain an operator and parameter record where audit evidence is required.
Prevent common mistakes
Use a small pilot, consistent batch naming and result summaries. Do not lose valid leads through country-code errors, rerun an entire oversized batch unnecessarily, or store personal-number exports in public or unencrypted locations. Apply role-based access and delete caches and expired exports under the retention policy.
