Article summary
Use +359 cleanup, a field budget and staged acceptance to decide when Bulgaria lists need WS Full Format rather than a smaller task.
WhatsApp Full Format should not be the default entry point for a Bulgaria phone list. Start with the column the business will actually use, then choose the task. If registration alone answers the decision, collecting age, avatar and skin-tone observations creates missingness, bias and custody duties without making the decision better.
Give every field a budget
| Business question | Smallest task | Usually unnecessary |
|---|---|---|
| Was WhatsApp registration observed? | WS Registration | Profile fields |
| Does a queue require dated segmentation? | WS Activity | Avatar type |
| Must several field families be studied together? | Evaluate WS Full Format | Columns without a purpose |
+359 is a numbering entry, not a customer profile
Preserve phone_raw and list provenance before validating international notation against the current Bulgaria numbering plan. Do not prepend +359 twice. Convert national notation only when country evidence supports it, and send uncertain length or service ranges to an exception queue rather than padding digits.
Accept Full Format as three workbooks in one
WS Full Format may contain phone, activity time, active days, gender, age, avatar, skin-tone observation, avatar type, business-account observation and mapped WhatsApp phone. Accept base/activity, profile and account-relationship groups separately. One total hit rate would conceal which family is missing.
Use a blind sample instead of an accuracy slogan
Sample first-party forms, reseller files and legacy CRM separately, inserting a small set of human-reviewed controls. Reconcile submitted rows, format quarantine, returns, unknowns and mapping conflicts. If one source fails, pause that source rather than turning the issue into a claim about Bulgaria.
Customer profiles do not belong in TXT
AIPUSH accepts TXT with one phone per line. A private crosswalk maps batch_row to contact_id; name, order, language and permission stay inside the company. Returned Excel first enters staging, and a non-unique mapped phone receives human review instead of an automatic customer merge.
Profile columns answer limited questions
Age, gender, avatar and skin-tone fields are limited observations, not user self-declarations. They must not decide identity, minor status, employment, credit, insurance or differential pricing. If crossing small categories could expose a person, widen the group or stop the output.
Put an expiry on every +359 run
Store checked_at, task_version and source_batch. Activity and profile observations can change, so new tasks append events rather than overwriting history. When the purpose ends, delete person-level temporary workbooks while retaining only necessary aggregates and opt-out suppression evidence.
The decision this Bulgaria page should support
Correct formatting is not permission to contact. Verify sender, channel, purpose, frequency and opt-out against the WhatsApp Business Messaging Policy. The smallest sufficient task is more governable than the task with the most columns.
