← All frames · Frame 04 · Verified

Phone verified → continue

Rendered only after POST /verify/phone/confirm returns 200 with phoneVerified: true. Nothing is shown optimistically. Continue resolves through nextAfterPhone() (see 01), using a re-fetched status. It goes to check-inbox only if an email was sent and isn't confirmed yet. Otherwise it goes straight into the app, and the Email step is dropped from the rail.

Desktop · AuthCard 420px · /signup/phone

FuzeFront
  1. Account (completed)
  2. Phone (completed)
  3. Email (current step)

Phone verified

+44 •••• •• 0123 is now confirmed as your account's contact number.

One more step. We've sent a link to ada@lovelace.io. Confirm your email next.
Continue

Phone verified.

Mobile · 375px · email still pending

Verify your phone
  1. Account (completed)
  2. Phone (completed)
  3. Email (current step)

Phone verified

+44 •••• •• 0123 is now confirmed as your account's contact number.

One more step. We've sent a link to ada@lovelace.io. Confirm your email next.
Continue

Phone verified.

verified · email off or already confirmed

verification.email === false, or emailVerified became true in another tab. The inbox screen is skipped: Continue goes to ?next= or the default app.

Mobile · 375px (Android TWA)

Verify your phone
  1. Account (completed)
  2. Phone (completed)

Phone verified

+44 •••• •• 0123 is now confirmed as your account's contact number.

You're all set. There's nothing else to confirm.
Continue to FuzeFront

Phone verified.

Review · signup-phone-verification approve or reject each flow ↓
signup-phonependingApproveReject