Article summary
Russia and Kazakhstan share +7, so a +7 phone cannot be assigned to Russia on sight. Route it with current ranges and provenance before a WS/WA registration check and permission review.
A Russia WhatsApp registration check has a routing question that must be answered before the task runs: does a +7 phone belong to the Russian or Kazakhstan numbering plan? +7 is shared, so “correct length after removing the plus sign” is not country attribution. Wrong routing contaminates Russian registration rates, market reporting and any later outreach list.
What shared +7 changes
The ITU’s Russian numbering-plan entry provides the +7 country-code and current plan materials. Operations should maintain valid Russian and Kazakhstan ranges with their rule dates. country_code yields a “+7 zone”; a current national destination range participates in country routing.
Build a two-stage parser
| Stage | Question | Output |
|---|---|---|
| Syntax parse | Is this a parseable +7 international phone? | parsed / exception |
| Range routing | Does the current range indicate Russia, Kazakhstan or uncertainty? | RU / KZ / review |
| Provenance comparison | Does CRM country agree with range? | agree / conflict |
| Task admission | Can it enter the Russian cohort? | admit / quarantine |
National 8 and international +7 are not a blind substitution
Phones from a Russian domestic system may begin with a national dialling prefix, but a file can also contain extensions, short codes, text and non-Russian records. Convert only when provenance is clear and a current rule matches. Retain phone_raw, phone_e164_candidate and transformation_reason; never guess an exception.
Quarantine cross-border CRM conflicts
If a form says Russia while current range routing indicates Kazakhstan, do not silently change country and do not ignore the range. Mark country_range_conflict and review the customer’s choice, order market or source system. Numbering-plan assignment is still separate from a person’s current residence.
The boundary of a WS Registration result
AIPUSH WS/WA Registration exports phone and registration status. It does not include activity time, avatar, Gender and Age or conversations, and it cannot confirm that the SIM remains used, who holds the phone or whether an account is safe. A wider field need requires the corresponding task and its own stated purpose.
A registration rate needs the right denominator
| Count | In Russian-rate denominator? | Reason |
|---|---|---|
| Confirmed RU and successfully checked | Yes | Target population |
| Routed KZ | No | Separate market cohort |
| Uncertain shared-zone phone | No | Needs a rule or human evidence |
| Format exception/duplicate | No | Data-quality issue |
| Task unknown | Report, but do not force registered/not registered | Preserve uncertainty |
TXT carries admitted phones only
Write one admitted Russian-cohort phone per line in TXT. Name, order, country evidence, permission and contact_id remain in an internal crosswalk. The AIPUSH Excel export lands in staging and rejoins through a batch key. Do not upload KZ and review records together for convenience and guess after the fact.
“Registered” cannot replace consent
A registered observation describes platform state at check time. Sending still depends on provenance, purpose, regional requirements, user permission, opt-out and suppression history. Registration status never bypasses a refusal record and cannot prove that the recipient wants Russian-language content.
Plan changes trigger targeted review
Store effective_date, source_url and version for the range table. When it changes, compare range differences, identify affected phones and reroute those records. Unaffected history need not be reprocessed. Previous routing remains for audit but stops contributing to current market statistics after expiry.
The deliverable is more than one percentage
The package reports RU/KZ/review routing counts, conflicts, duplicates, exceptions, registered, not registered, unknown, checked time, rule version and deletion plan. Transparent treatment of a shared country code keeps the Russian WS Number Checker result from resting on false country attribution.
