What Not to Say at the Start of an App Feedback Conversation

Starting an app feedback conversation the wrong way can make the other person defensive, confused, or less willing to help. The most common problem is using language that sounds like an attack, a demand, or a vague complaint. This guide shows you exactly which phrases to avoid and what to say instead, so your feedback is heard and taken seriously.

Quick Answer: The Three Worst Openers

If you want your app feedback to be effective, never start with these three types of phrases:

• Accusations: “You always make this bug happen.”
• Vague complaints: “This app is terrible.”
• Demands without context: “Fix this now.”

Instead, start with a neutral observation, a polite request, or a specific description of what you experienced. The rest of this article explains why these openers fail and gives you better alternatives.

Why Your Opening Words Matter

The first sentence of an app feedback conversation sets the tone for everything that follows. If you start with blame or frustration, the person on the other side will likely become defensive. If you start with a vague statement, they won’t know what you actually need. Good openers are specific, neutral, and focused on the problem, not the person.

Phrases to Avoid and What to Use Instead

1. “You always…” or “You never…”

These are absolute statements that rarely reflect reality. They sound like accusations and put the listener on the defensive immediately.

Why it fails: It blames the person rather than describing the issue. It also exaggerates, which makes your feedback less credible.

Better alternatives:

• “I noticed that the app crashes when I try to upload a photo.”
• “The login screen sometimes freezes after I enter my password.”

When to use it: Never. Replace absolute statements with specific observations.

2. “This app is broken.”

This is too vague. The other person has no idea what part of the app is broken or what you were doing when it happened.

Why it fails: It gives no useful information. The person receiving the feedback has to ask multiple follow-up questions just to understand the problem.

Better alternatives:

• “The search function isn’t showing results for any keywords I type.”
• “The payment page shows an error message after I confirm my card details.”

When to use it: Only if you are speaking to a close friend who already knows the context. In any formal or customer support setting, be specific.

3. “Fix this immediately.”

This is a demand, not a request. It sounds rude and impatient, even if you are frustrated.

Why it fails: It creates tension and makes the other person less willing to help. It also assumes they know exactly what “this” refers to.

Better alternatives:

• “Could you please look into the issue with the notification sound not working?”
• “I’m having trouble with the calendar sync. Can you help me fix it?”

When to use it: Only in an emergency situation where you have already explained the problem and the person is ignoring it. Even then, a polite request works better.

4. “I hate this feature.”

Strong emotional language like “hate” makes the conversation personal. It focuses on your feelings rather than the actual problem.

Why it fails: It can make the other person feel attacked or defensive. It also doesn’t explain what specifically you dislike.

Better alternatives:

• “The new layout makes it hard to find the settings menu.”
• “I find the color scheme difficult to read in bright sunlight.”

When to use it: Avoid in professional feedback. If you are talking to a friend, you can use casual language, but still try to explain why.

5. “Why did you do this?”

This question sounds like an interrogation. It puts the other person in a position where they have to justify their decisions.

Why it fails: It shifts the focus from solving the problem to defending past choices. This rarely leads to a productive conversation.

Better alternatives:

• “Can you explain the reason for the recent change to the home screen?”
• “I’m curious about the new update. What was the goal behind it?”

When to use it: Only if you are genuinely asking for information in a neutral tone. Avoid using it as a complaint.

Comparison Table: Bad Openers vs. Good Openers

Natural Examples of Good Openers

Here are realistic examples of how to start an app feedback conversation in different situations.

Email to customer support

“Hello, I’m writing about an issue with the app’s reminder feature. When I set a reminder for 3 PM, it doesn’t notify me until 4 PM. Could you help me fix this?”

In-app chat with support

“Hi, I’m having trouble with the payment screen. It says ‘transaction failed’ but the money was taken from my account. Can you check?”

Feedback form

“I suggest adding a dark mode option. The current white background is hard on my eyes when I use the app at night.”

Conversation with a developer friend

“Hey, I found something weird. When I tap the profile icon, the app freezes for a few seconds. Have you seen this before?”

Common Mistakes Learners Make

Even advanced English learners sometimes use the wrong opener. Here are the most frequent mistakes.

Mistake 1: Using “you” too much

