In this guide
You sent the build, the testers said yes, and now there is silence. This is normal. Testing is a favour done in spare time, and a favour that is unclear or heavy slips down the list. Fix the cause first, then remind, politely and once.
Why testers stay silent
- They do not know what to do. "Try the app" is not a task.
- It takes too long. A request that needs an hour gets postponed.
- Install trouble. They could not install or sign in and gave up without saying so. See Testers cannot install.
- No sense that it matters. Nobody confirmed that their last report was read.
- Bad timing. The message arrived on a busy day and got buried.
- They are not the right people. Someone who joined only to be counted may never open the app.
Fix the setup before you remind
- One clear task, 10 to 15 minutes. "Create an account, add one item, delete it, tell us what felt wrong."
- A simple way to answer. A short form or a template. Do not require a long email.
- A date. "Feedback by Friday" is easier to act on than "whenever".
- A first message that explains why the test matters and what you will do with the answers.
- Say thanks when something arrives, and say what you changed. Testers who see their report used tend to send the next one.
When and how to remind
A reminder is not a push. A simple pattern:
| When | What |
|---|---|
| Day 0 | Invitation with task, link, date |
| Around the middle of the period | One friendly check: "Anything blocking you?" |
| A day before the date | A short reminder with the link |
| After the date | One thank-you, and a last offer to send feedback later |
After that, stop. Messages every day make people mute you.
Reminder templates
Middle check
Hi, quick check: did the install and sign-in work for you? If anything is blocking you, tell me and I'll sort it out. Even two sentences of feedback help.
Before the date
Hi, a friendly reminder: feedback is welcome until Friday. If you're short on time, just tell me the one thing that bothered you most.
After the date
Thanks for being part of the test. If you still want to share something, I'm happy to read it. No pressure at all.
What not to do
- Do not offer money, gifts or favours in exchange for store reviews or ratings. Feedback to you stays voluntary, and store reviews are the tester's own decision, unasked.
- Do not guilt-trip or send long chains of messages.
- Do not count silent testers as testers when you plan: if you need a number of active people, recruit more than that.
When a whole group goes quiet
If many drop out, read closed test testers dropped out: what to do now. It covers what to do when the numbers fall during a test with a time requirement.
Related
- Overview: App testing problems and fixes
- Contradictory tester feedback: how to decide
- Too many bugs before release: what to fix first
AppReviewX is built around this problem: feedback is a fair exchange between developers, one feedback you write earns one credit, and credits buy feedback on your app. Nothing is traded for store reviews. For Google Play there are test groups (12 testers, 14 days in a row, for Android apps). Start free