Article summary
Interpret WhatsApp registration results for Montenegro +382 phones, including legacy-code exceptions and the difference between negative, unknown and error states.
A Montenegro WhatsApp “registration check” means only that this run returned a registration state for a normalized phone. It does not establish who controls the number, whether the person is in Montenegro, whether messages are wanted or whether the account is recently active. That boundary matters more than a larger positive rate.
+382 is the starting point for phone handling
Montenegro uses country code +382. Historical databases may contain legacy country notation, missing codes or records confused with neighbors. Retain phone_raw, record age and country_evidence. A bulk replacement must not turn historical ambiguity into false certainty.
| Input | Action | Risk |
|---|---|---|
| Reliable +382 | Validate under the current structure | Length-only checking |
| Legacy / neighboring code | Return to source and date | Changing to +382 without evidence |
| Domestic notation | Handle the national prefix by rule | Duplicated zero |
What WS Registration returns
The core fields are phone and registration result. AIPUSH takes a one-phone-per-line TXT and exports Excel after completion. This task does not provide activity time, avatar, gender, age or contact permission.
Keep four outcomes separate
| Outcome | Interpretation | Next action |
|---|---|---|
| Explicit registered | Positive state in this run | Still check permission |
| Explicit unregistered | Negative state in this run | Retain date |
| Unknown / blank | No definitive answer | Do not write “no” |
| Error | Format or task exception | Correct cause, rerun subset |
Why registration state can differ later
Account registration, deletion, phone reassignment, input-rule changes and observation time can all create differences. Store checked_at, batch_id and TXT hash for each run. Today’s state does not erase historical evidence.
Reconcile Excel before calculating a rate
Join through the internal contact_id crosswalk. Unmatched rows, one-to-many relationships and repeated states enter an exception queue. Calculate registration rate only after proving the denominator; format failures must not become unregistered.
Registration does not verify identity
A phone may belong to a shared device, a company role or a reassigned subscription. Registration checking cannot replace identity verification, contract confirmation or proof of account ownership.
Registration does not mean recent activity
When the decision needs activity time, choose WS Activity and accept its field and validity boundaries. Never append an “active user” label to Registration output.
Registration certainly does not create marketing permission
Provenance, WhatsApp channel scope, purpose and opt-out determine contact eligibility. An opted-out phone remains suppressed when registered, and an unexplained list does not become compliant after a positive result.
A qualified +382 report
Disclose the phone rule, legacy-code exceptions, input and return counts, explicit states, unknowns, errors and observation date. Registration checking is valuable because it provides a traceable answer to a limited question—not because it expands that answer into human intent.
