Email (2FA) Verification configurations

What these configurations cover

Email (2FA) Verification confirms that an end user possesses the email address they claim by sending a confirmation code to it. Its configurations decide which Verification checks the template requires, and how many tries an end user gets at entering that code.

Email (2FA) Verification offers required or un-required Verification checks and maximum retries, which is the number of confirmation code attempts allowed.

Where to find it in the Dashboard

Documentation > Verification Checks lists every check available. Find the section for Email checks.
Verifications > Templates is where the change is made. Select the Email Verification template, then open Checks.

The two settings worth knowing first

Required checks decide what has to pass. A required check must pass for the Inquiry as a whole to be marked completed, so requiring more checks makes a template stricter and requiring fewer makes it more forgiving. See What is a Required Verification Check?.

Maximum attempts sets how many times an end user can enter a confirmation code before the Email Verification fails. The default is 5. Allowing more attempts can improve conversion when someone mistypes a code, and allowing fewer gives a bad actor fewer chances to guess a valid one.

When to reach for it

Reach for maximum attempts when the flow is higher risk and you want that guessing window smaller, or when mistyped codes are costing you completions. For lower risk, high conversion flows the default is often the right answer. Reach for required checks when your pass rates or your fraud exposure suggest the current set is wrong for the template.

For the full walkthrough, see Configuring Email (2FA) Verification checks. To read what the checks report once they have run, see Understanding Email (2FA) Verification results.

Plans Explained