/OTP verification

OTP verification

Make respondents verify their email or phone with a one-time code before they can submit — by email or SMS.

How it works#

An Email or Phone field can require a one-time code. The respondent enters their email/phone, taps Send code, receives a 6-digit code, and enters it. The form won't submit until that field is verified — and changing the value afterwards asks them to verify again.

The verification UI only appears on your live published form, not in the editor preview — so designing a form never sends real codes (or costs you anything).

Turn it on#

  1. Add an Email or Phone field to your form.
  2. Open its properties (click the field) and switch on "Require email verification (OTP)" (email) or "Require SMS verification (OTP)" (phone).

Delivery channels#

  • Email — the code is emailed to the respondent.
  • SMS — a text message to the respondent's phone, for phone fields.

Plans#

Both email and SMS verification are Business-plan features — each send costs real money on the form owner's account. You can switch either on to try it in preview, but publishing a form that uses OTP requires Business.

Security & limits#

  • Codes are 6 digits, expire after 10 minutes, and allow at most 5 attempts.
  • There's a 30-second cooldown between resends to limit spend and abuse.
  • Editing the email/phone after verifying clears the verification — they re-verify the new value.
On the roadmap
Today, verification gates the submit in the respondent's browser. Server-side enforcement on the submission endpoint (rejecting a submit whose value wasn't verified) is a planned follow-up.