When you contact tech support, the most important skill is explaining your problem clearly and accurately. This guide shows you exactly how to describe technical issues in English so the support agent understands you quickly and can help you solve the problem. You will learn the right words, sentence patterns, and tone for different situations, whether you are on a phone call, in a live chat, or writing an email.
Quick Answer: The Three-Step Formula for Explaining Any Problem
Use this simple structure every time you explain a tech problem:
- State what happened – Describe the action you took or what you were doing.
- State what went wrong – Describe the unexpected result or error.
- State what you expected – Describe what should have happened instead.
Example: “I clicked the ‘Save’ button, but the document did not save. I expected it to save automatically.”
Key Vocabulary for Problem Explanations
These words and phrases are essential for describing tech issues. Use them to make your explanation precise.
| Word / Phrase | Meaning | Example Sentence |
|---|---|---|
| Crash | The program stops working completely | “The app crashed when I tried to open the file.” |
| Freeze | The program stops responding but does not close | “My screen froze during the video call.” |
| Error message | A notification that something is wrong | “I saw an error message that said ‘Access Denied’.” |
| Not loading | The page or content does not appear | “The website is not loading on my browser.” |
| Slow performance | The system runs slower than normal | “My computer has slow performance after the update.” |
| Connection issue | Problem with internet or network | “I am having a connection issue with the Wi-Fi.” |
| Missing feature | A function that should be there is not available | “The ‘Export’ button is missing from the menu.” |
| Unexpected behavior | The system does something you did not intend | “The software is showing unexpected behavior when I type.” |
Formal vs. Informal Problem Explanations
The tone you use depends on the situation. Use formal language for emails and professional chats. Use informal language for quick phone calls or casual support chats.
Formal (Email or Professional Chat)
Use complete sentences and polite language. Be specific and include details like error codes.
Example:
“Dear Support Team, I am writing to report an issue with the billing system. When I attempted to generate an invoice for order #4521, the system displayed error code E-304 and did not complete the process. I expected the invoice to be generated successfully. Please advise on the next steps.”
Informal (Phone or Quick Chat)
Use shorter sentences and everyday words. You can be more direct.
Example:
“Hi, I have a problem with the billing system. I tried to make an invoice for order #4521, but it gave me an error code E-304 and stopped working. It should have just made the invoice. Can you help?”
Comparison Table: Formal vs. Informal
| Situation | Formal | Informal |
|---|---|---|
| Email to support | “I am experiencing an issue with…” | “I have a problem with…” |
| Live chat | “Could you please assist me with…” | “Can you help me with…” |
| Phone call | “I would like to report a technical difficulty.” | “Something is not working.” |
| Describing error | “The application encountered an error.” | “The app crashed.” |
| Asking for help | “I would appreciate your guidance.” | “What should I do?” |
Natural Examples for Different Tech Problems
Here are realistic examples you can adapt to your own situation. Each example follows the three-step formula.
Example 1: Software Not Installing
“I tried to install the latest version of the editing software. The installation started but stopped at 45% and showed a message saying ‘Installation failed.’ I expected it to install completely without errors.”
Example 2: Email Not Sending
“I composed a new email and clicked the send button. The email stayed in my outbox and never went through. I expected it to send immediately.”
Example 3: Printer Not Working
“I sent a print command from my laptop to the office printer. The printer did not respond, and I did not see any error on the screen. I expected the document to print normally.”
Example 4: Login Problem
“I entered my username and password on the login page. The page refreshed and showed a blank screen instead of taking me to my dashboard. I expected to log in successfully.”
Common Mistakes When Explaining Problems
Avoid these errors that can confuse the support agent and slow down the solution.
Mistake 1: Being Too Vague
Wrong: “My computer is not working.”
Better: “My computer turns on, but the screen stays black after the logo appears.”
Mistake 2: Using Incorrect Technical Terms
Wrong: “The internet is broken.”
Better: “I cannot connect to the Wi-Fi network. Other devices in the house are connected, but my laptop shows ‘No Internet Access.'”
Mistake 3: Giving Too Much Unnecessary Information
Wrong: “I was sitting at my desk drinking coffee, and then I opened the program, and then I clicked something, and then it crashed.”
Better: “I opened the program and clicked the ‘Start Scan’ button. The program crashed immediately.”
Mistake 4: Not Mentioning What You Expected
Wrong: “The file did not save.”
Better: “I clicked ‘Save,’ but the file did not save. I expected it to save to my Documents folder.”
Better Alternatives for Common Phrases
Replace weak or unclear phrases with more precise ones.
| Avoid This | Use This Instead |
|---|---|
| “It is not working.” | “The program crashes when I click the ‘Submit’ button.” |
| “Something is wrong.” | “I see an error message that says ‘Invalid input.'” |
| “It is slow.” | “The page takes more than 30 seconds to load.” |
| “I cannot do it.” | “I cannot access the settings menu.” |
| “It is broken.” | “The search function returns no results even when I type exact keywords.” |
When to Use Each Type of Explanation
- Phone call: Use short, clear sentences. Speak slowly. Repeat the key problem at the beginning. Example: “I am calling because my email stopped sending messages about an hour ago.”
- Live chat: Write one or two sentences at a time. Do not send a long paragraph. Wait for the agent to respond. Example: “I am having a problem with the login page. It shows a blank screen after I enter my password.”
- Email: Write a structured message. Include the steps you took, the error, and what you expected. Add any error codes or screenshots if possible. Example: “Subject: Login Issue – Blank Screen After Password Entry. Body: I attempted to log in at 10:00 AM. After entering my password, the page went blank. I expected to see my dashboard. Error code: none.”
Mini Practice Section
Test your understanding. Read each situation and choose the best explanation.
Question 1: You are on a live chat. Your internet browser keeps closing by itself. What do you say?
A) “My browser is bad.”
B) “My browser closes by itself every few minutes when I am on any website. I expected it to stay open.”
C) “Fix my browser.”
Answer: B. This is clear, specific, and follows the three-step formula.
Question 2: You are writing an email about a missing file. What is the best opening?
A) “I lost a file.”
B) “I saved a report to the shared drive yesterday, but today it is not there. I expected it to remain in the folder.”
C) “Where is my file?”
Answer: B. It explains what you did, what happened, and what you expected.
Question 3: You are on the phone. The software update failed. What should you say first?
A) “I tried to update the software, but it failed at 80% and showed error code U-22.”
B) “The update did not work.”
C) “I hate updates.”
Answer: A. It gives the specific action, the result, and the error code.
Question 4: You are in a live chat. The agent asks, “What happened exactly?” Which reply is best?
A) “I clicked the button and nothing happened.”
B) “I clicked the ‘Download’ button, the page refreshed, but the download did not start. I expected a file to download.”
C) “You should know what happened.”
Answer: B. It is precise and follows the formula.
Frequently Asked Questions
1. What if I do not know the exact error message?
Describe what you saw as clearly as possible. Say “There was a pop-up message, but I closed it before reading the details.” Then describe the problem. The agent can help you find the error again.
2. Should I use technical terms even if I am not sure?
Only use terms you understand. It is better to say “The program stopped responding” than to guess and say “The program crashed” if you are not sure. Guessing can lead to wrong troubleshooting steps.
3. How do I explain a problem that happens only sometimes?
Use words like “occasionally,” “sometimes,” or “intermittently.” Give an example of when it happened. Example: “The app occasionally freezes when I switch between tabs. It happened twice this morning.”
4. What if the support agent does not understand me?
Stay calm. Repeat your explanation using different words. Use the three-step formula again. You can also say, “Let me explain it another way.” Then simplify your description. For more practice with different conversation situations, visit our Tech Support Conversation Starters and Tech Support Conversation Polite Requests sections.
Final Tips for Success
Practice explaining problems out loud. Record yourself and listen. Check if you included all three steps: what you did, what went wrong, and what you expected. The more you practice, the more natural it will become. For additional help, review our Tech Support Conversation Problem Explanations category for more examples. If you have questions about this guide, please see our FAQ page or contact us.
Comments are closed.