Not every message deserves the same answer, speed or audience. Decide the channel first, then the wording.
The matrix
| Channel | Who sees your reply | Typical need | Suggested speed (a suggestion, not a rule) |
|---|---|---|---|
| Support mail | The sender only | A broken thing for one person | Fastest. This person is blocked. |
| Private feedback (in-app, tester feedback) | The sender only | Detail, bugs, ideas | Acknowledge briefly; reply in full when you act. |
| Public store review | Every future visitor | A verdict plus context | Prompt for clear problems, selective for the rest. |
Support mail
The sender wants a fix. Answer privately, ask for device and steps, and tell them what happens next. Nothing here needs to be public.
Private feedback
Say thanks, say whether you will act, and close the loop when you ship something. Testers who see their feedback used give better feedback next time.
Public reviews
Your reply is also written for the next reader.
- Keep it short, polite and specific.
- Do not argue and do not share personal data.
- Move details to private: "Please write to support at ..., so we can look at your device."
- Never offer anything in return for changing a rating.
Templates and tone: how to reply to app reviews. Legal and tone points: see the related page on tone and law.
A quick decision
- Is the person blocked? Support mail, answer first.
- Is it detail meant for you? Private reply.
- Will others read it and be misled or reassured? Public reply.
- Can you do nothing useful with it? Skip, without guilt.
Nudge the channel
Put a feedback link and a support address in your app and listing. If people have a private door, fewer complaints end up in public.
Start free for structured private feedback.
Related: hub, learn from one-star reviews, tone and law of replies.