01
Identify the order and issue
Start with the relevant order reference and the latest recorded status you can access. Describe the specific issue, such as an incomplete address, an unexpected status or a customer cancellation request. Avoid saying only “the platform is broken” when you can identify the affected step.
Do not attach a list of unrelated customer records. The team needs the context for this issue, not every contact in your campaign. Use an authorized support channel rather than public comments.
02
Separate observations from assumptions
State what you observed, when it happened and what clarification you need. For example: “The customer requested an address correction after submission; can the responsible team review it?” Do not claim a shipment is lost merely because an update has not yet appeared.
If including an image, crop to the relevant issue and hide unnecessary personal details. Never send passwords, access codes or banking security information with a support request.
03
Describe the requested outcome
Ask for a concrete review: confirm the next step, inspect an address correction or explain a recorded financial result. Keep operational decisions with the authorized team. An affiliate message does not independently approve a refund, alter stock or mark an order delivered.
For a wallet question, reference the relevant order or payout record and distinguish estimated earnings from the displayed balance. Do not recompute an old order using today’s product price.
04
Follow one thread to resolution
Add new relevant facts to the existing discussion instead of opening several identical requests. Check the recorded outcome after the team responds; a reply in chat is not always the same as a completed operational change.
Keep a private note of the resolution and use repeated issues to improve future data entry or offer explanations. Do not publish a support screenshot as a testimonial or expose another customer’s details.