Article summary
Merge three place-specific WhatsApp Full Format queues with a common schema, territory keys and count reconciliation.
St Helena, Ascension and Tristan da Cunha can be delivered in one Full Format workbook, but the three queues should not be mixed first and reconstructed later. Process by place, accept each queue, and merge only through a common schema.
Make merge keys explicit
| Field | Purpose |
|---|---|
| batch_row | Return to the input row |
| territory_key | Preserve the three queues |
| schema_version | Confirm field compatibility |
| observed_at | Bound the result in time |
| source_id | Connect private evidence |
Perform three count reconciliations first
For each queue, reconcile submitted, returned, format_exception and task_unknown before checking the merged total. A total alone can let extra rows in one place cancel missing rows in another.
Do not fill an unavailable field with false
When a place or batch did not observe a field, use not_available or unknown. A tidy schema does not justify changing absence into a negative result.
Separate avatar queues from Full Format merging
A companion article explains place-specific avatar review. This page focuses on field compatibility, row integrity and handover rather than repeating profile interpretation.
Represent a shared contact point once
When one organisational phone appears across places, use relationship_scope to describe coverage. Do not create three duplicate personal identities in the customer master.
Keep the batch mapping beside TXT
The upload still contains one phone per line. territory_key and business ID remain in the crosswalk, and batch_row reconnects them after Excel returns.
Check enum versions before merging
If columns with the same name use different state sets, map them explicitly and preserve the raw state. String replacement must not conceal a semantic difference.
Create role-specific views after delivery
Operations sees necessary format and contact states; relationship reviewers handle mappings; temporary profile observations receive tighter access and retention.
The acceptance test for one workbook
Users can aggregate all three places and still return to any queue and original input. Consolidation creates convenience without sacrificing provenance, state or time.
