System states, customer accounts and operational records may describe different stages. Turn the conflict into verifiable questions and separate evidence gathering from customer communication.

The customer says the parcel never arrived; the system says delivered. Support trusts the system, the warehouse says it handed the parcel over, and the customer feels passed between teams. The immediate task is to establish what each record supports and which step remains uncertain. Delivery is one example of a wider evidence problem.

Translate a status into the action it records

Delivered is a recorded state; receipt by the customer is an outcome to verify. Establish who generated the state, when and from which information. Separate dispatch, carrier handover, receipt records and customer feedback. Mark missing steps as unresolved rather than infer them from neighbouring events.

The distinction also helps with refunds, bookings and service completion. Initiation does not necessarily establish receipt, and closing a ticket does not establish that a promise was executed. Apply these questions to the specific facts, not as an assumption that either party must be wrong.

Use the conflict to assign evidence tasks

Connect the customer's account, the business record, the discrepancy and the question to resolve. If a receipt record names a location the customer disputes, investigate the location and delivery evidence rather than repeatedly demand proof of non-receipt. Use appropriate private channels and collect information relevant to the issue.

The warehouse supplies dispatch facts, the carrier supplies its delivery records, and support confirms the customer's account and contact arrangements. Record sources and dates. Leave responsibility unresolved where the facts do not yet support a conclusion.

Compare delivery records with the customer account

Warehouse and truck records and a customer at a doorway without a parcel connect separately to a central reviewer.

Warehouse and transport on the leftRecords held by each party

Customer doorway on the rightAccount of actual receipt

Comparison point in the centreAssign each conflict for evidence

Transport records and the customer’s receipt account meet for comparison; the difference remains visible without deciding liability. AI-generated editorial illustration.

Investigate and communicate in parallel

Assign one customer contact to explain confirmed facts, remaining checks and the next update arrangement. Avoid sending the customer separately to the warehouse, carrier and support, or promising results and deadlines outside the team's control.

Communicate replacement, refund or other remedies only after an authorised decision. An incomplete investigation does not require silence, and a timely update does not require an early liability conclusion. Public replies should not expose addresses, phone numbers or private conversations.

Separate factual findings from completed remedies

Record resolved conflicts, remaining uncertainty and the business's chosen action. Completion needs evidence of execution; notifying another party is not completion. If the sequence cannot be fully reconstructed, retain that limitation.

Recurring disputes at the same stage justify examining record or handoff gaps. Similar system states do not establish a common cause, but they can guide a further sample review.

Use the case to identify the management gap

The investigation should reveal whether the missing element is operational evidence, traceability, ownership or clear customer updates. Assign that gap to someone who can improve it rather than produce a longer defensive response.

A useful output is a reconstructable timeline and the questions still open. The next owner should not have to interview everyone again, or mistake an earlier assumption for a verified fact.

Sources checked on 21 October 2026:Review replies

Turn useful ideas into your business’s next step.