How to Give a Useful Problem Summary in Repair Service Conversation English
When you contact a repair service, the first thing the technician needs is a clear, accurate summary of the problem. A useful problem summary tells them what is wrong, when it started, and what you have already tried, without extra details or emotional language. This guide shows you exactly how to structure your problem summary in English, with phrases for phone calls, in-person visits, and emails, so the repair person can start helping you immediately.
Quick Answer: The Three-Part Problem Summary
To give a useful problem summary, follow this simple structure:
- State the main issue – What is not working?
- Add a time or frequency detail – When did it start? How often does it happen?
- Mention what you have tried – Did you check anything? Did you restart it?
Example: “My washing machine stops mid-cycle. It started doing this two days ago, and I already checked the drain hose.” This gives the technician a clear starting point.
Why a Good Problem Summary Matters
Repair service conversations are time-sensitive. The technician uses your summary to decide which tools to bring, which parts to order, and how long the repair might take. A vague or emotional summary like “It’s broken, fix it!” forces them to ask many follow-up questions. A structured summary saves time and reduces frustration for both sides.
Key Vocabulary for Problem Explanations
Use these common words and phrases to describe problems accurately:
- Not working – general problem (e.g., “The remote is not working.”)
- Makes a strange noise – sound-related issue (e.g., “The fridge makes a clicking noise.”)
- Won’t turn on / Won’t start – power or startup issue
- Stops mid-cycle – stops before finishing
- Leaks / Drips – water or fluid escaping
- Overheats – gets too hot
- Error code – a number or letter shown on the display
- Intermittent – works sometimes, stops sometimes
- Slower than usual – performance issue
Formal vs. Informal Problem Summaries
The tone you use depends on whether you are speaking on the phone, writing an email, or talking in person. Below is a comparison table to help you choose the right level of formality.
| Context | Tone | Example |
|---|---|---|
| Phone call to a repair shop | Informal to neutral | “Hi, my dishwasher isn’t draining. It started yesterday. I cleaned the filter, but it didn’t help.” |
| Email to a service center | Formal | “I am writing to report an issue with my refrigerator. The ice maker has stopped producing ice. This began approximately three days ago. I have checked the water supply line, and it appears to be connected properly.” |
| In-person at a repair counter | Neutral | “I have a laptop that won’t charge. The battery light blinks orange. I tried a different cable, but it still doesn’t work.” |
| Online chat or text | Informal | “My AC is blowing warm air. It’s been like this since this morning. I changed the filter already.” |
Natural Examples of Problem Summaries
Here are realistic examples for different repair situations. Notice how each follows the three-part structure.
Example 1: Washing Machine
Customer: “My washing machine shakes violently during the spin cycle. It started about a week ago. I checked if it was level, and it seems fine.”
Technician: “Thank you. That helps. I will check the drum bearings and suspension springs.”
Example 2: Laptop
Customer: “My laptop screen flickers when I move the lid. It has been doing this for two days. I updated the drivers, but the problem continues.”
Technician: “That sounds like a loose display cable. I will bring a replacement cable.”
Example 3: Air Conditioner
Customer: “The air conditioner runs but does not cool the room. It started this afternoon. I checked the thermostat setting and the air filter.”
Technician: “Good. It could be a refrigerant issue or a compressor problem. I will test both.”
Example 4: Refrigerator
Customer: “The refrigerator is not cold enough. The temperature reads 15°C inside. This started after I defrosted it yesterday. I did not change any settings.”
Technician: “That is helpful. It may need time to stabilize, or there could be a thermostat issue.”
Common Mistakes When Giving a Problem Summary
English learners often make these mistakes. Avoid them to sound clear and professional.
Mistake 1: Giving too much emotional detail
Wrong: “I am so frustrated! This stupid machine never works! I am going to throw it out!”
Better: “The machine stops working after 10 minutes. It has happened three times this week.”
Mistake 2: Being too vague
Wrong: “It’s broken.”
Better: “The power button does not respond. The screen stays black.”
Mistake 3: Guessing the cause
Wrong: “I think the motor is dead.”
Better: “The motor makes a grinding sound, then stops. I am not sure what is wrong.”
Mistake 4: Forgetting to mention what you tried
Wrong: “The internet is not working.”
Better: “The internet is not working. I restarted the router and checked the cables, but there is no change.”
Better Alternatives for Common Phrases
Replace weak or unclear phrases with more precise ones.
- Instead of: “It’s acting weird.” → Use: “It turns off randomly.”
- Instead of: “It doesn’t work right.” → Use: “It does not heat properly.”
- Instead of: “It’s making noise.” → Use: “It makes a high-pitched whining sound.”
- Instead of: “It stopped.” → Use: “It stops after 5 minutes of use.”
When to Use Each Type of Summary
Choose your summary style based on the situation:
- Phone call: Keep it short. The technician may be writing notes. Say the main issue first, then details.
- Email: Include all relevant details in one paragraph. Use bullet points if the problem has multiple parts.
- In-person: You can show the problem. Point to the part that is not working and describe what you see.
- Online form: Follow the form fields. Do not repeat information. Be specific about error codes.
Mini Practice: Write Your Own Problem Summary
Read each situation and write a short problem summary using the three-part structure. Then check the suggested answer.
Question 1
Situation: Your microwave makes a loud buzzing sound when you use it. It started yesterday. You checked the turntable, and it is not blocked.
Your summary: _________________________________
Suggested answer: “My microwave makes a loud buzzing sound when it runs. It started yesterday. I checked the turntable, and nothing is blocking it.”
Question 2
Situation: Your car’s air conditioner blows warm air. It has been like this for a week. You checked the coolant level, and it is fine.
Your summary: _________________________________
Suggested answer: “The car AC blows warm air. It started about a week ago. I checked the coolant level, and it is fine.”
Question 3
Situation: Your printer shows an error code “E4” and will not print. This happened after you changed the ink cartridge. You turned it off and on again.
Your summary: _________________________________
Suggested answer: “My printer shows error code E4 and will not print. It started after I changed the ink cartridge. I restarted the printer, but the error remains.”
Question 4
Situation: Your television screen has a vertical line of dead pixels. You noticed it this morning. You did not try anything yet.
Your summary: _________________________________
Suggested answer: “My TV screen has a vertical line of dead pixels. I noticed it this morning. I have not tried anything yet.”
Frequently Asked Questions
1. Should I always mention what I tried before calling?
Yes, if you tried something simple like restarting or checking a cable. It saves the technician from suggesting the same thing. If you did not try anything, say “I have not tried anything yet.”
2. What if I do not know the exact name of the part?
Describe the part by its location or function. For example, “the part on the bottom that spins” or “the button on the top right.” The technician will understand.
3. Is it okay to say “I think” in a problem summary?
Yes, but only for things you are unsure about. For example, “I think the water is coming from the back.” Do not use “I think” for the main problem. Say “The water is coming from the back” if you are sure.
4. How long should my problem summary be?
Two to four sentences is ideal. Longer summaries can confuse the technician. Stick to the three-part structure: main issue, time/frequency, and what you tried.
Final Tips for Repair Service Conversations
Practice your problem summary before you call or write. Write it down if you are nervous. Remember that the technician wants to help you, and a clear summary makes their job easier. For more help with starting the conversation, see our Repair Service Conversation Starters. If you need to make polite requests during the repair, visit Repair Service Conversation Polite Requests. To practice replying to technician questions, check Repair Service Conversation Practice Replies. For more problem explanation examples, browse Repair Service Conversation Problem Explanations. If you have questions about this guide, see our FAQ.
