In this guide
Your testers gave you time. How you treat them at the end decides whether they test your next version. Plan four short messages and send them on time. None of them asks for a store rating.
The timeline
| When | Message | Goal |
|---|---|---|
| During the beta | Short progress note | Keep testers engaged |
| After the beta | Thank-you with results | Show their work mattered |
| Shortly before launch | Heads-up | No surprise, no pressure |
| At launch | Launch note | Share the link, invite further private feedback |
1. Progress note (during the beta)
Send after you ship a fix someone reported. One sentence per change.
Subject: What changed this week
Hi {name}, thanks to your reports, this version fixes {issue 1} and {issue 2}. Still open: {issue 3}. If you have 5 minutes, {specific thing to try}.
Example: "Thanks to your reports, this version fixes the crash when rotating the screen. Still open: slow sync on weak networks."
2. Thank-you with results (end of beta)
Name concrete outcomes, not praise in general.
Subject: The beta is done. Thank you.
Hi {name}, the test is finished. Because of you we fixed {number or list} problems, including {most important}. Next step: {what and when}. You will hear from me when it is live.
Only write numbers you counted. If you did not count, name two or three real fixes instead.
3. Heads-up (shortly before launch)
Subject: Launch is close
Hi {name}, the app goes live around {date or "this month"}. Your tester access may end then; I will tell you what changes. Thank you again.
Do not promise a date you cannot keep. If store timing is unclear, say "around". Check each store's current rollout and tester rules.
4. Launch note
Subject: It's live
Hi {name}, {app} is out: {store link}. You helped shape it. If you notice anything wrong, reply to this email or use the feedback form in the app. That helps me more than anything.
What to leave out
- No request for public ratings. Do not ask, do not hint, do not offer anything in return. Reviews are the user's own choice. Never buy or swap them; see buying reviews and what to do instead. If a tester chooses to write one on their own, that is theirs to decide.
- No pressure to keep testing. An invitation, nothing more.
- No promise of rewards you cannot give.
Keep the channel open
Invite testers to keep sending private feedback. A short in-app form works better than a public post; see ask for in-app feedback without nagging. Respect people who do not reply. Remove anyone who asks to leave.
If testers gave you data like email addresses, use them only for tester updates unless they agreed to more. This is general information, not legal advice.
Next steps: the launch day plan, developer communities and zero budget app marketing. Back to the ASO and launch hub.
On AppReviewX, one feedback you write earns one credit, and one credit buys private feedback on your app. Try AppReviewX.