Start here

Use the official support channel and identify the order or relevant account reference without exposing unnecessary private information. Describe what differs from the expected result and ask for clarification or an available remedy. Keep correspondence and promised timing for a focused follow-up if needed.

A message saying my order is wrong starts a conversation, but support will need to know which order and what differs. Providing the relevant details can make the next response more useful.

Use the company's official support channel. Give the order reference and a clear description of the issue. Include a photograph if it is useful and appropriate, keeping unrelated personal information out of view.

Say what you are asking for

Request clarification, correction or the available remedy without assuming a policy you have not checked. Save the correspondence and any promised date. Never send passwords or full payment credentials to resolve an ordinary order question.

If the response does not address the issue, point to the missing part and use the provider's escalation process where appropriate. Keep the facts consistent across messages. A concise account with the relevant reference helps an agent investigate, while a record of the exchange gives you something dependable to use if further follow-up is needed.

Explaining a wrong item in an order

An illustrative example

Suppose an item you receive differs from the order confirmation. In the official support form, you give the order reference and describe the difference using the item names shown in the record. You attach a relevant photograph after checking that no address label or unrelated private information is visible. Your request asks which correction or remedy is available under the provider's process. You do not assume a refund policy or send payment credentials to prove the order. When the response asks about delivery timing, you provide the relevant date from the record. You save the reply and any promised update point. If the response still misses the item mismatch, your follow-up names that unresolved part directly.

Give support what it needs to investigate

Tick the steps as you work through them.

0 of 5 steps checked

When the response does not address the issue

Refer to the case number and identify the unanswered point. Keep the factual account consistent across messages and ask which step comes next under the provider's process. Use an appropriate escalation route when needed. Avoid sending passwords or full payment details in ordinary correspondence. If a request for information seems unusual, verify it through the official channel before responding. A concise record of the issue, replies and promised timing helps you follow up without reconstructing the entire order history each time.

A support message outline

Your notes stay in this page. Copy them before leaving; they are not saved or sent to us.

Next useful stepHow to write a useful follow-up with context →

Written by the Painless Success editorial team. Our upcoming book, Painless Success, brings these ideas together. Preview its contents or join the release waitlist.