Article summary
Use the new Kazakhstan-Russia shared +7 arrangements to avoid country attribution by +7 alone and build an updateable Full-Format number workflow.
Labeling every +7 phone as Russian is one of the most common and most fundamental attribution errors in a Kazakhstan WhatsApp dataset. Kazakhstan continues to share World Numbering Zone 7 with Russia, and arrangements formally published in 2026 clarify the resources used by each country. A cleanup service must interpret the range beyond the country code rather than stop at +7.
The shared +7 zone is not a temporary anomaly
An official Kazakhstan government statement published in 2026 says the arrangement appeared in ITU Operational Bulletin No. 1341 and assigns +7 0, +7 6 and +7 7 resources to Kazakhstan. Russia uses the other agreed resources. For a database, country_code=7 can therefore never complete country attribution on its own.
Attribution must read the resource after +7
The parser preserves phone_raw, separates +7 from the remaining digits and evaluates the value against a dated range table to produce plan_country_candidate. Do not write every +7 record as RU during import. Once that false country enters CRM, it contaminates language, time-zone, compliance-routing and reporting fields downstream.
Use a reversible repair tree for legacy data
| Record condition | Decision | Important limit |
|---|---|---|
| Explicit +7 within a current Kazakhstan resource | country_plan=KZ candidate | Does not prove current location |
| Explicit +7 within an agreed Russian resource | country_plan=RU candidate | Keep source market separately |
| Range not covered or length malformed | unresolved | Do not force attribution from list name |
| Existing CRM country conflicts with plan | review | Retain old and new values plus rule version |
The 2026 update should trigger a differential replay
Store range_version and attributed_at for every country-plan result. When the allocation changes, recompute only affected +7 prefix cohorts and output before_country, after_country and change_reason. Never overwrite the old value without history; otherwise changes in historical reports become impossible to explain.
Numbering-plan country and business market can coexist
A Kazakhstan phone holder may be in Russia, Germany or elsewhere, while a Russian phone can appear in an Almaty business list. Keep phone_plan_country, source_market, declared_location and preferred_language as distinct attributes. The last three require their own evidence and cannot be derived from the +7 allocation.
Full Format does not repair country attribution
AIPUSH WS Full Format may include phone, activity time, active days, gender, age, avatar, skin tone, avatar type, business status and mapped WhatsApp phone. It does not replace numbering-plan interpretation. First route KZ, RU and unresolved records, then create TXT batches from mobile candidates allowed by the business purpose.
Divide the wide workbook into access zones
- Number foundation: raw value, normalized candidate, plan country and rule version.
- Perishable observations: activity time, active days, checked date and expiry date.
- Restricted profile data: avatar, age, gender, skin tone, avatar type and business observation with purpose-based access.
Not every team member needs every column. Zoning also reduces the chance that an analyst combines plan country and profile fields into an unsupported “Kazakhstan user” persona.
Re-evaluate country when the mapped phone changes
If a mapped WhatsApp phone differs from the input, parse its +7 resource again and display input_plan_country beside mapped_plan_country. A cross-range change may reflect formatting, number change or a record relationship requiring investigation. Do not merge customers automatically or transfer permission from the original phone.
Submit only normalized candidates in TXT
The TXT contains one phone per line and no name, country label, language or order. An internal manifest retains input_id, raw_hash, plan_candidate and batch_id. The returned Excel first enters staging, and only records passing mapping and state rules move downstream.
Accept the rules with a country-attribution matrix
Sample KZ, RU and malformed phones whose status is supported by reliable evidence. Measure false attribution, unresolved routing and out-of-rule values separately. Pay special attention to +7 6 and +7 7 records that a legacy system may have labeled RU by default. The goal is fewer explainable attribution errors, not the artificial elimination of unresolved records.
Kazakhstan demonstrates that an international country code does not always map to one country. A defensible Full-Format project retains the shared zone, allocated resource, version date and business provenance together so one early country label does not distort every later analysis.