Starting every sentence with “you” sounds like blame. Instead, use “I” or “the app” to describe the problem.

Wrong: “You made the app slow.”
Right: “The app has been running slowly since the last update.”

Mistake 2: Being too indirect

Some learners are so polite that the problem is unclear. Being polite is good, but you still need to be specific.

Wrong: “I was wondering if maybe there is a small thing about the button…”
Right: “The ‘save’ button doesn’t respond when I click it.”

Mistake 3: Mixing formal and informal tone

If you start with “Hey, what’s up?” and then switch to “I respectfully request,” it sounds unnatural. Choose one tone and stick with it.

Wrong: “Hey dude, I would like to formally report a bug.”
Right (informal): “Hey, I found a bug in the chat feature.”
Right (formal): “Hello, I would like to report a bug in the chat feature.”

Mistake 4: Forgetting to mention what you were doing

Without context, the other person cannot reproduce the problem. Always say what action you were taking.

Wrong: “The app crashed.”
Right: “The app crashed while I was trying to upload a video from my gallery.”

Better Alternatives for Common Situations

Here are specific replacements for common bad openers, organized by context.

When you are frustrated

Bad: “This is so annoying.”
Better: “I’m having a frustrating experience with the login process. It keeps saying ‘invalid password’ even though I just reset it.”

When you want a new feature

Bad: “Add this feature now.”
Better: “Would it be possible to add a search filter by date? It would make finding old conversations much easier.”

When you disagree with a change

Bad: “The new update is stupid.”
Better: “I preferred the old layout because the buttons were easier to reach. Is there a way to switch back?”

When you are not sure if it’s a bug

Bad: “Something is wrong.”
Better: “I’m not sure if this is a bug or intended behavior, but when I swipe left on a message, nothing happens.”

Mini Practice Section

Test your understanding. Choose the best opener for each situation.

Question 1: You want to report that the app’s map feature shows the wrong location.

A) “Your map is broken.”
B) “The map shows my location as downtown, but I am actually at the airport.”
C) “Fix the map.”

Answer: B. It is specific and neutral.

Question 2: You are emailing support about a payment that was charged twice.

A) “You charged me twice. Give my money back.”
B) “I was charged twice for my subscription on March 5th. Can you help me get a refund?”
C) “This is a scam.”

Answer: B. It states the facts and makes a polite request.

Question 3: You want to suggest a new feature to a developer friend.

A) “Your app is missing a dark mode.”
B) “Why didn’t you add dark mode?”
C) “Hey, have you thought about adding a dark mode? I think it would be useful for night use.”

Answer: C. It is friendly and suggests an idea without blame.

Question 4: You are filling out a feedback form about a confusing menu.

A) “The menu is bad.”
B) “I find the menu confusing because the settings are under the ‘profile’ tab instead of a separate menu.”
C) “Who designed this?”

Answer: B. It explains the problem clearly.

FAQ: Starting an App Feedback Conversation

1. Should I always start with “Hello” or “Hi”?

Yes, in most formal or semi-formal situations. A greeting shows respect and sets a polite tone. In very casual conversations with friends, you can skip it, but it is safer to include a greeting when you are not sure.

2. Is it okay to start with “I have a problem”?

It is acceptable, but it is better to be more specific. “I have a problem with the notification settings” is much more helpful than just “I have a problem.”

3. What if I am very angry about a bug?

Take a moment to calm down before writing. Angry openers rarely get good results. Write your feedback, then read it again before sending. If it sounds angry, rewrite it in a neutral tone. You can still express frustration without being rude.

4. Can I use emojis at the start of feedback?

In casual conversations, a simple emoji like 😊 can soften your tone. In formal emails or support tickets, avoid emojis. They can make you seem less serious about the issue.

Final Advice

The best way to start an app feedback conversation is to be specific, neutral, and polite. Describe what happened, what you were doing, and what you expected to happen. Avoid blame, vague statements, and demands. Practice using the good alternatives in this guide, and you will get better results every time. For more help with polite requests, visit our App Feedback Conversation Polite Requests section. If you need to explain a problem in detail, check out App Feedback Conversation Problem Explanations. For practice replies, see App Feedback Conversation Practice Replies. And if you have general questions, our FAQ page may have the answer.