How to Give a Useful Problem Summary in Product Return Message English
When you need to return a product, the most important part of your message is the problem summary. A useful problem summary clearly explains what is wrong with the item, how it affects its use, and what you expect from the seller. It helps the customer service team understand your issue quickly and process your return without back-and-forth emails. This guide shows you exactly how to write a clear, effective problem summary in English for product return messages, whether you are writing a formal email or a quick chat message.
Quick Answer: What Makes a Problem Summary Useful?
A useful problem summary includes three key parts: (1) what the problem is, (2) when or how you noticed it, and (3) the result or inconvenience. Keep it factual, avoid emotional language, and mention the specific defect or issue. For example: “The laptop charger stopped working after three days of normal use. The charging light does not turn on, and the battery drains completely within one hour.” This gives the seller clear information to act on.
Understanding the Context: Formal vs. Informal Problem Summaries
Your choice of words depends on where you are writing the message. In a formal email to a company’s support team, you should use polite, complete sentences. In a live chat or a message on a marketplace app, you can be more direct but still respectful. Below is a comparison table to help you choose the right tone.
| Context | Tone | Example Sentence |
|---|---|---|
| Formal email | Polite, detailed, complete sentences | “I am writing to report that the blender I received on March 10 does not operate on the highest speed setting.” |
| Live chat / app message | Direct, shorter, still polite | “The blender I got yesterday won’t work on high speed. Can you help?” |
| Phone call | Conversational, clear, brief | “Hi, I just received a blender, and the high-speed button doesn’t do anything.” |
Key Elements of a Useful Problem Summary
To write a summary that gets results, include these four elements in your message:
- Identify the product: Mention the product name, model number, or order number.
- State the defect clearly: Describe what is wrong without guessing the cause.
- Explain when it happened: Was it upon arrival, after first use, or after a few days?
- Describe the impact: How does the problem affect the product’s function or your use?
Natural Examples
Here are three natural examples that show different levels of formality. Each one follows the key elements above.
Example 1 (Formal email):
“Dear Customer Service, I am writing about order #4521 for a pair of wireless earbuds. The left earbud produces no sound at all, even after charging and resetting the device. I noticed this issue immediately after unboxing. The earbuds are otherwise in perfect condition, but I cannot use them as a stereo pair. Please advise on the return process.”
Example 2 (Informal chat):
“Hi, I got the wireless earbuds from order 4521. The left one doesn’t make any sound. I tried charging and resetting, but nothing works. Can I return them?”
Example 3 (Phone call script):
“Hello, I’m calling about a pair of earbuds I ordered. The left earbud is completely silent. I just opened the package today. What should I do?”
Common Mistakes in Problem Summaries
Many English learners make the same errors when writing problem summaries. Avoid these to keep your message clear and professional.
- Being too vague: “It doesn’t work.” This does not tell the seller what is wrong. Be specific: “The power button does not respond.”
- Adding unnecessary emotion: “I am so angry because this is terrible quality.” Stick to facts. The seller needs information, not complaints.
- Guessing the cause: “I think the motor is broken because it makes a weird noise.” Instead, say: “The motor makes a grinding noise when turned on.”
- Forgetting the order number: Always include your order number or product reference. Without it, the seller cannot find your purchase.
Better Alternatives for Common Phrases
Replace weak or unclear phrases with stronger, more useful ones.
| Weak Phrase | Better Alternative | When to Use It |
|---|---|---|
| “It’s broken.” | “The screen has a visible crack in the top-left corner.” | When you can see the damage. |
| “It doesn’t fit.” | “The size M shirt measures 2 inches shorter in the sleeves than the size chart indicates.” | When the size is wrong. |
| “It arrived damaged.” | “The box was crushed on one side, and the ceramic vase inside has a chip on the rim.” | When the packaging is damaged. |
| “It stopped working.” | “After three uses, the fan blade no longer spins when the switch is turned on.” | When the product fails after use. |
How to Structure Your Problem Summary
Follow this simple structure for any return message. It works for both formal and informal contexts.
- Greeting and order reference: “Dear Support, regarding order #7890…”
- State the problem: “The coffee maker leaks water from the bottom during brewing.”
- Give details: “I noticed this on the second use. The first use was fine.”
- Explain the impact: “Water pools on the counter, and the machine stops before finishing.”
- Request action: “Please let me know how to return it for a replacement or refund.”
When to Use a Short Summary vs. a Detailed One
Use a short summary when you are in a live chat or sending a quick message through an app. The seller can ask for more details if needed. Use a detailed summary when writing an email or filling out a return form. The seller may not reply immediately, so include everything they need to process your request. For example, in a chat you might say: “The coffee maker leaks. Order 7890.” In an email, you would write the full structure above.
Mini Practice: Write Your Own Problem Summary
Try these four practice questions. Write your answer in your mind or on paper, then check the suggested answer below.
Question 1: You ordered a pair of running shoes. The left shoe has a loose sole that flaps when you walk. Write a short problem summary for a live chat.
Suggested Answer: “Hi, I got the running shoes from order 1234. The sole on the left shoe is loose and flaps when I walk. Can I return them?”
Question 2: You bought a desk lamp. The light flickers after 10 minutes of use. Write a formal email problem summary.
Suggested Answer: “Dear Customer Service, I am writing about order 5678 for a desk lamp. The light starts flickering after about 10 minutes of use and does not stop until I turn it off. This makes it difficult to read. Please advise on the return process.”
Question 3: You received a book with missing pages (pages 45-60 are blank). Write a short message for an app.
Suggested Answer: “Hello, order 9012. The book I received has blank pages from 45 to 60. Can I get a replacement?”
Question 4: You bought a phone case, but the cutouts for the charging port and speakers do not line up. Write a problem summary for a return form.
Suggested Answer: “The phone case for model XYZ does not fit correctly. The charging port cutout is misaligned by about 2mm, and the speaker holes are partially covered. The case is otherwise undamaged.”
Frequently Asked Questions
1. Should I include photos or videos in my problem summary?
Yes, if the platform allows attachments. A photo of the defect or a short video showing the problem can make your summary much clearer. Mention in your message that you have attached evidence: “I have attached a photo showing the crack on the screen.”
2. What if I am not sure what caused the problem?
Do not guess. Just describe what you see or experience. For example, say “The battery drains from 100% to 0% in two hours without use” instead of “I think the battery is defective.” The seller will determine the cause.
3. How long should my problem summary be?
For a formal email, 3 to 5 sentences is usually enough. For a chat message, 1 to 2 sentences works. The key is to include the essential details without extra words.
4. Can I use the same summary for different products?
No. Each product has a unique issue. Always customize your summary to the specific defect. Copying a generic summary like “The item is defective” will slow down the return process because the seller will need to ask for more details.
Final Tips for Writing a Useful Problem Summary
Keep your language simple and direct. Use the present tense to describe the current state of the product. Avoid words like “always” or “never” unless they are true. For example, “The screen always freezes after 5 minutes” is better than “The screen freezes sometimes.” Finally, always proofread your message before sending. A clear, error-free summary shows that you are serious and helps the seller help you faster.
For more guidance on how to start your return message, visit our Product Return Message Starters section. If you need help with polite requests during the return process, check out Product Return Message Polite Requests. You can also practice your replies with our Product Return Message Practice Replies page. For any questions about this guide, see our FAQ or contact us.