Back to InsightsInfrastructure

My own contact form lied to me for seventeen days

Narcisa BudworthAugust 15, 20264 min read

I test other people's contact forms for a living. Mine failed silently for seventeen days, and the only reason it cost nothing was luck. Here is how to catch this on your site.

Late one night I submitted a test through my own contact form. The success screen played its little animation, told me to expect a reply, and looked exactly the way I designed it to look. Then I opened my inbox and waited for a message that never came.

I audit websites for a living. Forms that fail silently are one of the first things I check on other people's sites, and my own site runs automated health checks I built myself. None of that helped, because none of it watches the one thing that matters about a form: whether the message actually arrives.

What the thank-you screen actually measures

When a visitor submits a form, the site hands the message to a delivery system and reports that the handoff worked. That is what the thank-you screen measures. The handoff. Delivery happens later, in machinery the visitor never sees, and when it fails there, nothing comes back to the page. My messages were being accepted, tried five times each, rejected every time, and quietly set aside in a holding pen for failed mail. From the outside, a perfect form. From the inside, a slow month.

One deleted line

The cause was a cleanup from weeks earlier. I removed a page nobody visited, and the same change quietly deleted one line deep in the email machinery: the line that attaches a field my email provider requires on every message it sends. From that day, the provider rejected everything. The cleanup looked harmless. It was about a page, not about email. That is how these failures work: the break lands two systems away from the thing you touched.

Seventeen days

The form was broken for seventeen days. Seventeen days is long enough to lose real business. I got lucky. Luck is not a system.

The uncomfortable part: I had already published the warning. There is an article on this site that tells owners the quietest failure a website can have is a form that says thank you into a void, and that they should test their own forms regularly. I wrote the advice. My site still needed me to follow it.

The earlier article on silent failures

How it got caught

It got caught the boring way. I submitted a test like a stranger would, waited for the email like an owner would, and when it did not arrive, I went into the delivery log and read what happened to every message the site ever tried to send. The log had been recording the whole story for seventeen days. Every attempt, every rejection, every message given up on. Nobody had asked it. The fix took one evening: restore the deleted line, replay the test through the repaired pipeline, and watch the log finally say sent.

The checks that beat luck

  • Once a month, submit your own contact form and follow the message all the way to your inbox. The thank-you screen does not count. Arrival counts.
  • After any change to your site, test the form again, even when the change seems unrelated. Especially when it seems unrelated.
  • If inquiries go quiet for two weeks, treat it as a symptom to investigate, not a season to wait out.
  • Know where your delivery log lives, or make sure someone does. Silent failures are only silent when nobody reads the record.

A form that says thank you is not the same as a form that delivers. The difference is invisible from the outside, cheap to check, and expensive to ignore. My site got the lesson for free. Most businesses find out the other way.

Website management and care plans

Written by

Narcisa Budworth

Founder of Minarvo. Formerly a senior engineering leader at PEAK6 and Symphony, now building digital platforms for small and mid-sized businesses from Chicago.

Sound like your website? A free 30-minute call will tell you where you stand.

Book a call