The first reason is quality. FormSmarts is typically used for transaction where the information submitted is important. Important because the information collected is intended to be read by humans, rather than machines. Important because this information is often intended to be acted upon.

By allowing users to review and modify their submission, we increase the accuracy of the information you get in the end.

Form users understand that, and it increases their confidence that you value the information they are sending you. Most of times, confirmation will only add a few seconds to the whole transaction.

The second reason is security and usability. Many form submissions are automated, or even manual spamming attempts, known as form spam or comment spam.

When a user presses the submit button, a lot more happens on the server than you may suspect. If we spot a likely spamming attempt, we’ll ask the user to complete one or more tests (e.g. CAPTCHA test) on the confirmation page. But in the same time, the bulk of users will never be asked to waste time on a CAPTCHA test.

Yes, we do use CAPTCHA tests, but not everytime a form is submitted. Instead, the form handler decides each time whether or not to require a CAPTCHA test (and other verifications), based on unobtrusive analysis by our form spam blocker of the information submitted.

This saves time to every one, and reduces form abandonment.

Asking the user to complete a CAPTCHA test for every form submission affects form usability and accessibility.