How to Request More Details in an App Feedback Conversation

When you receive feedback about an app, you often need more information to understand the issue fully. This article shows you how to ask for those extra details politely and effectively in English, whether you are writing an email, chatting in a support ticket, or speaking on a call. You will learn the exact phrases to use, when to use them, and how to avoid common mistakes that can confuse the person giving feedback.

Quick Answer: How to Ask for More Details

To request more details in an app feedback conversation, use polite, open-ended questions that show you value the user’s input. Start with phrases like “Could you please tell me more about…?” or “Would you mind describing…?”. Avoid demanding words like “need” or “must”. Keep your tone friendly and curious, not defensive. The goal is to get clear information without making the user feel questioned or blamed.

Understanding the Context: Formal vs. Informal

How you ask for more details depends on the situation. In a formal email or a support ticket, use complete sentences and polite modals. In a quick chat or a casual conversation, you can be shorter but still respectful. Below is a comparison table to help you choose the right approach.

Key Phrases for Requesting More Details

Here are the most useful phrases, organized by how polite and direct they are. Use them as templates and fill in your own situation.

Polite and Indirect (Best for formal emails and sensitive feedback)

• “Could you please elaborate on…?” – Use this when you need a fuller explanation. Example: “Could you please elaborate on the steps that led to the crash?”
• “Would you mind providing more context about…?” – This is very polite and works well for vague feedback. Example: “Would you mind providing more context about the ‘slow loading’ you mentioned?”
• “I would appreciate it if you could share…” – A warm, respectful way to ask. Example: “I would appreciate it if you could share the exact error message you saw.”

Neutral and Clear (Good for most support conversations)

• “Could you tell me more about…?” – Simple and effective. Example: “Could you tell me more about what you expected to happen?”
• “What did you do just before…?” – Direct but not rude. Example: “What did you do just before the app closed unexpectedly?”
• “Can you describe…?” – A straightforward request. Example: “Can you describe the screen you saw after the update?”

Informal and Friendly (Best for chat or known users)

• “Can you give me a bit more detail on…?” – Casual but still polite. Example: “Can you give me a bit more detail on what wasn’t working?”
• “What happened exactly?” – Short and direct. Use this only after a friendly greeting. Example: “Hey, thanks for the report. What happened exactly?”
• “Mind telling me more about…?” – Very casual. Example: “Mind telling me more about the button you pressed?”

Natural Examples in Real Conversations

Seeing these phrases in action helps you understand the nuance. Below are three realistic scenarios.

Scenario 1: Email Follow-Up After a Bug Report

User feedback: “The app keeps crashing when I try to upload a photo.”
Your reply: “Thank you for letting us know. Could you please tell me more about the type of photo you were uploading? Also, would you mind describing the exact step where the crash happened? This will help us fix it faster.”

Why it works: You thank the user first, then ask two specific, polite questions. You explain why you need the details, which encourages cooperation.

Scenario 2: Live Chat During a Feature Request

User: “I wish the search function was better.”
You: “Thanks for the suggestion! Can you give me a bit more detail on what you’d like to see improved? For example, are you looking for faster results or more filters?”

Why it works: You acknowledge the feedback, then ask a friendly, open-ended question with a concrete example to guide the user.

Scenario 3: Phone Call About a Payment Issue

User: “I couldn’t complete my purchase.”
You: “I’m sorry to hear that. Would you mind walking me through what you saw on the screen? Did you see any error message?”

Why it works: You show empathy first, then use a polite request (“Would you mind…”) and a specific follow-up question to get useful details.

Common Mistakes and How to Avoid Them

Even advanced learners make these errors. Here are the most frequent ones when requesting more details.

Mistake 1: Using Demanding Language

Wrong: “I need you to tell me exactly what happened.”
Better: “Could you please tell me exactly what happened?”
Why: “I need” sounds like an order. “Could you please” turns it into a polite request.

Mistake 2: Asking Too Many Questions at Once

Wrong: “What device were you using? What time did it happen? What error did you see? Did you restart the app?”
Better: “Thank you for the report. Could you start by telling me what device you were using? Then we can go step by step.”
Why: A list of questions feels overwhelming. Break them into a conversation.

