Article summary
Normalize Bulgarian +359 phones, treat WS activity fields as expiring observations, and govern refresh, deletion and permission in an EU customer pool.
A Bulgaria WhatsApp activity check should not permanently divide customers into “active” and “dormant.” It should assign a date and expiry rule to one observation. Cross-border EU customers can change country, phone or workplace. +359 structure, activity time and permission therefore remain independent records.
Keep the domestic source beside +359
Retain phone_raw, country_evidence and normalization_version, then handle the national prefix under the current Bulgarian numbering rule to create +359 international notation. A Cyrillic name or Bulgarian address does not prove that the phone belongs to +359.
| Layer | Fields | Validity |
|---|---|---|
| Source evidence | phone_raw, source | Business retention policy |
| Normalized phone | +359 form, rule version | Review after rule changes |
| Activity observation | Time, days, checked_at | Business window |
| Permission | Channel, purpose, opt-out | Can end at any time |
WS Activity returns a limited schema
The export includes phone, activity time, active days and WhatsApp mapped phone. It does not establish current country, working hours, identity, messaging permission or purchase intent.
Define the expiry action before the run
Set refresh_after for each use case. At expiry, mark the observation stale and stop using it for prioritization; do not recheck the entire database automatically. Only a minimal subset with a continuing lawful purpose and relationship enters a rerun.
Three states are not all “inactive”
| State | Meaning | Handling |
|---|---|---|
| Older activity observation | Last activity lies outside the window | Display its date |
| Blank field | No definitive result | Preserve unknown |
| Expired data | Beyond business validity | Stop using it |
Minimal TXT and internal mapping
AIPUSH accepts TXT with one phone per line. Name, company, order, language and permission remain internal and reconnect Excel through contact_id. Store the TXT hash and row count for reconciliation.
Do not schedule by country code for cross-border workers
A +359 phone may roam elsewhere in the EU, and a foreign phone may belong to a Bulgarian customer. Obtain message time zone from user settings or service address rather than phone and activity timestamps.
Mapping collisions pause automatic merging
Write mapped phones into a relationship table. One-to-many, many-to-one or implausible country structure creates a case with batch and reviewer. Never overwrite customer source data.
Opt-out outranks activity
Recent activity cannot restore contact eligibility after an opt-out. Marketing requires provenance, WhatsApp scope, purpose and suppression checks. Activity may only prioritize an already-approved service process.
Accept on data lifecycle
Report +359 format pass, number type, activity coverage, stale share, mapping collisions and planned deletion date. Knowing when a field must stop being used is as important as knowing its current value.
