A product review should follow what a new user actually receives, not just what the signup screen promises. Test inboxes make the email part of that journey visible without mixing synthetic messages into a personal mailbox.
Choose a few distinct journeys
- A new user who confirms the first email promptly.
- A user who returns after the verification link expires.
- An invited teammate who already has an account.
- A person who entered the wrong address and needs to correct it.
- A trial user who opts out of promotional reminders.
Record decisions, not screenshots alone
For each journey, note the triggering action, expected email, observed arrival, destination screen and available next step. Record whether the user can recover without starting again. Screenshots help illustrate confusing copy, but they do not show whether the underlying state changed correctly.
Separate product friction from delivery trouble
If a message is late, inspect the sending and receiving stages before rewriting the confirmation page. If it arrives promptly but the user cannot tell which link to use, that is a different issue. Track these categories separately so a single conversion number does not hide the problem.
Turn the review into acceptance criteria
For example: an invited user sees the intended workspace name; an expired link provides a supported retry route; opting out of marketing does not suppress required account messages. Test these criteria in staging with synthetic data, and exclude the test accounts from acquisition reports.
Use a durable controlled address for longer research panels or beta programs. A temporary inbox should not become the only recovery channel for a valuable test workspace.