How to Report an Issue in a Tech Support Message

When you need help with a computer, phone, or software, the most important part of your message is clearly explaining what went wrong. To report an issue effectively in a tech support message, you need to state the problem directly, include what you were doing when it happened, and mention any error messages you saw. This guide will show you exactly how to write that part of your message so the support team can understand and fix your problem quickly.

Quick Answer: How to Report an Issue

Start with a clear sentence like “I am having an issue with [the product/feature].” Then add one or two sentences describing what happened. For example: “I am having an issue with my email. When I try to send a message, I get an error that says ‘Connection failed.'” Keep it short and factual. Avoid long stories or emotional words.

Why Clear Problem Explanations Matter

Tech support teams handle many requests every day. If your problem explanation is unclear, they may ask for more details, which delays the solution. A well-written problem explanation helps them diagnose the issue faster. It also shows that you are organized and serious about getting help.

For more guidance on starting your message, visit our Tech Support Message Starters section.

Key Parts of a Good Problem Explanation

Every problem explanation should include these three things:

• What you were doing: “I was trying to log into my account.”
• What went wrong: “The page showed a blank screen.”
• Any error details: “The error code was 500.”

You do not need to add your opinion or guess the cause. Just report the facts.

Formal vs. Informal Tone

Your tone depends on how you are contacting support. Here is a comparison:

In formal messages, use complete sentences and polite words. In informal messages, you can be shorter, but still clear.

Natural Examples

Here are realistic examples for different situations:

Example 1: Software crash

Formal email: “I am reporting an issue with the video editing software. When I try to export a project, the program closes without warning. I have tried restarting my computer, but the problem continues.”

Informal chat: “The video editor keeps crashing when I export. Any ideas?”

Example 2: Login problem

Formal email: “I cannot log into my account. After entering my username and password, the page refreshes and shows no error message. I have reset my password twice.”

Informal chat: “I can’t log in. It just refreshes the page. I already reset my password.”

Example 3: Hardware issue

Formal email: “My laptop battery stops charging at 60%. The power light is on, but the battery percentage does not increase. This started three days ago.”

Informal chat: “My laptop battery won’t charge past 60%. It started a few days ago.”

Common Mistakes

English learners often make these errors when reporting issues:

• Mistake 1: Being too vague. “My computer is broken.” This does not help. Instead say: “My computer screen is black after I turned it on.”
• Mistake 2: Adding unnecessary details. “I was listening to music and then I decided to check my email and then the screen froze.” Keep it simple: “The screen froze while I was checking my email.”
• Mistake 3: Using the wrong tense. “The error shows yesterday.” Use past tense for completed actions: “The error showed yesterday.” Or present perfect for recent events: “The error has shown up twice today.”
• Mistake 4: Guessing the cause. “I think the server is down because of a virus.” Let the support team diagnose. Just report what you saw.

Better Alternatives for Common Phrases

Here are some phrases you can improve:

• Avoid: “It doesn’t work.” Use: “The app does not open after I click the icon.”
• Avoid: “Something is wrong.” Use: “The Wi-Fi disconnects every five minutes.”
• Avoid: “I have a problem.” Use: “I am unable to save files to the cloud folder.”

When you use specific language, the support team can start troubleshooting immediately.

When to Use Each Type of Problem Explanation

Different situations call for different levels of detail:

• Urgent issue (system down): Be direct and include the impact. “The payment system is down. Customers cannot complete purchases. This started at 10:00 AM.”
• Minor issue (cosmetic bug): Be polite and less urgent. “I noticed that the button color is wrong on the settings page. It is not critical, but I wanted to report it.”
• Recurring issue: Mention frequency. “The app crashes every time I upload a file larger than 5 MB. This has happened five times today.”

For more examples of polite phrasing, see our Tech Support Message Polite Requests section.

Mini Practice Section

Test your understanding with these four questions. Write your answer, then check the suggested answer below.

Question 1

You are writing an email to report that your printer prints blank pages. What is the best first sentence?

Suggested answer: “I am writing to report that my printer is printing blank pages.”

Question 2

You are in a live chat. Your internet disconnects every hour. How would you say it informally?

Suggested answer: “My internet keeps disconnecting every hour.”

Question 3

You see an error code “0x80070002” when installing an update. What should you include in your message?

Suggested answer: Include the error code: “When I try to install the update, I get error code 0x80070002.”

Question 4

Your problem is that the keyboard types wrong letters. What is a common mistake to avoid?

Suggested answer: Avoid saying “The keyboard is broken.” Instead say: “When I press the letter ‘a’, the letter ‘s’ appears.”

FAQ: Reporting Issues in Tech Support Messages

1. Should I include my operating system or device model?

Yes, if you know it. It helps the support team. For example: “I am using Windows 11 on a Dell XPS 13.”

2. What if I don’t know the exact error message?

Describe what you saw. For example: “A pop-up appeared with a red X, but I closed it too fast.” That is still useful.

3. How long should my problem explanation be?

Two to four sentences is usually enough. If the issue is complex, you can add a short list of steps you tried.

4. Can I report multiple issues in one message?

It is better to send separate messages for unrelated problems. If they are related, list them clearly: “I have two issues: first, the app crashes on startup. Second, the settings do not save.”

Final Tips

When you report an issue, remember these points:

• State the problem in the first sentence.
• Use past tense for what happened.
• Include error codes or messages if you have them.
• Do not blame or guess.
• Be polite, especially in formal messages.

For more practice with replies from support teams, check our Tech Support Message Practice Replies section.

If you have questions about this guide, please visit our FAQ page or contact us. We also recommend reading our Editorial Policy to understand how we create content.