What to do when testers go silent

Silence is normal in a closed test. People have jobs, families, and notifications they did not ask for. A tester who does not reply is not necessarily a tester who opted out.

The useful response is not guilt or a burst of messages. It is a short diagnosis, a clear ask, and a replacement plan if the person has genuinely gone.

Diagnose before you chase

Find out which of these is true:

• Never opted in. They have the link but did not accept.
• Opted in, never installed. They accepted but did not install from the testing page.
• Installed, not using. They are in, but the app is not part of their routine.
• Opted out. They left the test or uninstalled.
• Wrong account. They opted in with a different Google account.
• Console lag. They are active, but the count has not updated.
• Notification fatigue. They are ignoring messages because there are too many.

Each has a different fix. Asking "are you still testing?" without checking the Console first can make the conversation harder than it needs to be.

A follow-up cadence that does not annoy

Keep it light and spaced out:

• Day 1: welcome, install steps, one task.
• Day 3: "Did the install work? Anything confusing?"
• Day 7: "I fixed [issue]. Could you try [specific screen]?"
• Day 11: "Quick check: are you still opted in? The test ends on [date]."
• Day 13: final confirmation and thank you.

Do not send the same message every day. If someone has not replied twice, assume they are busy and plan around it.

Make replying easy

A message with one question is easier to answer than a message with five.

Weak:

Hey, how is the testing going? Any feedback? Also can you check the settings, the profile, the payment flow, and the crash on Android 13? And are you still opted in?

Better:

Quick one: are you still opted in to the test? A yes or no is enough. If yes, could you try the settings screen once and tell me if it loads?

The second message has a clear action and a low cost to reply.

Use screenshots

If a tester says "it doesn't work," ask for a screenshot of the screen and, if possible, the testing page. A screenshot answers the account, country, and install-source questions faster than a conversation.

Do not ask for screenshots that contain personal information. Tell them to crop or blur anything sensitive.

When to replace

Replace a tester when:

• they have opted out;
• they cannot install and the issue cannot be fixed quickly;
• they have gone silent through two follow-ups and the window is closing;
• they are using the wrong account and cannot switch.

Remember that a replacement starts their own 14-day clock. If you are on day 12, a replacement will not help the current window. In that case, extend the test or plan a new window rather than pretending the count is fine.

What not to do

• Do not send guilt-inducing messages.
• Do not spam the group.
• Do not create fake accounts to fill the gap.
• Do not offer payment for a five-star review.
• Do not ask testers to leave a review as a condition of testing.
• Do not remove a tester from the list without checking whether they are still opted in.

A short message that works

Hi [name], quick check on the closed test: are you still opted in? The test ends on [date]. If you are still in, a simple "yes" is enough. If you cannot continue, no problem — just let me know so I can plan around it. Thanks for helping.

That is friendly, specific, and easy to answer.

The short version

• Silence is normal; diagnose before you chase.
• Space out follow-ups and ask one question at a time.
• Make replying cheap.
• Replace testers early enough for the 14-day window.
• Never use fake accounts or review incentives.
• Keep a buffer so a quiet tester does not break the test.

Next: how to keep testers opted in, or how to replace a tester.