How to Say You Do Not Understand in an App Feedback Conversation

When you are testing an app or reporting a problem, you will sometimes need to say that you do not understand a feature, an instruction, or a reply from the support team. In an app feedback conversation, saying “I don’t understand” directly can feel too blunt or even rude, especially if you are writing to a developer or a customer service representative. The key is to choose a phrase that matches the situation—whether you are in a quick chat, a formal email, or a polite request for clarification. This guide gives you clear, ready-to-use phrases, explains when to use each one, and helps you avoid common mistakes that can confuse the other person.

Quick Answer: What to Say When You Do Not Understand

If you need a fast, polite way to say you do not understand in an app feedback conversation, use one of these three phrases depending on the tone:

• Formal (email or support ticket): “I’m afraid I don’t quite follow your explanation. Could you clarify that point?”
• Neutral (chat or feedback form): “I’m not sure I understand how this feature works. Can you explain it differently?”
• Informal (quick message to a teammate): “Sorry, I didn’t get that. Can you say it again?”

These phrases are direct, polite, and natural for English learners to use in real app feedback situations.

Understanding the Context: Formal vs. Informal

The way you say you do not understand depends on who you are talking to and the channel you are using. In app feedback conversations, you might be writing to a developer, a product manager, or a support agent. Each situation calls for a different level of politeness and clarity.

Formal Situations (Email, Support Tickets, Official Feedback)

When you are writing a formal message, you want to show respect and avoid sounding frustrated. Use longer, softer phrases that give the other person room to explain again.

• “I’m afraid I don’t quite understand the steps you mentioned. Could you please elaborate?” – This is polite and shows you are trying to follow along.
• “I’m having trouble grasping the logic behind this setting. Would you mind clarifying?” – This works well when you are confused about a feature’s purpose.
• “Could you rephrase that? I want to make sure I’m not missing anything.” – This is a gentle way to ask for a simpler explanation.

Informal Situations (Chat, Quick Messages, Team Conversations)

In casual chats, you can be more direct, but still polite. Short phrases are fine, but avoid sounding annoyed.

• “Sorry, I didn’t catch that. Can you repeat it?” – Natural and friendly.
• “I’m lost. Can you walk me through it again?” – Honest and easy to understand.
• “Not sure I follow. What do you mean by ‘sync’ here?” – Specific and helpful for the other person.

Comparison Table: Phrases for Different Situations

Natural Examples in App Feedback Conversations

Here are realistic examples that show how to use these phrases in actual app feedback situations. Each example includes the context and the tone.

Example 1: Email to Support About a Login Issue

Context: You received a reply from support about resetting your password, but the instructions are unclear.

Your message: “Thank you for your response. I’m afraid I don’t quite follow the part about the verification code. You mentioned it will be sent to my email, but I didn’t receive anything. Could you clarify where the code should appear?”

Tone: Formal and polite. You are not blaming anyone; you are asking for help.

Example 2: Chat with a Developer About a New Feature

Context: The developer explains a new sorting option, but you are not sure how to use it.

Your message: “Sorry, I didn’t get that. When you say ‘long press the list,’ do you mean hold it for two seconds or just tap and hold?”

Tone: Informal and direct. You are asking for a specific detail.

Example 3: Feedback Form About a Confusing Error Message

Context: The app shows an error that says “Session expired,” but you don’t know what that means.

Your message: “I’m not sure I understand the error message. It says ‘Session expired,’ but I was still using the app. Could you explain what causes this and how to fix it?”

Tone: Neutral and clear. You are reporting a problem and asking for clarification.

Common Mistakes When Saying You Do Not Understand

English learners often make these mistakes in app feedback conversations. Avoid them to sound more natural and polite.

Mistake 1: Using “I don’t understand” Too Directly

Wrong: “I don’t understand your instructions.”
Why it’s a problem: This can sound blunt or even rude, especially in formal writing. It puts the blame on the other person.
Better alternative: “I’m having trouble following your instructions. Could you explain them differently?”

Mistake 2: Saying “What?” or “Huh?”

Wrong: “What? I don’t get it.”
Why it’s a problem: These words are too casual and can sound impatient or disrespectful in a professional conversation.
Better alternative: “Sorry, I didn’t catch that. Can you repeat it?”

