Article summary
Use source-country evidence and rule versions to admit phones to a Russia WhatsApp Activity queue when +7 alone is insufficient.
In a +7 numbering context, the prefix alone is insufficient to assign every row to a Russia list. Country admission needs both provenance and current numbering rules. WhatsApp Activity cannot validate country backward.
Score evidence for country admission
| Evidence | Weight | Handling |
|---|---|---|
| Original international phone fits current rule | High | Candidate |
| User country choice or order | High | Cross-confirm |
| Filename or campaign name | Low | Insufficient alone |
| No provenance | None | country_unknown |
Date and version the rule
Store country_rule_version and authority date. New batches use a new version after numbering changes; old output retains its historical explanation.
Do not rewrite source phones in bulk
Keep phone_raw immutable and store candidates plus transformation logs separately. Country conflicts enter human review; Activity return cannot decide format.
Begin Activity with a business action
Only an authorised, time-sensitive service or operating queue needs activity observation. Country-market research does not need person-level time data.
Output does not prove location
Activity time, active days, avatar and business-account observation cannot show that a person is currently in Russia or generate language and citizenship labels.
Separate TXT from country evidence
Upload one phone per line while source_country and permission stay in the crosswalk. Reapply admission on return without auto-changing country.
Report each provenance separately
Show format exception, return and unknown for forms, orders, partners and legacy CRM to locate the defect.
Permission precedes recent state
Opted-out or out-of-purpose records do not enter the queue. A mapped phone cannot bypass suppression.
The Russia boundary answer
+7 is one entry signal. Country admission, Activity observation and contact permission remain independent.
