Article summary
Prepare Kosovo +383 phones without guessing local formats, then accept WS registration observations with clear denominators, permission and retention controls.
A Kosovo WhatsApp Registration Check should answer one narrow question: was a correctly prepared +383 phone observed as registered at check time? It does not verify the holder, establish residence, confirm that a SIM is active or grant permission to send marketing messages.
Establish Kosovo country evidence first
Use +383 only when the source record supports Kosovo through an explicit country selection, contract, address or documented dataset. A local-looking number copied from a mixed Balkan CRM is not enough evidence to prepend a country code.
Preserve raw and normalized values
| Column | Purpose | Rule |
|---|---|---|
| phone_raw | Audit and recovery | Never overwrite |
| phone_e164_candidate | Task-ready value | Generate from current +383 ranges |
| format_state | Admission control | pass, exception or review |
| rule_version | Reproducibility | Store source and date |
Do not “repair” ambiguous local phones
Quarantine wrong length, extension, duplicated country code, non-phone text and conflicting market evidence. Never pad a short value or delete digits to increase the pass rate. An exception is a valid quality result, not a production failure.
Create the TXT execution file
AIPUSH accepts a TXT file containing one phone per line. Remove the header and blank lines, but keep name, region, order and permission outside the upload in an internal crosswalk keyed by batch_row.
Interpret the Excel result narrowly
WS Registration returns phone and registration status. Unknown and missing results remain distinct from “not registered.” Deduplicate before calculating a registration rate, and use only successfully checked, Kosovo-routed unique phones in the denominator.
A registered account is not a verified person
Phones can be reassigned, shared by a household or used as a business contact point. Registration does not prove the CRM name, age, company or current location. Mapping conflicts require review rather than automatic merging.
Consent is a separate gate
Check collection notice, purpose, channel, opt-out and suppression before contact. A technically registered phone with unknown permission stays quarantined. Registration status never bypasses a refusal.
Retain a reproducible batch record
Record raw rows, unique phones, formatting exceptions, duplicates, registered/not registered/unknown, checked_at, rule version, permitted purpose and deletion date. That evidence makes future review possible without repeatedly checking the entire list.