Mistake 3: Using “I’m confused” Without Context

Wrong: “I’m confused.”
Why it’s a problem: It is vague. The other person does not know what part you are confused about.
Better alternative: “I’m confused about the part where you said to enable notifications. Which settings menu should I open?”

Mistake 4: Apologizing Too Much

Wrong: “I’m so sorry, I’m really sorry, but I don’t understand. I’m sorry for bothering you.”
Why it’s a problem: Too many apologies make you sound unsure of yourself and can annoy the reader.
Better alternative: “Thank you for your help. I just need a little more clarification on the last step.”

Better Alternatives for Common Phrases

Here are simple swaps you can make to sound more professional and clear in your app feedback conversations.

• Instead of: “I don’t get it.” → Use: “I’m not sure I follow.”
• Instead of: “Can you explain again?” → Use: “Could you walk me through that one more time?”
• Instead of: “This is confusing.” → Use: “This part is a bit unclear to me.”
• Instead of: “I don’t know what you mean.” → Use: “I’m not sure I understand what you mean by that.”

Mini Practice: 4 Questions and Answers

Test yourself with these short practice questions. Each one gives a situation, and you need to choose the best response. Answers are below.

Question 1

Situation: You are in a chat with a developer. They say, “Just toggle the switch in the advanced settings.” You don’t know where that is. What do you say?

A. “What? I don’t see it.”
B. “Sorry, I’m not sure where the advanced settings are. Can you point me to the menu?”
C. “I don’t understand your instructions.”

Answer: B. It is polite, specific, and asks for help without sounding rude.

Question 2

Situation: You are writing a support email. The agent used a term you don’t know: “cache.” What do you write?

A. “What is cache?”
B. “I’m not familiar with the term ‘cache.’ Could you explain what it means in this context?”
C. “I don’t get it.”

Answer: B. It is formal and shows you want to learn.

Question 3

Situation: A teammate in a group chat says, “Just sync the data first.” You missed the earlier message. What do you say?

A. “Sorry, I missed the earlier message. Can you repeat the sync step?”
B. “Huh?”
C. “I’m confused.”

Answer: A. It is polite and gives context about why you didn’t understand.

Question 4

Situation: You are testing a new feature and the instructions say “swipe left.” You tried it but nothing happened. What do you say in the feedback form?

A. “It doesn’t work.”
B. “I’m not sure I’m swiping correctly. When I swipe left, nothing changes. Is there a specific area I should swipe on?”
C. “This is broken.”

Answer: B. It explains what you did and asks for a specific clarification.

FAQ: Saying You Do Not Understand in App Feedback

Q1: Is it okay to say “I don’t understand” in a formal email?

It is better to use a softer phrase like “I’m afraid I don’t quite follow” or “I’m having trouble understanding.” These sound more polite and professional. Direct “I don’t understand” can feel too blunt in formal writing.

Q2: How can I ask for clarification without sounding rude?

Use phrases that include “could you” or “would you mind.” For example, “Could you clarify that point?” or “Would you mind explaining that again?” These show respect and give the other person a chance to help you.

Q3: What if I still don’t understand after the second explanation?

It is fine to say, “Thank you for explaining again. I think I’m still missing something. Could you show me with a screenshot or a short video?” This is honest and asks for a different type of help.

Q4: Should I apologize when I don’t understand?

A single “sorry” or “I apologize” is fine, but do not overdo it. One polite apology is enough. Then move on to your question. Too many apologies can make the conversation awkward.

Final Tips for App Feedback Conversations

When you need to say you do not understand, remember these three points:

• Be specific. Tell the person exactly what part you are confused about. This helps them give you a useful answer.
• Match the tone. Use formal phrases for emails and support tickets, and informal phrases for chats with teammates.
• Stay polite. Even if you are frustrated, keep your language calm and respectful. This makes the conversation productive.

For more help with polite requests in app feedback, visit our App Feedback Conversation Polite Requests section. If you need practice replies, check out App Feedback Conversation Practice Replies. You can also learn how to start a feedback conversation in our App Feedback Conversation Starters guide. For any questions about this guide, see our FAQ or contact us.