Article summary
Preserve country evidence for +383 and other international phones inside a Serbia +381 business list before WhatsApp Registration.
A +383 phone in a Serbia business list must not be changed automatically to +381. List ownership, numbering plan and customer market are separate fields. Preserve the evidence for each before WhatsApp Registration.
Route four queues by prefix and provenance
| Queue | Handling |
|---|---|
| Supported +381 | Serbia-rule checking |
| Supported +383 | Keep code and check separately |
| Other international code | Corresponding rule |
| Unknown national notation | country_unknown |
A project name is not country evidence
“Serbia customer sheet” describes a business folder, not every phone. Order, address, user country choice and original international code provide stronger evidence.
Protect the original phone irreversibly
Never overwrite phone_raw. Write every country-code change to candidate and transform_log. A higher return rate cannot decide which country code is correct.
Registration does not determine affiliation
TXT contains one phone per line and Excel returns registration observation. A return does not validate country, residence, citizenship or identity.
Keep cross-queue duplicates as conflicts
Matching final digits under different country codes cannot be merged casually. Connect only a supported one-to-one relationship.
Do not mix denominators
Report submitted, exception, observed and unknown separately for +381, +383, other international and unknown queues.
Permission does not migrate with a code
Changing a candidate format cannot clear opt-out or change purpose. Apply related controls only after human confirmation.
Retain rule version
Store country_rule_version and checked_at so later rule changes explain old batches rather than rewrite history.
The Serbia search answer
Separate +381 and +383 evidence before Registration; a technical task cannot decide country or identity for you.
