Verification prompts in your application
Make email verification states understandable before customers retry
Check whether your verification prompt reflects the latest address and explains waiting, resending, and correction without exposing live links.
- ✓Yesterday's address stays on screen
- ✓Waiting resembles completion
- ✓Correction is hard to find
Turn waiting-state confusion into bounded findings
Current destination evidence
Connect the address edit to the prompt that should reflect it.
Resend language with boundaries
Separate visible request feedback from unproven claims about delivery or verification.
A useful return check
Review repeated edits and returning states rather than accepting one fresh signup capture.
Start with the waiting customer
Someone signs up for your application, sees a verification prompt, and changes the address because of a typo. The prompt still displays the original destination, so the person repeatedly requests another message. Review how the screen explains the current address, waiting state, resend action, and route back to editing. These are screens in your product, not an email verification service supplied by Retick.
Capture changes to the destination
Prepare synthetic addresses under a reserved example domain and an approved test mailbox where needed. Capture the prompt before editing, the change confirmation, and the prompt after returning. Keep message contents and usable verification URLs out of view. Record build, viewport, and whether verification was simulated. Retick accepts supported uploaded media and browser captures; it does not need access to your mailbox to review visible feedback.
Identify stale context precisely
A concrete issue is Verification prompt retains the previous email after an address change. Annotate the displayed destination and include the steps that produced it. Compare AI candidate findings with the capture, editing any assumption that messages were sent to the wrong place. A stale label and an actual delivery defect are different claims. Reject suggestions that rely on delivery evidence the recording does not contain.
Example acceptance criteria
After the address change is accepted, the verification prompt should show the current synthetic destination according to the app's display policy. Resend feedback should identify a waiting or accepted state without suggesting that verification is already complete. The user should have an obvious route to correct another typo. Confirm the agreed wording and directly check the return navigation with the responsible application team.
Follow the prompt through another cycle
Store the original and revised screens in a review cycle, then retest changing the address twice, resending while waiting, and returning after a controlled verified state. Download reviewed issues for a manual handoff or create cards from selected individual-media findings in Trello. Visual evidence cannot establish message deliverability, link ownership, or backend verification state. Those checks remain separate, and reviewers should never treat a reassuring banner as proof that an account is verified.
Review the message between signup and verification
Capture the changed address and clarify what the waiting screen should communicate.