How to Request More Details in an App Feedback Reply
When a user leaves feedback that is vague or incomplete, you need to ask for more details in a way that is clear, polite, and helpful. The goal is to get the information you need without making the user feel ignored or frustrated. This guide shows you exactly how to request more details in an app feedback reply, with ready-to-use phrases, tone advice, and common pitfalls to avoid.
Quick Answer: How to Request More Details
To request more details politely, start by thanking the user for their feedback, then explain why you need more information, and finally ask a specific question. Use phrases like "Could you tell us more about…" or "To help us understand better, could you share…" Keep your tone friendly and appreciative, not demanding.
Why Requesting More Details Matters
When a user writes "The app is slow" or "I don't like the update," you cannot fix the problem without specifics. Asking for details shows you care about their experience and want to solve the issue. It also helps you avoid making changes based on incomplete information. A polite request for more details can turn a frustrated user into a loyal one.
Formal vs. Informal Tone
Your choice of words depends on your app's brand voice and the context of the feedback. Here is a quick comparison:
| Context | Formal Example | Informal Example |
|---|---|---|
| Email reply | "We would appreciate it if you could provide additional details regarding the issue." | "Can you tell us a bit more about what happened?" |
| In-app chat | "Could you kindly elaborate on the steps you took before the error occurred?" | "What were you doing when the app crashed?" |
| Review response | "Thank you for your feedback. To assist you further, we would like to request more specifics." | "Thanks for letting us know! Could you share more details so we can help?" |
When to Use Formal Tone
Use formal language when replying to a complaint about a serious issue, such as a payment error or data loss. Formal tone shows respect and professionalism. It is also appropriate for email replies or when the user has used formal language themselves.
When to Use Informal Tone
Use informal language for minor issues, feature requests, or when the user's feedback is casual. Informal tone feels friendly and approachable, which can encourage users to share more. It works well in in-app chat or social media replies.
Natural Examples
Here are realistic examples of how to request more details in different situations.
Example 1: Vague Complaint About Speed
User feedback: "The app is too slow."
Your reply: "Thanks for your feedback. Could you tell us which part of the app feels slow? For example, is it the login screen, loading a page, or something else? Any details you share will help us improve."
Example 2: Unclear Bug Report
User feedback: "I got an error."
Your reply: "We're sorry to hear that. To help us fix this quickly, could you let us know what you were doing when the error appeared? Also, if you saw an error message, please share what it said."
Example 3: Feature Request Without Context
User feedback: "Add a dark mode."
Your reply: "Great suggestion! Could you tell us more about how you would use dark mode? For example, do you use the app mostly at night, or do you prefer dark themes in general? Your input will help us design it better."
Example 4: Negative Review With No Details
User feedback: "This update is terrible."
Your reply: "We're sorry the update didn't meet your expectations. Could you share what you liked about the previous version or what you find difficult now? Your feedback is very important to us."
Common Mistakes When Requesting More Details
Avoid these mistakes to keep your reply effective and polite.
Mistake 1: Asking Too Many Questions at Once
Wrong: "What device are you using? What version? What steps did you take? What error did you see?"
Why it's bad: The user may feel overwhelmed and ignore your request.
Better: "Could you start by telling us what device you are using? That will help us narrow down the issue."
Mistake 2: Sounding Demanding or Accusatory
Wrong: "You need to provide more details."
Why it's bad: It sounds rude and may make the user defensive.
Better: "We would love to hear more details so we can help you better."
Mistake 3: Not Explaining Why You Need the Information
Wrong: "Tell us more."
Why it's bad: The user may not see the value in responding.
Better: "To help us fix this issue as quickly as possible, could you share the steps you took before the error?"
Mistake 4: Using Vague Language
Wrong: "Can you give us some info?"
Why it's bad: The user does not know what info you need.
Better: "Could you tell us which screen you were on when the problem happened?"
Better Alternatives for Common Phrases
Here are some phrases you might be tempted to use and better alternatives that sound more natural and polite.
| Avoid This | Use This Instead |
|---|---|
| "Give me more details." | "Could you share more details?" |
| "I need to know…" | "It would help us to know…" |
| "What do you mean?" | "Could you explain what you mean by that?" |
| "Tell me exactly what happened." | "Could you walk us through what happened?" |
| "Send me a screenshot." | "If possible, a screenshot would be very helpful." |
Nuance in Requesting Details
The way you ask for details can change how the user feels about your request. Here are some nuances to consider.
Showing Appreciation First
Always start by thanking the user. This sets a positive tone and makes the user feel valued. For example: "Thank you for taking the time to share your thoughts."
Giving a Reason
Explain why you need the details. This helps the user understand that you are not just being nosy. For example: "To make sure we fix the right issue, could you tell us…"
Offering Options
Give the user choices to make it easier for them to respond. For example: "Was the problem on the home screen or in the settings menu?"
Being Patient
Do not pressure the user to respond immediately. Use phrases like "Whenever you have a moment" or "No rush."
Mini Practice Section
Test your understanding with these four questions. Each question presents a situation, and you need to choose the best reply.
Question 1
Situation: A user writes: "The app keeps crashing." What is the best reply?
A) "That's strange. Tell us more."
B) "We're sorry about that. Could you tell us what you were doing when it crashed?"
C) "You need to restart your phone."
Answer: B. This reply is polite, apologetic, and asks a specific question.
Question 2
Situation: A user writes: "I don't like the new design." What is the best reply?
A) "What don't you like about it?"
B) "Thanks for your feedback. Could you share what you preferred about the old design?"
C) "The new design is better."
Answer: B. This reply thanks the user and asks for specific, helpful information.
Question 3
Situation: A user writes: "I can't log in." What is the best reply?
A) "Did you forget your password?"
B) "We're sorry to hear that. Could you let us know what error message you see?"
C) "Try again later."
Answer: B. This reply is empathetic and asks for a specific detail that can help solve the problem.
Question 4
Situation: A user writes: "Add more filters." What is the best reply?
A) "We will add more filters soon."
B) "Great idea! Could you tell us what kind of filters you would find useful?"
C) "Filters are not a priority."
Answer: B. This reply is positive and asks for more details to guide development.
Frequently Asked Questions
1. What if the user does not respond to my request for details?
If the user does not respond, you can send a gentle follow-up after a few days. Keep it short and polite, like "Just checking in—did you have a chance to see our previous message? We're here to help." If they still do not reply, it is best to move on and use the information you have.
2. How many questions should I ask at once?
Ask only one or two specific questions at a time. Asking too many questions can overwhelm the user and reduce the chance of getting a reply. If you need more information, you can ask follow-up questions after the user responds.
3. Should I use emojis when requesting details?
Emojis can make your reply feel friendlier, but use them carefully. A simple smiley face or thumbs up is usually safe. Avoid emojis that might seem unprofessional, like laughing faces, especially if the user is reporting a problem.
4. What if the user's feedback is very negative or angry?
Stay calm and professional. Acknowledge their frustration first, then politely ask for details. For example: "We understand your frustration and apologize for the inconvenience. To help us resolve this, could you share more about what happened?" Never argue with the user or dismiss their feelings.
Putting It All Together
Requesting more details in an app feedback reply is a skill that improves with practice. Always start with a thank you, explain why you need the information, and ask a specific question. Choose your tone based on the context, and avoid common mistakes like asking too many questions or sounding demanding. With the phrases and examples in this guide, you can turn vague feedback into actionable insights that help you improve your app and build stronger relationships with your users.
For more help with polite replies, visit our App Feedback Reply Polite Requests section. You can also explore App Feedback Reply Starters for opening phrases, or check our FAQ for common questions about replying to feedback.
