How to Give a Useful Problem Summary in Complaint Resolution Conversation English
When you need to resolve a complaint in English, the most important part of the conversation is your problem summary. A useful problem summary clearly explains what went wrong, when it happened, and what you expected, without unnecessary emotion or confusion. This guide will show you exactly how to structure your problem summary so the other person understands your issue quickly and can work toward a solution.
Quick Answer: What Makes a Problem Summary Useful?
A useful problem summary includes three key elements: the specific issue, the impact on you, and what you would like to happen next. Keep it short, factual, and polite. For example: “I ordered a laptop on Monday, but it arrived with a cracked screen. I need a replacement or a full refund.” This gives the listener everything they need to help you.
The Structure of a Strong Problem Summary
Think of your problem summary as a three-part formula. Each part has a clear purpose, and together they create a complete picture.
Part 1: State the Problem Clearly
Start with what happened. Be specific about the product, service, or situation. Avoid vague language like “something is wrong” or “it doesn’t work.” Instead, say exactly what the issue is.
Example: “The software I purchased from your website does not open after installation.”
Part 2: Explain the Impact
Tell the listener how this problem affects you. This helps them understand why it matters and why they should take it seriously. Keep the focus on facts, not feelings.
Example: “Because of this, I cannot complete the project I was working on, and I am now behind schedule.”
Part 3: State Your Desired Outcome
End with what you want. This could be a refund, a replacement, a fix, or an apology. Being clear about your expectation makes it easier for the other person to respond.
Example: “I would like a full refund or a working replacement sent to me within three business days.”
Formal vs. Informal Problem Summaries
The tone of your problem summary depends on the situation. Use this table to decide which style fits best.
| Situation | Tone | Example |
|---|---|---|
| Email to a company | Formal | “I am writing to report an issue with my recent order. The item I received is damaged, and I kindly request a replacement.” |
| Phone call to customer service | Semi-formal | “Hi, I’m calling because the package I got yesterday has a tear in the box, and the product inside is broken. Can you help me with a return?” |
| Chat with a friend | Informal | “Hey, the phone case I bought from that shop is already peeling. I’m going to ask for a refund.” |
| In-person complaint at a store | Polite but direct | “Excuse me, I bought this shirt here yesterday, but when I tried it on at home, I found a stain. I’d like to exchange it.” |
Natural Examples of Problem Summaries
Here are four realistic examples that show how to use the three-part structure in different contexts.
Example 1: Defective Product (Email)
Problem: “I received my order of headphones on March 10, but the left earbud does not produce any sound.”
Impact: “This means I cannot use them for my online meetings, which I have every day.”
Outcome: “Please send a replacement pair or issue a refund to my original payment method.”
Example 2: Service Delay (Phone Call)
Problem: “I scheduled a technician to fix my internet on Tuesday between 2 and 4 PM, but no one arrived.”
Impact: “I work from home, so I lost a full day of work waiting.”
Outcome: “Can you reschedule for tomorrow morning and confirm the time by email?”
Example 3: Billing Error (Chat)
Problem: “My last bill shows a charge of $50 for a premium plan, but I only have the basic plan.”
Impact: “I was overcharged, and I need this corrected before my next payment.”
Outcome: “Please remove the extra charge and refund the difference.”
Example 4: Wrong Item Delivered (In-Person)
Problem: “I ordered a black desk lamp, but the box contains a white one.”
Impact: “It doesn’t match my office setup, so I can’t use it.”
Outcome: “I would like to exchange it for the correct color.”
Common Mistakes When Summarizing a Problem
Even advanced English learners make these errors. Avoid them to keep your summary clear and effective.
Mistake 1: Being Too Vague
Wrong: “Something is wrong with my order.”
Better: “The shirt I ordered is the wrong size. I ordered a medium, but I received a small.”
Mistake 2: Adding Too Much Emotion
Wrong: “I am so angry and frustrated because you ruined my day!”
Better: “I am disappointed because the delay caused me to miss an important meeting.”
Mistake 3: Not Stating What You Want
Wrong: “The product is broken. What are you going to do about it?”
Better: “The product is broken. I would like a replacement sent to me.”
Mistake 4: Giving Too Much Background
Wrong: “I ordered this on a Tuesday because it was on sale, and I used a coupon code, and then I waited for three days, and then the delivery guy came, but…”
Better: “I ordered this on Tuesday, and it arrived today with a missing part.”
Better Alternatives for Common Phrases
Some phrases are overused or unclear. Here are stronger alternatives.
| Instead of saying… | Say this… | When to use it |
|---|---|---|
| “It doesn’t work.” | “The device does not power on.” | When describing a technical issue |
| “I am not happy.” | “The service did not meet my expectations.” | In formal written complaints |
| “Fix it.” | “Please resolve this issue as soon as possible.” | When you want a polite but firm request |
| “You made a mistake.” | “There seems to be an error with my order.” | To avoid sounding accusatory |
Nuance in Problem Summaries
Understanding subtle differences in language can make your complaint more effective. Here are a few important nuances.
Direct vs. Indirect Language
In English, being direct is often seen as honest and efficient, but in very formal situations, indirect language can be more polite. Compare these two summaries:
- Direct: “You sent me the wrong item. Send the correct one.”
- Indirect: “I believe there may have been a mix-up with my order. Could you please check and let me know how to proceed?”
Use direct language in casual or urgent situations. Use indirect language in formal emails or when speaking to someone in a higher position.
Using “I” vs. “You”
Starting sentences with “I” focuses on your experience, which feels less confrontational. Starting with “You” can sound like an accusation.
- Better: “I received a damaged product.”
- Worse: “You sent me a damaged product.”
Mini Practice Section
Test your understanding with these four questions. Write your own answer, then check the suggested response.
Question 1
You ordered a pizza, but it arrived cold. Write a problem summary for a phone call to the restaurant.
Suggested answer: “I ordered a large pepperoni pizza about 30 minutes ago, but it arrived cold. I can’t eat it like this. Can you send a fresh one or refund my money?”
Question 2
Your internet has been down for two days. Write a problem summary for an email to your internet provider.
Suggested answer: “My internet connection has been down since Monday morning. I work from home, so this is causing serious problems. Please send a technician to fix it as soon as possible.”
Question 3
You bought a ticket for a concert, but the date on the ticket is wrong. Write a problem summary for a chat with customer support.
Suggested answer: “I bought a ticket for the concert on June 15, but the ticket shows June 16. I need the date corrected or a new ticket issued.”
Question 4
Your hotel room was not cleaned during your stay. Write a problem summary for an in-person conversation at the front desk.
Suggested answer: “I checked in two days ago, but my room has not been cleaned once. The trash is full, and I need fresh towels. Can you please arrange cleaning today?”
Frequently Asked Questions
1. How long should my problem summary be?
Keep it to two or three sentences. Any longer, and you risk confusing the listener. Focus on the problem, the impact, and what you want.
2. Should I apologize when giving a problem summary?
No. You do not need to apologize for reporting a problem. However, if you are unsure about the details, you can say “I’m sorry, but I’m not sure if this is the right department” to be polite.
3. What if the person I’m talking to does not understand me?
Slow down and repeat the key points. Use simple words. For example, instead of “malfunctioning,” say “not working.” You can also ask, “Would you like me to explain again?”
4. Can I use the same summary for email and phone?
Yes, but adjust the tone. Emails can be more detailed and formal. Phone calls should be shorter and more conversational. In both cases, keep the three-part structure.
For more help with starting a complaint conversation, visit our Complaint Resolution Conversation Starters section. If you need to practice polite requests, check out Complaint Resolution Conversation Polite Requests. For more examples of explaining problems, explore Complaint Resolution Conversation Problem Explanations. You can also see how to reply to complaints in Complaint Resolution Conversation Practice Replies. If you have questions about how we create our guides, please see our Editorial Policy.
