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

When you send feedback about an app, you may need to say that you do not understand a feature, an error message, or an instruction. The direct way to say this is to state clearly that something is unclear, but the best choice depends on your tone and the situation. For example, you can say “I do not understand this error” for a direct report, or “Could you clarify what this means?” for a polite request. This guide will help you choose the right wording for your app feedback messages, whether you are writing a bug report, a feature request, or a general comment.

Quick Answer: Best Phrases for Saying You Do Not Understand

If you need a fast answer, here are the most useful phrases for app feedback messages. Use the first two for polite situations and the last two for direct reports.

• Polite and clear: “Could you please clarify what this message means?”
• Formal and respectful: “I am unable to understand the instructions provided.”
• Direct and simple: “I do not understand this error.”
• Problem-focused: “The explanation is unclear to me.”

These phrases work well in most app feedback contexts. Choose the one that matches your relationship with the app team and the seriousness of the issue.

Understanding the Context: Formal vs. Informal Tone

App feedback messages can range from casual comments to formal bug reports. The way you say you do not understand should match the tone of the app and your reason for writing. Here is a breakdown of the main contexts.

Formal Tone (For Official Bug Reports or Support Tickets)

Use formal language when you are reporting a problem to a professional support team. This tone shows respect and helps the team take your feedback seriously. Formal phrases often include words like “unable,” “clarify,” or “explain.”

Example: “I am unable to understand the error code that appears after I press the submit button. Could you please explain what it means?”

Informal Tone (For In-App Feedback or Community Forums)

If you are writing a quick comment inside the app or on a community board, an informal tone is fine. Use simple words and shorter sentences. This feels natural and friendly.

Example: “I don’t get what this message says. Can you help?”

Conversation vs. Written Feedback

In a live chat or conversation, you can use shorter phrases like “I’m lost” or “That’s not clear.” In written feedback, such as an email or a form, you need to be more specific so the team can understand your issue.

Comparison Table: Phrases for Different Situations

Natural Examples for App Feedback Messages

Here are realistic examples that show how to say you do not understand in different app feedback situations. Each example includes a brief explanation of why it works.

Example 1: Bug Report (Direct)

Feedback: “I do not understand the error message that says ‘Invalid input format.’ What does this mean?”
Why it works: This is clear and specific. The user names the error message and asks for an explanation. The team can quickly identify the issue.

Example 2: Feature Request (Polite)

Feedback: “Could you please clarify how the new search filter works? I am not sure what it does.”
Why it works: The user uses polite language (“could you please”) and states the specific feature. This encourages a helpful response.

Example 3: General Feedback (Neutral)

Feedback: “The instructions for setting up my profile are unclear to me. I cannot find the next step.”
Why it works: The user explains the problem without blaming anyone. The team can improve the instructions based on this feedback.

Example 4: Support Ticket (Formal)

Feedback: “I am unable to understand the steps listed in the troubleshooting guide. Could you provide a simpler explanation?”
Why it works: This is respectful and professional. The user acknowledges the guide but asks for help, which is appropriate for a support ticket.

Common Mistakes When Saying You Do Not Understand

English learners often make small errors that can confuse the reader. Here are the most common mistakes and how to fix them.

Mistake 1: Using “I don’t understand” without context

Wrong: “I don’t understand.”
Why it is a problem: The team does not know what you do not understand. This is too vague.
Better: “I don’t understand the error message that appears after I log in.”

Mistake 2: Mixing formal and informal words

Wrong: “I am unable to get what this means.”
Why it is a problem: “Unable” is formal, but “get” is informal. This sounds awkward.
Better: “I am unable to understand what this means.” (formal) or “I don’t get what this means.” (informal)

Mistake 3: Using “confusing” as a personal feeling

Wrong: “I am confusing about this feature.”
Why it is a problem: “Confusing” describes the thing, not the person. The correct word is “confused.”
Better: “I am confused about this feature.”

Mistake 4: Being too aggressive

Wrong: “This is stupid. I don’t understand it.”
Why it is a problem: This sounds rude and may not get a helpful response.
Better: “This is unclear to me. Could you explain it differently?”

Better Alternatives for Common Phrases

Sometimes the first phrase you think of is not the best choice. Here are better alternatives for common situations.

Instead of “I don’t understand”

• Better alternative: “This is unclear to me.” – This sounds more neutral and professional.
• When to use it: Use this in written feedback when you want to point out a problem without sounding frustrated.

Instead of “What does this mean?”

• Better alternative: “Could you clarify the meaning of this message?” – This is more polite and specific.
• When to use it: Use this in a support ticket or formal email.

Instead of “I’m lost”

• Better alternative: “I am not following the instructions.” – This is clearer and more appropriate for written feedback.
• When to use it: Use this when you are describing a step-by-step process that confuses you.

Instead of “Can you help?”

• Better alternative: “Could you please provide more details about this feature?” – This is more specific and shows what kind of help you need.
• When to use it: Use this when you need additional information, not just general assistance.

Mini Practice Section: Test Your Understanding

Try these four practice questions. Each question gives a situation, and you need to choose the best phrase. Answers are below.

Question 1

You are writing a bug report about an error message that says “Connection failed.” What is the best way to say you do not understand?

A) “I don’t get this.”
B) “I do not understand the ‘Connection failed’ error. What does it mean?”
C) “This is confusing.”

Question 2

You are sending a polite request to the support team about a feature. Which phrase is best?

A) “Could you please clarify how the new update works?”
B) “I don’t know what this does.”
C) “Explain this to me.”

Question 3

You are giving general feedback about unclear instructions. What should you write?

A) “The instructions are unclear to me. I cannot find the next step.”
B) “I am confused.”
C) “This is bad.”

Question 4

You are in a live chat with support and need a quick answer. What is the best informal phrase?

A) “I am unable to understand this.”
B) “I don’t get what this means. Can you help?”
C) “Could you please provide clarification?”

Answers

Answer 1: B. This is specific and direct. It names the error and asks for an explanation.
Answer 2: A. This is polite and specific. It uses “could you please” and names the feature.
Answer 3: A. This explains the problem clearly. It says the instructions are unclear and gives a reason.
Answer 4: B. This is informal and natural for a live chat. It uses “I don’t get” and asks for help.

Frequently Asked Questions (FAQ)

1. Can I say “I am confused” in an app feedback message?

Yes, you can say “I am confused,” but it is better to add context. For example, “I am confused about the login process” is more helpful than just “I am confused.” This helps the team understand your specific problem.

2. What is the most polite way to say I do not understand?

The most polite way is to use “could you please” and a specific request. For example, “Could you please clarify the steps for resetting my password?” This shows respect and makes it easy for the team to help you.

3. Should I use formal or informal language in app feedback?

It depends on the app and the situation. For official bug reports or support tickets, use formal language. For casual feedback or community forums, informal language is fine. When in doubt, use polite and clear language that is not too casual.

4. How can I avoid sounding rude when I say I do not understand?

Avoid blaming the app or the team. Instead of saying “This is poorly explained,” say “This is unclear to me.” Use polite words like “please” and “could.” Focus on your own confusion rather than criticizing the app.

Final Tips for Writing App Feedback Messages

When you need to say you do not understand in an app feedback message, remember these key points. First, always add context. Tell the team what specific part you do not understand. Second, choose the right tone. Use formal language for support tickets and informal language for quick comments. Third, avoid common mistakes like using “confusing” instead of “confused” or being too vague. Finally, practice using the phrases from this guide in your own feedback. For more help, explore our App Feedback Message Starters and App Feedback Message Polite Requests sections. If you have questions, visit our FAQ or contact us for support.