When you send feedback about an app and the response you receive is vague or incomplete, you need to ask for more details politely and clearly. This article gives you direct, practical phrases and strategies to request additional information in an app feedback message without sounding demanding or frustrated. You will learn the right wording for different situations, from formal support emails to casual in-app chats, so you can get the answers you need.
Quick Answer: How to Request More Details
To request more details in an app feedback message, start by thanking the person for their response, then clearly state what information you still need. Use polite phrases like "Could you please clarify…" or "I would appreciate more details about…". Keep your tone respectful and specific about what you are asking for. For example: "Thank you for your reply. Could you please provide more details about the steps to resolve this issue?"
Understanding the Context of Your Request
Before you write your request, consider the context. Are you replying to a customer support agent, a developer, or another user? Is the conversation happening through email, a support ticket, or an in-app chat? Your tone and word choice should match the situation.
Formal vs. Informal Tone
In a formal context, such as a support ticket or email to a company, use complete sentences and polite expressions. In an informal context, like a quick chat with a developer you know, you can be more direct but still respectful.
| Situation | Example Phrase | Tone |
|---|---|---|
| Formal email to support | "I would be grateful if you could elaborate on the solution you mentioned." | Polite, formal |
| In-app chat with a developer | "Can you give me a bit more info on that?" | Casual, friendly |
| Reply to a feedback response | "Thank you for your help. Could you please clarify what you mean by ‘check your settings’?" | Polite, specific |
Key Phrases for Requesting More Details
Here are practical phrases you can use directly. Each phrase is followed by a note on when to use it.
Polite and Formal Phrases
- "Could you please provide more details about…"
Use this when you need specific information about a feature, step, or issue. - "I would appreciate it if you could elaborate on…"
This is very polite and works well in email or support tickets. - "Would it be possible to clarify…"
Use this when the previous message was unclear or confusing.
Casual and Direct Phrases
- "Can you tell me more about…"
Simple and friendly, good for quick chats. - "Could you explain that a bit more?"
Direct but still polite, suitable for ongoing conversations. - "I’m not sure I understand. Can you give me an example?"
Use this when you need a concrete example to understand the point.
Natural Examples
Here are complete examples showing how to request more details in different app feedback scenarios.
Example 1: Formal Email to Support
Context: You reported a bug, and the support team replied with a short solution that is not clear.
Dear Support Team,
Thank you for your quick response. I appreciate your suggestion to clear the cache. Could you please provide more details about which cache files I should remove and whether this will affect my saved data? I would be grateful for any additional steps you can share.
Best regards,
Alex
Example 2: In-App Chat with a Developer
Context: A developer replied to your feedback about a missing feature.
Hi, thanks for getting back to me. Can you tell me more about when this feature might be available? Also, could you explain what you mean by ‘under review’? Is there a timeline?
Example 3: Reply to a Feedback Response
Context: You gave feedback about a payment issue, and the response was vague.
Thank you for your reply. I’m not sure I understand the part about ‘contact your bank.’ Could you please clarify what information I should ask my bank for? I would appreciate a step-by-step guide if possible.
Common Mistakes When Requesting More Details
Avoid these mistakes to keep your message polite and effective.
Mistake 1: Being Too Vague
Wrong: "Can you tell me more?"
Why it is a problem: The reader does not know what you need. It sounds lazy or impatient.
Better: "Can you tell me more about the steps to reset my password?"
Mistake 2: Sounding Demanding
Wrong: "I need you to explain this now."
Why it is a problem: This sounds rude and may make the other person less willing to help.
Better: "Could you please explain this when you have a moment?"
Mistake 3: Not Thanking First
Wrong: "What do you mean by that?"
Why it is a problem: It feels abrupt and ungrateful.
Better: "Thank you for your response. Could you clarify what you mean by that?"
Mistake 4: Asking Too Many Questions at Once
Wrong: "Can you tell me when it will be fixed, why it happened, and how to avoid it?"
Why it is a problem: Overwhelming the reader may result in no answer at all.
Better: Ask one or two clear questions at a time. For example: "Could you first tell me when the fix is expected? After that, I would also like to know why it happened."
Better Alternatives for Common Phrases
Sometimes the phrase you want to use can be improved for clarity or politeness.
| Instead of saying… | Say this… | Why it is better |
|---|---|---|
| "I don’t get it." | "I’m not sure I understand. Could you explain it differently?" | More polite and specific. |
| "Tell me more." | "Could you provide more details about…?" | Shows exactly what you need. |
| "What does that mean?" | "Could you clarify what you mean by…?" | More formal and respectful. |
| "I need more info." | "I would appreciate more information about…" | Softer and more grateful. |
When to Use Each Approach
Choosing the right approach depends on your relationship with the person and the platform you are using.
Use a Formal Approach When:
- You are writing to a customer support team for the first time.
- The issue is serious, such as a payment problem or data loss.
- You are replying to a formal email or support ticket.
Use a Casual Approach When:
- You have an ongoing conversation with a developer or support agent.
- The app uses a chat interface with a friendly tone.
- The issue is minor or you are asking for a quick clarification.
Mini Practice: Request More Details
Test your understanding with these four practice questions. Write your own response, then check the suggested answer.
Question 1
Situation: A support agent replied to your bug report saying, "We are working on it." You want to know when a fix will be released.
Your response: _________________________________
Suggested answer: "Thank you for your reply. Could you please provide an estimated timeline for when the fix will be available?"
Question 2
Situation: A developer said, "Try restarting the app." You already tried that, and it did not work.
Your response: _________________________________
Suggested answer: "Thank you for the suggestion. I already tried restarting the app, but the issue persists. Could you please suggest another solution or provide more details about what might be wrong?"
Question 3
Situation: You received a feedback response that says, "Your request has been noted." You want to know if it will be implemented.
Your response: _________________________________
Suggested answer: "Thank you for noting my request. Could you please clarify whether this feature is planned for a future update? I would appreciate any details you can share."
Question 4
Situation: A support agent wrote, "Check your email for instructions." You did not receive any email.
Your response: _________________________________
Suggested answer: "Thank you for your response. I checked my email, but I did not receive any instructions. Could you please resend the email or provide the instructions here?"
FAQ: Requesting More Details in App Feedback
1. What if the person does not reply after I ask for more details?
Wait a reasonable time, usually 24 to 48 hours. Then send a polite follow-up message. For example: "I just wanted to follow up on my previous request. I would still appreciate more details about the solution. Thank you."
2. Is it okay to ask for more details more than once?
Yes, but be patient and polite. If the first answer is still unclear, you can say: "Thank you for your previous response. I am still a bit unclear about one point. Could you please explain it again?"
3. Should I include screenshots when asking for more details?
Yes, if it helps. Screenshots can show exactly what you are confused about. For example: "I have attached a screenshot of the error message. Could you please explain what it means?"
4. How can I make sure my request is understood?
Be specific and use simple language. Avoid long sentences. Break your request into clear points. For example: "I have two questions: First, what does ‘pending’ mean? Second, how long does it usually take to change to ‘approved’?"
Final Tips for Success
When you request more details in an app feedback message, remember these key points:
- Always start with thanks. It sets a positive tone.
- Be specific about what you need. Vague requests get vague answers.
- Match your tone to the context. Formal for support tickets, casual for chats.
- Ask one or two questions at a time. This makes it easy for the other person to reply.
- Be patient. People are busy, but a polite follow-up is fine.
For more help with the first part of your feedback message, visit our App Feedback Message Starters guide. If you need to explain a problem clearly before asking for details, see our App Feedback Message Problem Explanations section. To practice replying to feedback, check out App Feedback Message Practice Replies. For more polite request phrases, explore our App Feedback Message Polite Requests category.
Comments are closed.