Why Website Forms Lose Inquiries, and How to Test Yours
Trace a test inquiry from your website form to the person who answers it, and find problems with spam checks, errors, confirmation, and email.

A contact form can look finished and still lose work. For an inquiry to reach you, a person has to finish the form, the site has to accept it, a notification has to reach someone, and that someone has to reply. A break at any step looks the same from your side: nothing arrives.
Five places worth checking are: a spam check that blocks real people, a confirmation message that is not true, errors that are hard to fix, a notification that never reaches the person who should act on it, and a form that asks for too much. A short test submission can help you see where the process breaks.
Where inquiries leak
A spam check blocks real people
Form spam is real, but the fix can cost you customers. The W3C note Inaccessibility of CAPTCHA says interactive challenges, the puzzles and distorted text meant to prove you are human, "inherently" exclude many people with disabilities, and that many popular techniques "are no longer particularly effective or secure."
This is a W3C Group Draft Note from December 2021, so treat it as guidance rather than a finished standard. Our recommendation is to use the least intrusive spam control that works for your form and test it with real people.
The confirmation says "sent" when nothing was saved
Some forms show a thank-you message the moment the button is pressed, whether or not the submission was stored. A more honest pattern confirms success only after the server confirms receipt. If sending fails, the form says so and keeps the visitor's text so they can try again or call instead.
Our recommendation: check receipt and notification separately. A message stored by the website may still need to reach an email inbox or customer system before someone can act on it.
Errors are hard to see or fix
When someone skips a required field, the form should explain what needs fixing. The W3C user notifications tutorial recommends clear error feedback and success messages. As a practical check, make sure an error does not force someone to type all their answers again.
The notification reaches no one who acts on it
Notification emails can land in spam, go to an old address, or arrive in a shared inbox nobody owns. Google's email sender guidelines require everyone sending to personal Gmail accounts to set up SPF or DKIM email authentication and warn that unauthenticated messages "might be marked as spam or rejected." If your form sends notices through a separate email service, that service needs to be set up for your domain.
The same guidelines tell senders not to impersonate Gmail "From:" headers, which matters if a form sends its notice "from" the visitor's Gmail address. A safer setup sends from your domain and puts the visitor's address in the reply-to field. That is consistent with Google's guidance that the From: header should show the actual sender, but it does not guarantee delivery.
The last leak is human: name the person who checks inquiries each business day.
The form asks for too much
The W3C forms tutorial notes that "if irrelevant or excessive data is requested, users are more likely to abandon the form," so keep only the fields you need to reply.
A 15-minute monthly form test
We suggest setting a reminder to run this regularly, such as monthly, and after a change to your site, email provider, or domain settings. This is an owner checklist; choose a frequency that fits how much you rely on the form.
- Submit each form from a phone. Put "TEST" and the date in the message.
- Trigger an error on purpose. Leave a required field empty. Check that the message names the field and that your other entries are still there.
- Read the confirmation. It should match what happened and say what comes next.
- Find the notification. Check the inbox it should reach, the spam folder, and any customer system the form feeds.
- Press reply. Confirm the reply goes to the test address, not to a no-reply address or to yourself.
- Note the time. Write down how long the notice took to arrive.
- Log the result. A one-line record by date makes a change easy to spot.
If a step fails, note where. "Would not submit" and "went to spam" are different problems with different fixes.
A hypothetical example
This example is made up. A landscaping company notices that quote requests have slowed. Its form has eight required fields, including phone and budget, and a picture puzzle at the end. Notices go to an address the owner stopped checking last year.
One monthly test finds three problems: the puzzle is hard to complete on a phone, the error message clears the form, and the notice lands in an unwatched inbox. Cutting the form to four fields, replacing the puzzle with a quieter spam filter, and routing notices to a monitored inbox addresses each one. Whether requests recover depends on many things, but the owner can now tell when the form itself is the problem.
When to get help
If the form accepts your test but no notification arrives, send the person who manages it your test time, the page address, and what you saw. Ask them to trace that specific submission. The website ownership checklist can help you identify which accounts and providers are involved.
Evidence
Sources
- Inaccessibility of CAPTCHAW3C WAI · Retrieved
- User NotificationW3C WAI · Retrieved
- Email sender guidelines - Gmail HelpGoogle · Retrieved
- Forms TutorialW3C WAI · Retrieved
A useful next step
Keep a useful record
Use the ownership checklist to organize the accounts and people involved in your site.
Open the ownership checklist