Contact Forms

Your Contact Form Is Probably Broken, and Nobody Told You

By brucepro•November 19, 2026•6 min read
Your Contact Form Is Probably Broken, and Nobody Told You

A customer fills in your contact form, presses Send, and gets a polite thank-you message. She waits two days. Then she calls the next company on Google. You never knew she wrote, because the notification sat in a spam folder, or never left the website at all.

That failure is quieter than a broken page, and more common than owners expect. Leadferno submitted purchase-ready messages to 225 small business websites that ranked in Google's local top 10. In that test, 4.8% of the forms were broken outright, with errors or failed submissions even when every field was completed correctly. The other forms mostly worked. Working turned out to be a low bar.

Follow one message on its trip

Start where the visitor starts, on a phone, because that is how a Missoula homeowner with a leaking water heater will find a plumber. She types her name, phone number, and a short note about the leak. The first place that message can die is the button itself. A spam check that never loads, a script error after an update, or a required field that rejects a normal phone format can stop the send while the page still looks fine from your office computer.

If the send goes through, the website usually stores the entry in one place and emails a notification to another. Those are two separate deliveries, and they fail separately. A stored entry with no email means the lead exists, in a dashboard nobody opens. An email with no stored backup means one filter decision erases the only copy.

The email leg is where most of the quiet losses happen. SplitForms lists eight common causes in its troubleshooting guide, from spam-folder routing and missing SPF and DKIM records to exhausted free-tier quotas and a content delivery network caching the form response. The guide says those eight cover about 95% of the incidents its support team sees. Your form vendor will have its own list. The pattern underneath is the same: the website can be up, the form can be visible, and the handoff in the middle can be down for weeks.

The message that arrived and still got missed

Last week a client told me he had not realized website inquiries were reaching him at all. The forwards from his sales address looked like ordinary direct email in his inbox, so the website's work was invisible to him. Nothing was broken. He still nearly missed the point of having the form, because an inquiry he cannot tell apart from routine mail gets routine-mail urgency.

That conversation changed how I label form mail on builds now. The subject line carries a plain marker, Website Inquiry, followed by the sender's name. Two seconds of formatting, and the owner can see at a glance which messages came through the site and which ones a person typed to him directly.

A test that proves delivery, not just display

Open your public contact page on your phone, signed out of everything, and send a message you will recognize. Use a personal email address for the reply field, and write something plain in the body: November form test, checking delivery, no reply needed beyond confirming it arrived.

Then trace that one message through every stop:

  • Did the page show a clear confirmation after you sent it?
  • Does the entry appear in the form dashboard or website backend?
  • Did the notification reach the inbox it is supposed to reach, spam folder included in the search?
  • Can you reply from that notification and reach your personal address?
  • Did an automatic confirmation go back to the visitor address, and does it set a reply time you can actually meet?

Leadferno found only 15.6% of the businesses in its test sent any automatic confirmation at all. The visitor who gets silence after Send has no way to know whether her message landed, and plenty of them solve that uncertainty by writing to a competitor next. Guidance from Sande Caplin and Associates on routine form testing makes the same point from the maintenance side: test the full path after any change to the form, hosting, email, spam protection, or routing, and retest after a repair before calling the job done.

Build a second door

Give every submission a backup copy. On the sites I build, a submission gets stored first and emailed second, so a filter problem costs a notification, not the inquiry itself. The notification goes to two addresses. A weekly automated test sends a marked message through the live form, and I get an alert if the confirmation does not come back, which turns a month of silence into a same-week fix.

Your setup can be simpler and still cover the main risk. Keep the stored entries turned on in whatever form tool you use, and look at that list once a week when you check your reviews. Put a monitored phone number and a direct email address on the contact page next to the form, so a visitor whose send fails has another way through. Add the form test to the same calendar reminder as your backups, monthly, and again on any week the website or your email changes hands.

Run the phone test this week and time how long the message takes to reach the person who would actually answer it. If nobody can find your test by lunch, a customer with a leaking water heater already knows how that story ends.

Sources