Your Contact Form Has Been Broken for Months

Key takeaways:

• Contact forms can fail silently for months — visitors see a confirmation message, but submissions never arrive — and most business owners only discover this during an audit, not in real time.
• A broken form is a measurement and monitoring problem, not a design problem. Spending money on a redesign before fixing the underlying issue guarantees you’ll repeat the mistake on a more expensive website.
• The most valuable thing a discovery call can surface is that the brief is wrong. Solving the actual problem is almost always faster and cheaper than solving the requested one.

When the Website Looks Fine but Isn’t Working

The form has a submit button. There’s a confirmation message. Everything looks professional. The only thing missing is that nobody’s receiving anything.

I’ve been auditing websites for a long time. Back when I started building sites in 1998, form submissions went straight to an email address via a simple CGI script, and when it broke you knew immediately because there was nothing subtle about it. A blank screen, a server error, something visible. What we have now is more sophisticated infrastructure and, paradoxically, more invisible failure modes. SMTP connections. Plugin dependencies. Email authentication layers. Any one of them can silently sever the chain between a completed form and a received enquiry, and the front-end experience stays completely intact. The visitor fills in the form. They hit submit. They see “Thank you, we’ll be in touch.” Nothing reaches anyone.

I had a discovery call late last year with a small consultancy in Toa Payoh. They wanted to scope a $14,000 website redesign. Before we talked about design or positioning or any of that, I asked to look at their analytics. Standard practice. Within a few minutes it was obvious their contact form had been silently failing since November. Five months. A plugin update had broken the SMTP connection. No error messages on the front end, no bounce notifications, no alert of any kind. Just silence where enquiries used to be.

They had assumed enquiries dried up because of market conditions.

How does a contact form fail without anyone noticing?

The short answer is that modern WordPress sites depend on a chain of components that can break at any link without producing a visible error. The form plugin captures the submission. A mailer plugin (or a configured SMTP service) handles the actual sending. That SMTP connection authenticates through a third-party provider. Each of those layers can fail independently, and the failure often doesn’t propagate back to the user-facing confirmation message.

In the Toa Payoh case, a plugin update in November changed how the mailer plugin handled authentication. The form kept working exactly as designed from the visitor’s perspective. The SMTP connection was simply no longer authorised to send. The messages queued, failed, and disappeared. No log entry the client knew to check. No notification. The confirmation message kept firing as if everything was fine.

This is more common than most people think. At Chillybin, whenever we do a site audit before a redesign conversation, checking form deliverability is one of the first things we do. Not because we expect to find a problem, but because we find one often enough that skipping it would be negligent. In the last couple of years I’ve seen this pattern repeat across retail sites, service businesses, and professional consultancies. The failure modes vary. The invisibility of the failure is consistent.

Why do businesses not catch this themselves?

Because there’s no natural alert. If your phone stops ringing, you notice immediately. If your contact form stops delivering, you see the same website you always had. The form is still there. The button still works. The confirmation still appears. The only signal is an absence, and absences are easy to rationalise.

The consultancy in Toa Payoh had been doing exactly that for five months. Slow quarter. Market’s tough. People are cautious. These are reasonable stories to tell yourself, and in many cases they’re true, which makes them even more effective at masking a technical failure. You’re not ignoring evidence. You’re explaining it away with plausible context.

This is why measurement has to come before interpretation. If you don’t have a baseline for how many form submissions you receive in a normal month, you have no threshold to trigger an investigation. You’re flying on feel, and feel will always find a narrative.

The fix in this case took twenty minutes. We reconnected the SMTP authentication, sent test submissions from three different devices, confirmed delivery, and documented the configuration. Twenty minutes to restore five months of lost lead flow. The $14,000 redesign conversation was paused while they monitored the restored form and collected actual data on enquiry volume.

Is this a WordPress-specific problem?

WordPress is where I see it most often because it’s what most small and mid-size businesses are running. But the underlying problem isn’t WordPress. It’s the assumption that a form that looks functional is functional.

Any platform that relies on third-party SMTP routing, whether that’s WordPress with WP Mail SMTP, a Webflow site using an external form handler, a Squarespace form with Mailchimp integration, can break at the integration point. The platform itself stays intact. The pipe that carries submissions to your inbox doesn’t.

I’ve seen this happen on Webflow sites where a Zapier integration quietly stopped authenticating. I’ve seen it on custom builds where an API key for a transactional email service expired. The specific mechanism changes. The result is the same: completed forms going nowhere, and a business owner who has no idea.

What makes WordPress more exposed is the update frequency. Core updates, theme updates, plugin updates, they happen constantly, and each one is a potential disruption point for any integration that depends on a specific version of a specific plugin. Most people have auto-updates enabled because it’s the secure thing to do. That’s correct. But security updates can break functionality, and if you’re not testing after updates, you find out through the absence of enquiries, not through an error message.

What should actually be in place to catch this?

Monitoring. Not sophisticated monitoring. Basic monitoring.

A dedicated inbox for form submissions that someone looks at weekly, not the general inbox where everything else lands. A simple test submission sent from outside the business every fortnight, just to confirm delivery. An analytics goal or event set up to track form submission completions, so you can spot a drop in the data before you’ve rationalised it into a market condition.

Some teams use uptime monitoring services that also test form functionality. That’s a reasonable layer for higher-volume sites. For most small businesses, a biweekly manual test and a watched inbox are enough. The point isn’t the sophistication of the system. The point is having a system at all.

One of my clients, a professional services firm in Sydney, now has a standing item in their weekly team meeting: send a test enquiry through the website, confirm it landed. Takes ninety seconds. They started doing it after we found a form failure during a quarterly review. That failure had been running for six weeks and cost them a measurable number of new business conversations. They didn’t need enterprise monitoring software. They needed a habit.

Why would someone spend $14K on a redesign before fixing this?

Because the redesign feels like a solution and the broken form feels like a mystery.

This is one of the oldest patterns in web projects. Something isn’t working, the visual experience feels dated, the conversion rate feels low, and the intuitive response is to redesign. A new site means a fresh start. It’s a tangible action that maps to a tangible outcome.

But if the enquiries weren’t coming in because the form was broken, not because the design was wrong, a new design doesn’t solve anything. You’ll have a $14,000 website with a beautifully designed contact page that still silently fails, or that converts at the same rate as before, because the design was never the constraint.

The consultancy I spoke to in Toa Payoh is a good example of what can happen when the brief gets interrogated before the project starts. They came in wanting a redesign. What they actually needed was a working form and a month of data to understand whether their lead volume was a design problem or a market reality. We didn’t build them anything that day. We fixed a connection and told them to wait. That’s not a glamorous engagement. It’s the right one.

Sometimes the most valuable thing a discovery call produces is the realisation that the brief is wrong. I’ve been doing this long enough that I’d rather have that conversation at the start than build something expensive that answers the wrong question.

The consultancy’s form is working now. They have three months of clean data ahead of them. If the enquiry volume recovers and holds, the existing site is probably good enough and the $14,000 stays in their business. If the volume recovers and the conversion rate is genuinely poor, then there’s a case for redesign, backed by actual evidence rather than a hunch dressed up as a brief.

Measurement and monitoring come first. The redesign question comes after. In 25 years of building websites, that order has never been wrong.