Identify the fact the customer needs
A shipping policy explains the normal process; an order record describes one transaction. Confirm the appropriate reference through your authorized workflow, then check the latest available event and its timestamp. Do not infer dispatch from payment or delivery from a generated label. When the system has no live order connection, say that a teammate needs to check the order.
State the evidence and the next step
A helpful reply identifies what is known, what remains unverified and who will act. Distinguish an estimated range from a confirmed carrier event. For a US store serving Saudi customers, label the timezone of tracking events and avoid treating customs or carrier delays as known causes without evidence. Keep the customer's data in the authorized case record rather than exposing it in public examples.
Fictional worked example
Fictional record: a label was created at 10 AM, but there is no carrier acceptance scan. A careful reply says the label exists and dispatch still needs confirmation. 'Your parcel is on the way' would add a fact the record does not establish. The next action is a check with the responsible fulfillment team, not a fabricated arrival date.
Action checklist
- Verify the order reference through the approved workflow.
- Record the latest event, timestamp and source.
- Separate policy estimates from transaction facts.
- If data is unavailable, assign a status check and state the next update.