anthrogate

Journey 1 of 2 · New user

Registration flow

A new user verifies into Anthrogate. Silent Authentication confirms the number belongs to the device. If the carrier check can't complete, the user falls back to an SMS code, then to an email code.

Consent shownSilent AuthenticationSMS OTPEmail OTP

Main path

Consent is shown on the first screen, next to the button that starts verification. No network call happens until the user taps Continue.

R1Enter number and consent

US carrier consent text and links to the Privacy Policy and Terms sit directly under the Continue button.

Consent shownNo network API
R2Carrier check runs

Vonage Silent Authentication is called over the device's mobile data connection to match the number to the device.

Silent Authentication
R3Number verified

Anthrogate completes verification and deletes user information when the attempt completes or fails.

No network API

Fallback 1 · SMS code

Used when the device is on Wi-Fi only, the carrier is unsupported, the number doesn't match, or the user taps “SMS the code instead” on R2.

RF1Enter SMS code

Vonage attempts SMS delivery first. Twilio is the planned fallback if Vonage fails to deliver the code. No carrier account data is used.

SMS OTP
RF2Number verified

Same result screen as R3, reached by SMS.

No network API

Fallback 2 · Email code

Used when the user taps “Email the code instead” on R2, chooses email on RF1, or the SMS code doesn't arrive.

RE1Enter email

The user provides an email address for a one-time code.

Email OTP
RE2Enter email code

The user enters the 6-digit code from their inbox.

Email OTP
RE3Account created

Registration completes. The number is marked unverified by carrier until a later sign-in succeeds.

No network API