Magic link screen review for your product

Review magic link sign-in when the customer returns to the wrong tab

Capture the waiting tab and controlled completion state to clarify the return journey without exposing a usable sign-in link.

  • ✓The original tab still waits
  • ✓Another request looks necessary
  • ✓Used-link guidance is vague

Evidence for the journey around the link

Tab order made explicit

Record which page the customer returns to after the separate link step.

Stale instructions isolated

Report outdated waiting feedback without assuming authentication failed.

A defined second-request route

Agree what used-link and request-again screens should offer before exporting work.

Follow the split-tab experience

A customer requests a magic sign-in link in your application, completes the controlled link step in another tab, and returns to a waiting screen that still says Check your email. The review question is what that original tab should communicate next. Retick reviews media of your application's journey; it does not supply magic links or connect to arbitrary email services on your behalf.

Capture the relevant states safely

Prepare an approved test mailbox or staged link-completion fixture with synthetic account details. Never record a usable sign-in URL or a real inbox. Show the request confirmation, the controlled completion state, and the original tab after returning. Describe any omitted transition in the review notes. Include browser, build, tab sequence, and whether the original page was refreshed so the observation remains reproducible.

Keep stale feedback distinct from failed access

Bring supported screenshots or video into Retick, or use browser capture. Review AI candidate findings before accepting them. An example issue is Waiting tab offers another email after sign-in completes elsewhere. Annotate the stale instruction and explain the tab order. Edit any claim that the customer failed to authenticate if the evidence shows only an outdated waiting page, and reject guesses about synchronization internals.

Example acceptance criteria

Agree whether the original tab should update, provide a status-check action, or explain how to continue after opening the link elsewhere. Whichever behavior the product chooses, the waiting message and primary action should remain consistent. A controlled used-link state should offer the approved route to a new request without implying the old link can be reused. Check the resulting navigation directly using the safe fixture.

Repeat the branches that change the message

Store original-tab, completed, and used-link captures in a review cycle. After revision, compare returning without refresh, refreshing deliberately, and requesting again before completion. File exports support a manual handoff; selected findings from an individual media item can become Trello cards. Retick does not verify link expiry, session creation, or mailbox ownership. The application's technical tests must establish those behaviors separately, and reviewers should not present a changed waiting message as proof that sign-in is secure or complete.

Connect the waiting tab to the return experience

Review safe passwordless states and choose a clear continuation rule.