How to Say You Do Not Understand in a Tech Support Reply
When you are working in tech support, you will often need to tell a customer that you do not understand what they mean. This is a normal part of the job. The key is to say it clearly and politely so the customer does not feel frustrated. This guide will show you exactly how to say you do not understand in a tech support reply, with direct phrases, tone advice, and common mistakes to avoid.
Quick Answer: The Best Phrases to Use
If you need to say you do not understand right now, use one of these simple and professional phrases:
- “I am not sure I follow. Could you explain that again?” – Polite and clear for email or chat.
- “I do not quite understand the issue. Can you describe it differently?” – Good for phone or live chat.
- “Could you clarify what you mean by [specific term]?” – Direct and helpful for technical terms.
- “I am having trouble understanding the problem. Can you give me an example?” – Works well when the customer uses vague language.
These phrases are safe, polite, and work in most tech support situations. They show you are trying to help, not just giving up.
Why Saying “I Do Not Understand” Is Hard for Learners
Many English learners feel embarrassed when they do not understand a customer. They worry that saying “I don’t understand” sounds unprofessional or rude. In reality, the opposite is true. Customers prefer an honest reply over a wrong answer or silence. The trick is to use the right tone and words.
In tech support, you are expected to solve problems. If you do not understand the problem, you cannot solve it. So admitting you need more information is a sign of good service, not weakness. This guide will help you choose the right phrase for email, chat, and phone conversations.
Formal vs. Informal Ways to Say You Do Not Understand
The tone you use depends on your company’s style and the customer’s mood. Below is a comparison table to help you choose.
| Situation | Formal (Email / Escalated Ticket) | Informal (Chat / Friendly Phone Call) |
|---|---|---|
| You did not hear or read clearly | “I apologize, but I did not catch that. Could you please repeat it?” | “Sorry, I missed that. Can you say it again?” |
| The customer used a technical term you do not know | “I am unfamiliar with that term. Could you provide a brief explanation?” | “I don’t know that term. What does it mean?” |
| The customer explained something confusing | “I am having difficulty understanding the situation. Would you mind rephrasing it?” | “I’m a bit lost. Can you explain it in a different way?” |
| You need more details | “To ensure I understand correctly, could you elaborate on that point?” | “Can you tell me more about that?” |
Use the formal column for written replies or when the customer is upset. Use the informal column for quick chats or when the customer is friendly.
Natural Examples for Real Tech Support Conversations
Here are realistic examples you can adapt for your own replies. Each example shows a different situation.
Example 1: Email Reply – Customer Uses a Vague Error Message
Customer wrote: “My computer shows an error when I try to open the program.”
Your reply: “Thank you for reaching out. I am not sure I understand the error you are seeing. Could you please tell me the exact text that appears on the screen? That will help me find the right solution.”
Tone note: This is polite and specific. You are not blaming the customer. You are asking for the missing information.
Example 2: Live Chat – Customer Uses a Slang Term
Customer: “My app keeps crashing when I try to log in. It’s totally bricked.”
Your reply: “I understand the app is not working. I am not familiar with the term ‘bricked’ in this context. Do you mean the app freezes completely and you cannot close it?”
Tone note: You admit you do not know the slang, but you offer a guess. This keeps the conversation moving.
Example 3: Phone Call – Customer Speaks Too Fast
Customer: “Yeah, so I went to settings, then advanced, then network, and I changed the DNS to 8.8.8.8, but now nothing works.”
Your reply: “I am sorry, I did not catch all of that. Could you please slow down and tell me the first step again?”
Tone note: It is okay to ask someone to slow down. Most customers will understand.
Common Mistakes When Saying You Do Not Understand
Even advanced learners make these errors. Avoid them to sound more professional.
Mistake 1: Using “I don’t understand” Without a Follow-Up
Bad: “I don’t understand.” (This sounds like you are giving up.)
Better: “I don’t understand the problem. Can you describe it in a different way?” (This shows you want to help.)
Mistake 2: Blaming the Customer
Bad: “You are not explaining this clearly.” (This is rude and will make the customer angry.)
Better: “I want to make sure I understand. Could you explain it again?” (This takes responsibility for understanding.)
Mistake 3: Pretending You Understand
Bad: “Okay, I will check that.” (Then you do nothing because you have no idea what to check.)
Better: “I need a moment to look into this. Can you hold on?” (Honesty is better than a wrong action.)
Mistake 4: Using Only “What?” or “Huh?”
Bad: “What?” (Too informal and can sound rude in writing.)
Better: “Sorry, could you repeat that?” (Polite and clear.)
Better Alternatives for Common Situations
Sometimes you need a more specific phrase. Here are better alternatives for common tech support moments.
When You Do Not Understand a Technical Term
- Instead of: “What is that?”
- Use: “I am not familiar with that term. Could you explain what it means in this context?”
When the Customer Gives Too Much Information at Once
- Instead of: “I am confused.”
- Use: “That is a lot of information. Let me break it down. First, did you restart the computer?”
When You Need the Customer to Rephrase
- Instead of: “I don’t get it.”
- Use: “I think I am missing something. Can you explain it in a different way?”
When to Use Each Phrase
Choosing the right phrase depends on the channel and the customer’s tone. Here is a quick guide.
- Email: Use formal phrases. You have time to write carefully. Example: “I would appreciate it if you could clarify the error code.”
- Live chat: Use semi-formal or informal phrases. Speed matters. Example: “I’m not sure I follow. Can you give me the error message?”
- Phone: Use polite, short phrases. The customer cannot see your face. Example: “Could you say that again, please?”
Mini Practice: 4 Questions and Answers
Test yourself. Read the customer message and choose the best reply. Then check the answer.
Question 1
Customer: “My printer is doing that thing again where it makes a weird noise and then stops.”
Your reply options:
- “I don’t understand. What thing?”
- “I am not sure what you mean by ‘that thing.’ Can you describe the noise or the error message on the screen?”
- “Okay, I will send a technician.”
Answer: Option 2 is best. It politely asks for more specific information without blaming the customer.
Question 2
Customer: “I followed your steps, but it still doesn’t work. You are not helping.”
Your reply options:
- “You are wrong. I gave you the right steps.”
- “I am sorry it is not working. I want to understand exactly what happened. Can you tell me the last step you completed?”
- “I don’t know what to tell you.”
Answer: Option 2 is best. It apologizes, shows you care, and asks for specific information to understand the problem.
Question 3
Customer: “The software crashed after I updated the driver. I think it’s a conflict with the kernel.”
Your reply options:
- “What is a kernel?”
- “I am not an expert on kernels. Could you explain what you mean by ‘conflict with the kernel’?”
- “That is not possible.”
Answer: Option 2 is best. It honestly admits you need more information without sounding unprofessional.
Question 4
Customer: “So, like, I clicked on the thing, and then the other thing happened, and now it’s all messed up.”
Your reply options:
- “I have no idea what you are talking about.”
- “I want to help, but I need more details. What did you click on first? Was it a button or a link?”
- “Just restart your computer.”
Answer: Option 2 is best. It guides the customer to give useful information without sounding frustrated.
Frequently Asked Questions (FAQ)
1. Is it okay to say “I don’t understand” in a tech support email?
Yes, but always add a polite request for more information. For example, “I don’t understand the error. Could you send a screenshot?” This shows you are still trying to help.
2. What if the customer gets angry when I say I do not understand?
Stay calm. Apologize briefly and ask a specific question. For example, “I am sorry for the confusion. To help you faster, could you tell me the exact error message?” This often calms the customer down.
3. How do I say I do not understand without sounding stupid?
Use phrases that put the responsibility on the situation, not on you. For example, “This issue is a bit complex. Let me make sure I have the details right.” This sounds professional, not ignorant.
4. Can I use these phrases for phone support?
Yes. For phone support, keep your phrases short and clear. For example, “Could you repeat that?” or “I missed the last part. Can you say it again?” Your tone of voice is also important. Speak calmly and politely.
Final Tips for Tech Support Replies
Remember these three rules when you need to say you do not understand:
- Be honest. Pretending you understand leads to mistakes and longer wait times.
- Be polite. Use “could you,” “would you mind,” or “I would appreciate it.”
- Be specific. Tell the customer exactly what you need. For example, “Can you tell me the error code?” is better than “Can you explain more?”
For more help with the right words, check our Tech Support Reply Starters for opening phrases, or visit Tech Support Reply Polite Requests for polite ways to ask for information. If you want to practice, our Tech Support Reply Practice Replies section has exercises. For any questions about this guide, see our FAQ or contact us.
