How to Ask for an Update in an App Feedback Reply

When you are replying to user feedback for an app, you often need to ask for an update on a reported issue or a requested feature. The direct way to do this is to use polite, clear language that shows you value the user’s time and input. This guide will show you exactly how to phrase those requests, whether you are writing a formal email, a casual in-app message, or a support ticket reply.

Quick Answer: The Best Way to Ask for an Update

If you need a quick, ready-to-use phrase, here are the most effective options:

• Formal: “Could you please provide an update on this matter at your earliest convenience?”
• Neutral: “Would you be able to share an update on the progress of this request?”
• Informal: “Just checking in—any news on this?”

These phrases work in most app feedback reply situations. The key is to match the tone to your relationship with the user and the context of the conversation.

Understanding Tone and Context

Asking for an update is not just about the words you use; it is about the relationship you have with the user. In app feedback replies, you are often speaking to someone who has already taken time to report a problem or suggest an improvement. Your goal is to be respectful and encouraging, not pushy or demanding.

Formal vs. Informal

Here is a simple breakdown of when to use each tone:

Email vs. In-App Conversation

In an email, you have more space to be polite and detailed. For example:

• Email: “Thank you for your patience. Could you please provide an update on the bug you reported last week?”
• In-app message: “Any update on this? Thanks!”

In-app messages are usually shorter and more direct, but you should still keep a polite tone.

Natural Examples

Here are realistic examples you can adapt for your own replies. Each example includes a brief context.

Example 1: Following Up on a Bug Report (Formal)

Context: A user reported a crash a few days ago. You are following up via email.

“Dear [User Name],

Thank you for reporting the crash issue. Our team is looking into it. Could you please provide an update on whether you have experienced this issue again since your last message? Your feedback is very helpful for our investigation.

Best regards,
[Your Name]”

Example 2: Checking on a Feature Request (Neutral)

Context: A user requested a new feature in the app’s feedback form. You are replying through the support system.

“Hi [User Name],

Thank you for your feature suggestion. We are reviewing it with our product team. Would you be able to share an update on how this feature would help your workflow? Any additional details would be appreciated.

Thanks,
[Your Name]”

Example 3: Casual Follow-Up (Informal)

Context: A user sent a quick message about a login problem in the in-app chat.

“Hey [User Name],

Just checking in—any news on the login issue? Let us know if you need more help.

Thanks!”

Common Mistakes When Asking for an Update

Many English learners make these mistakes. Avoid them to sound more natural and professional.

Mistake 1: Being Too Direct or Demanding

Wrong: “Give me an update now.”
Why it is wrong: This sounds rude and impatient. It does not respect the user’s time.
Better: “Could you please provide an update when you have a moment?”

Mistake 2: Using Vague Language

Wrong: “Let me know about the thing.”
Why it is wrong: The user may not know what “the thing” refers to. Be specific.
Better: “Could you let us know if the login issue is resolved?”

Mistake 3: Forgetting to Thank the User

Wrong: “Update on the bug?”
Why it is wrong: It feels cold and transactional. Users appreciate gratitude.
Better: “Thank you for your report. Do you have any update on the bug?”

Mistake 4: Overusing “Please” in a Robotic Way

Wrong: “Please please please update me.”
Why it is wrong: It sounds desperate or insincere. One “please” is enough.
Better: “Please let us know if you have any updates.”

Better Alternatives and When to Use Them

Here are some alternative phrases you can use instead of the basic “Can you update me?” Each has a specific nuance.

• “I would appreciate an update on this.” – Use this when you want to sound polite and formal. It works well in written emails.
• “Could you kindly share an update?” – This is slightly more formal than “please” and shows extra respect. Good for first-time replies.
• “Just checking in on the status.” – This is neutral and friendly. It is perfect for follow-ups without pressure.
• “Any progress on this?” – Use this in casual, ongoing conversations. It is short and direct but still polite.
• “We would love to hear how things are going.” – This is warm and encouraging. Use it when you want to build a positive relationship with the user.

Mini Practice Section

Test your understanding with these four questions. Try to answer each one before checking the suggested answer.

Question 1

Situation: A user reported a payment issue three days ago. You are sending a follow-up email. What is the best way to ask for an update?

Answer: “Thank you for reporting the payment issue. Could you please provide an update on whether the problem has been resolved on your end?”

Question 2

Situation: You are chatting with a user in the app, and they mentioned a problem with loading images. You want to check in casually.

Answer: “Hey, just checking in—any news on the image loading issue?”

Question 3

Situation: A user sent a feature request, and you need more details. How do you ask politely?

Answer: “Thank you for your suggestion. Would you be able to share an update on how you envision this feature working? Any examples would be helpful.”

Question 4

Situation: You are writing a formal reply to a user who has been waiting for a fix. How do you ask for an update without sounding impatient?

Answer: “We appreciate your patience. Could you kindly provide an update on the status of the issue you reported? Your feedback helps us improve.”

FAQ: Asking for an Update in App Feedback Replies

1. Is it okay to ask for an update more than once?

Yes, but space out your requests. If you ask too often, the user may feel pressured. A good rule is to wait at least two to three days before following up. Use a friendly tone each time.

2. What if the user does not reply to my update request?

If the user does not reply, send one more polite follow-up. If they still do not respond, it is best to move on. Some users may have resolved the issue on their own or lost interest.

3. Should I apologize when asking for an update?

Only apologize if you caused a delay. For example, if your team took a long time to respond, you can say, “We apologize for the delay. Could you please provide an update on the issue?” Otherwise, a simple thank you is enough.

4. Can I use emojis when asking for an update?

Yes, but only in informal contexts, like in-app chat. A simple smiley face or thumbs up can make the message feel friendlier. Avoid emojis in formal emails or support tickets.

Final Tips for Writing Update Requests

To write effective update requests in app feedback replies, remember these three points:

• Be specific: Mention the issue or feature you are asking about. This helps the user remember the context.
• Be polite: Use “please,” “thank you,” or “appreciate” to show respect.
• Match the tone: Use formal language for official emails and casual language for in-app chats.

For more help with polite requests, visit our App Feedback Reply Polite Requests section. If you want to practice writing your own replies, check out our App Feedback Reply Practice Replies page. You can also learn how to start your replies effectively in our App Feedback Reply Starters guide.

If you have any questions about this guide, feel free to contact us. For more information on how we create content, see our Editorial Policy.