Mistake 3: Being Vague

Wrong: “Tell me more.”
Better: “Could you tell me more about what you saw on the screen?”
Why: “Tell me more” is too open. The user may not know what to say. A specific direction helps them give useful information.

Mistake 4: Forgetting to Thank the User First

Wrong: “What happened?” (as the first message)
Better: “Thanks for reaching out. What happened?”
Why: Starting with a thank-you shows appreciation and builds a positive tone.

Better Alternatives for Common Situations

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

When the user’s feedback is very short (e.g., “It doesn’t work”)

• Instead of: “What doesn’t work?”
• Use: “Could you describe what you were trying to do when it didn’t work?”
• Why: The user may not know how to explain. Guiding them to describe their action helps.

When the user seems frustrated

• Instead of: “I need more details.”
• Use: “I understand this is frustrating. To help you as quickly as possible, could you share a bit more about what you saw?”
• Why: Acknowledging their feelings first reduces tension and makes them more willing to cooperate.

When you need a screenshot or recording

• Instead of: “Send me a screenshot.”
• Use: “If possible, could you attach a screenshot of what you see? That would help us a lot.”
• Why: “If possible” gives the user an option, and explaining why you need it increases the chance they will help.

When to Use Each Tone

Choosing the right tone is as important as choosing the right words. Here is a quick guide.

• Formal tone: Use for first-time contacts, official support tickets, or when the feedback is about a serious issue like data loss or payment. Example: “We sincerely apologize for the inconvenience. Would you kindly provide the details of your account so we can investigate?”
• Neutral tone: Use for most routine feedback conversations. Example: “Thanks for your report. Could you tell me which version of the app you are using?”
• Informal tone: Use only with users you have already spoken with, or in casual chat environments. Example: “Hey, thanks! Can you tell me what phone you’re on?”

Mini Practice Section

Test your understanding with these four questions. Try to answer before reading the suggested response.

Question 1

A user writes: “The app is too slow.” How do you ask for more details politely?

Suggested answer: “Thank you for letting us know. Could you please tell me which part of the app feels slow? For example, is it the login screen or the main menu?”

Question 2

A user says in a chat: “I can’t log in.” What is a good follow-up question?

Suggested answer: “Sorry about that. Can you describe what happens when you try to log in? Do you see an error message?”

Question 3

You are writing a formal email after a user reported a crash. What is a polite way to ask for device information?

Suggested answer: “We appreciate your report. Would you mind sharing the device model and operating system version you are using? This will help us identify the issue.”

Question 4

A user gives vague feedback: “The new update is bad.” How do you respond without sounding defensive?

Suggested answer: “Thank you for your honesty. Could you tell me more about what you don’t like? Your feedback helps us improve.”

Frequently Asked Questions

1. What if the user does not reply after I ask for more details?

Send a gentle follow-up after 24-48 hours. Keep it short and polite. For example: “Hi [Name], just checking if you had a chance to see my previous message. Any additional details would be very helpful. Thanks!”

2. Is it okay to ask for a screenshot in every request?

Only ask for a screenshot when it is genuinely needed. If the issue is visual (like a layout problem), a screenshot is very useful. For performance issues, ask for device details instead. Overusing screenshot requests can annoy users.

3. How do I ask for details without sounding like I doubt the user?

Always start by thanking the user and validating their feedback. Use phrases like “To make sure we fix this correctly…” or “To help you as fast as possible…”. This frames your request as helpful, not suspicious.

4. Can I use the same phrases for both email and chat?

Yes, but adjust the length. In email, you can use full sentences and more polite forms. In chat, shorter versions are fine. For example, “Could you elaborate?” works in both, but in chat you might say “Can you tell me more?”

Final Tips for Success

Requesting more details is a skill that improves with practice. Always remember these three points:

• Be specific: Tell the user exactly what information you need.
• Be polite: Use “could”, “would”, and “please” generously.
• Be grateful: Thank the user for their time and effort.

For more help with starting feedback conversations, visit our App Feedback Conversation Starters section. If you need to explain a problem clearly, check out App Feedback Conversation Problem Explanations. To practice your replies, see App Feedback Conversation Practice Replies. For any questions about this guide, please contact us.