Article summary
Use ten provenance, formatting, permission, deduplication and reconnection checks before admitting a Paraguay +595 partner list to WhatsApp Registration.
A file named “Paraguay customers” should not receive +595 and go straight to upload. Partner delivery needs ten provenance, phone, permission and reconnection checks. A critical failure decides usability before the registration rate does.
The ten-check acceptance table
| Category | Checks |
|---|---|
| Provenance | Owner, collection time, acquisition method |
| Purpose | Allowed use, channel, expiry |
| Phone | Raw value, country evidence, duplicate, exception |
| Control | Opt-out, reconnection key, deletion owner |
Create an exception for every missing item
Do not fill blanks from verbal assurance. Quarantine missing country evidence, purpose and suppression separately.
+595 is not a file-level default
Preserve phone_raw and create a candidate only from row-level evidence. Foreign phones retain their international notation.
Sample before the whole batch
Review formatting, duplicates and reconnection across every provenance and period. Clustered defects return to the partner for source correction.
What Registration answers
TXT contains one phone per line and Excel returns registration observation. It does not validate partner claims, the holder or permission.
Language does not come from a Paraguay label
Communication preference comes from user choice or an actual record, not country, name or avatar.
Return rate is not total supplier quality
Score provenance completeness, exceptions, unknowns, conflicts and deletion execution. High registration cannot offset missing permission or traceability.
Return without overwriting master data
Use batch_row and contact_id to enter staging. Humans review conflicts, and registration appends as an event.
The final partner rule
First prove why the list may be processed, then observe registration. Reversing the order mistakes a technical result for business authority.
