When you write a tech support message, explaining your problem clearly is the most important step. Many English learners make the same mistakes: they give too little detail, use the wrong tense, or sound unclear. This guide directly addresses the most frequent problem explanation mistakes in tech support English and shows you how to fix them. You will learn what to say, what to avoid, and how to write explanations that help support teams understand you quickly.
Quick Answer: What Are the Biggest Mistakes?
The most common problem explanation mistakes in tech support messages include:
- Using the wrong verb tense (e.g., saying “my computer crashes” when it happened once).
- Giving vague descriptions (e.g., “it doesn’t work” without saying what exactly happens).
- Forgetting to mention error messages or codes.
- Writing too much background information before the actual problem.
- Using informal or unclear language in email support.
Fixing these mistakes makes your message clearer and gets you faster help.
Mistake 1: Wrong Verb Tense for the Problem
One of the most frequent errors is using the wrong tense to describe when the problem happens. In tech support, you need to be precise about whether the issue is ongoing, happened once, or happens repeatedly.
Formal vs. Informal Context
In a formal email, you should use the present perfect for ongoing problems and the past simple for one-time events. In informal chat, you can use the present simple for repeated issues, but still be careful with one-time events.
| Situation | Incorrect | Correct | Explanation |
|---|---|---|---|
| Ongoing problem (started in the past and continues) | “My internet is not working yesterday.” | “My internet has not been working since yesterday.” | Use present perfect for problems that started in the past and still affect you. |
| One-time event | “My computer crashes when I open the file.” | “My computer crashed when I opened the file.” | Use past simple for a single completed event. |
| Repeated problem | “The app was freezing every time I use it.” | “The app freezes every time I use it.” | Use present simple for habits or repeated actions. |
Natural Examples
- Ongoing: “My email has not been sending attachments since this morning.”
- One-time: “I tried to log in, but the page showed an error and then closed.”
- Repeated: “Every time I click ‘Save,’ the program freezes for about 10 seconds.”
Common Mistake
“My printer is not working yesterday.” This mixes present continuous with a past time. Instead say: “My printer has not been working since yesterday” (ongoing) or “My printer did not work yesterday” (if it is working now).
Better Alternative
If you are not sure about the tense, use “I am experiencing” + noun. For example: “I am experiencing a problem with my printer since yesterday.” This is safe and clear.
Mistake 2: Vague Problem Descriptions
Saying “it doesn’t work” or “there is a problem” is too vague. Support agents need specific details to help you. A vague explanation forces them to ask follow-up questions, which slows everything down.
Formal vs. Informal Context
In a formal email, you should describe exactly what you see, hear, or cannot do. In informal chat, you can be a little shorter, but still specific.
| Vague | Specific | Why It Helps |
|---|---|---|
| “My computer is slow.” | “My computer takes more than 5 minutes to start up, and programs freeze when I open them.” | Gives a measurable time and a clear symptom. |
| “The app is not working.” | “When I open the app, I see a blank white screen and then it closes automatically.” | Describes the exact behavior. |
| “I cannot send emails.” | “When I click ‘Send,’ I get an error message that says ‘Connection timed out.'” | Includes the error message text. |
Natural Examples
- “When I try to print, the printer shows ‘Paper jam’ even though there is no paper stuck.”
- “The login page loads, but after I enter my password, it just refreshes without any error.”
Common Mistake
“My internet is bad.” This does not tell the agent what “bad” means. Is it slow? Does it disconnect? Do some sites not load?
Better Alternative
Use the formula: What I do + What happens + What I see. Example: “I try to open Google Chrome, but it shows a message saying ‘Not responding,’ and then I have to force close it.”
Mistake 3: Forgetting Error Messages or Codes
Error messages and codes are the most valuable information you can give. Many learners leave them out because they think they are not important or they do not know how to write them.
When to Use It
Always include the exact error message or code if you see one. Write it exactly as it appears, including numbers and punctuation. This helps the support team search their database for a solution.
Natural Examples
- “I get error code 0x80070002 when I try to update Windows.”
- “The message says: ‘Your session has expired. Please log in again.’ But I was already logged in.”
Common Mistake
“I got some error.” This tells the agent nothing. Even if you do not remember the exact code, describe what the message said.
Better Alternative
If you cannot copy the error, write it down word for word. For example: “The error message said: ‘Unable to connect to server. Please check your network settings.'”
Mistake 4: Too Much Background Information
Some learners write a long story before they get to the problem. For example: “I bought this computer two years ago. I use it for work. Yesterday I installed a new program. Then I restarted it. After that, I noticed…” This buries the actual problem.
Formal vs. Informal Context
In a formal email, you can include relevant background, but put the problem first. In informal chat, get to the point immediately.
| Too Much Background | Better |
|---|---|
| “I have been using this laptop for three years. It was working fine until last week. I usually keep it updated. But now…” | “My laptop screen has been flickering since last week. It happens when I open any video.” |
| “I am a student and I need this for my classes. Yesterday I tried to open a PDF…” | “I cannot open PDF files in Adobe Reader. When I double-click, nothing happens.” |
Natural Examples
- “I cannot connect to Wi-Fi. The network shows up, but when I enter the password, it says ‘Incorrect password’ even though I am sure it is correct.”
- “My keyboard types the wrong letters. For example, when I press ‘a,’ it types ‘q.'”
Common Mistake
Starting with “I hope you are doing well” and then writing three sentences about your day before mentioning the problem. In tech support, the problem is the priority.
Better Alternative
Start your message with the problem in the first sentence. Then add background if needed. Example: “I am having trouble with my email. It stopped sending attachments yesterday. I have not changed any settings.”
Mistake 5: Informal Language in Formal Emails
Using very casual language in a formal support email can make you sound less serious or unclear. For example, “My PC is acting up” or “It’s being weird” are too vague and informal for email support.
Formal vs. Informal Context
In a live chat, you can be more casual, but still clear. In an email, use professional language.
| Informal (Chat OK) | Formal (Email Better) |
|---|---|
| “My laptop is being dumb.” | “My laptop is not responding to any commands.” |
| “The thingy is broken.” | “The power button does not turn on the device.” |
| “It keeps glitching.” | “The screen flickers and the cursor jumps randomly.” |
Natural Examples
- Formal email: “I am writing to report that my account has been locked since this morning. I have tried resetting the password, but I do not receive the reset email.”
- Informal chat: “Hey, my account is locked. I tried resetting the password but no email came.”
Common Mistake
Using “stuff” or “things” to describe the problem. For example: “Some stuff is not working.” This is too vague for any context.
Better Alternative
Name the specific feature or function. Instead of “stuff,” say “the search function” or “the file upload option.”
Mini Practice Section
Read each problem description and choose the best way to explain it in a tech support email.
Question 1: Your internet disconnects every 10 minutes. What do you write?
A. “My internet is bad.”
B. “My internet disconnects every 10 minutes, and I have to restart the router to reconnect.”
C. “My internet was disconnecting yesterday.”
Answer: B. It is specific and describes the pattern.
Question 2: You tried to install an update, but it failed. You saw an error code.
A. “The update did not work.”
B. “I tried to install update version 2.1, but it failed with error code 0x800f0831.”
C. “Something went wrong with the update.”
Answer: B. It includes the version and the error code.
Question 3: Your mouse cursor moves, but clicking does nothing.
A. “My mouse is broken.”
B. “The cursor moves, but when I left-click, nothing happens. Right-click also does not work.”
C. “My mouse is not clicking.”
Answer: B. It describes exactly what works and what does not.
Question 4: You cannot open a specific website, but other sites work.
A. “The internet is not working.”
B. “I cannot open example.com. Other websites like google.com work fine. I get a ‘404 Not Found’ error.”
C. “One site is down.”
Answer: B. It names the site, mentions that others work, and includes the error.
FAQ: Common Problem Explanation Mistakes
1. Should I always include the error code?
Yes, if you see one. Error codes are the fastest way for support to identify the issue. Write it exactly as it appears.
2. Is it okay to say “it doesn’t work” in a chat?
In a live chat, you can start with “it doesn’t work,” but you should immediately follow with specific details. For example: “It doesn’t work. When I click the button, nothing happens.”
3. How do I describe a problem that happens sometimes but not always?
Use words like “occasionally,” “sometimes,” or “intermittently.” Also describe the pattern. Example: “The screen freezes occasionally, about once every hour, for 10 seconds.”
4. What if I do not know the technical term for the problem?
Describe what you see in simple words. For example, instead of “the GPU is failing,” say “the screen shows colored lines and then goes black.” Support can understand plain descriptions.
Final Tips for Better Problem Explanations
To avoid common mistakes in tech support messages, remember these three rules:
- Be specific: Say exactly what happens, when it happens, and what you see.
- Use the right tense: Present perfect for ongoing issues, past simple for one-time events, present simple for repeated problems.
- Put the problem first: Start your message with the issue, not with background stories.
For more help with writing clear tech support messages, explore our Tech Support Message Problem Explanations section. You can also review Tech Support Message Starters for good opening lines, or Tech Support Message Polite Requests for asking for help politely. If you want to practice replying, visit Tech Support Message Practice Replies. For any questions about this guide, see our FAQ page.
Comments are closed.