What should a generated pack include when customer channels disagree?

Ask for these components when scoping a generated pack in which customer instructions arrive through competing channels.

- Original messages with channel identifiers. - Separate receipt and customer-stated timestamps. - The field each instruction seeks to change. - Explicit withdrawal or replacement references. - A supplied source-precedence policy. - An unresolved-conflict state and routing destination. - Accepted reasons for choosing or deferring an instruction.

A utility customer submits a portal request to redirect bills, then sends an email asking to keep correspondence unchanged. If the email arrives through a delayed queue, arrival order alone may not establish the customer's latest intent. The pack should preserve that distinction rather than quietly sorting messages into a definitive sequence.

For a reseller, the deliverable is not simply a collection of duplicate requests. It is a controlled conflict between sources, with enough evidence for a downstream system to explain its resolution or recognise that resolution is unsupported.

Document which ordering facts are known and which remain uncertain. This lets buyers select tasks that test precedence rules, interpretation of withdrawal language or escalation under conflicting evidence without conflating those capabilities.