Make a private source record first
Keep the original message or screenshot in a location you control. Record its date and the service that produced it. Do not edit your only copy: a cropped image is a presentation aid, not a replacement for the source. Separate your own notes from the service’s exact wording so a later reader can tell which statement came from where.
Create a public summary
Describe the event and the question using ordinary words. Include the relevant date, the general stage of the order and the unit or currency when it matters. Leave out your name, home address, telephone number, email, payment references, account recovery information, QR codes and complete order or tracking identifiers. A barcode can encode the same information as visible text, so hiding only the printed number may not be enough.
Use a narrow question
“The status changed from A to B on 28 October; what additional event would confirm dispatch?” is easier to answer than “Where is my parcel?” It also avoids pretending that a brief label proves a physical location. If the question concerns a charge, separate the quoted component from the total and state which inclusion is unclear. Do not post payment-card or bank details.
Prepare the private version separately
For an authenticated support channel, use the identifiers that the service actually requests and that are relevant to the question. Check the destination yourself: a reply in a public forum is not automatically an official support contact. Never share a password, one-time login code or account recovery code to obtain order help.
Review the attachment, not just the caption
- Check the whole screenshot, including browser tabs, notification previews, filenames and background windows.
- Use an opaque redaction rather than a translucent highlight. Export a fresh image and inspect that exported copy.
- Check both text and machine-readable codes. When in doubt, describe the event in text and omit the attachment.
- Keep the public summary aligned with the evidence. Missing information should remain a question, not become an invented answer.
Example
Public: “My order shows a new processing event dated 28 October. The wording does not name a carrier. Which later event should I look for before treating it as dispatched?” Private: the same question plus the specific order reference, supplied only through the service’s authenticated support route if requested. These are illustrative examples, not reports of a real shipment.
Related references
The maintainer’s order and parcel tracking guide explains how to keep event records in context. For distinguishing cost components when drafting a fee question, use the cost calculation guide. Neither reference replaces the provider’s actual order record.