My contact form stopped working — how would I even know?

Why this one is uniquely nasty

Most website failures announce themselves. A broken page shows an error, a down site shows a warning, a slow page is visible.

A broken contact form shows the visitor a cheerful confirmation, thanks them for getting in touch, and delivers nothing. They believe they have contacted you. You believe nobody contacted you.

The symptom is an absence, and absence looks like a quiet month. Businesses have lost six weeks of enquiries to this and put it down to the season.

The reasons it breaks

Email deliverability. The most common by far. Forms send from your web server, which is not your email provider, so the message often looks like spam to receiving systems. It ends up in a junk folder or is rejected silently. Nothing on your site changes.

A changed address. The form sends to an employee who left, or an address that was closed. The mail bounces to somewhere nobody reads.

A plugin or integration update. Something updates, a connection breaks, the form still renders perfectly.

Spam protection set too aggressively. A filter starts rejecting real submissions. You see less spam and assume it is working — it is, on the wrong things.

Hosting or provider changes. A migration, a new security rule, an expired API key.

The two-minute test

Fill in your own form, from your phone, as a customer would. Not a test entry that says "test" — a realistic name and a realistic question, because some spam filters reject the obvious ones.

Then check:

• Did it arrive?
• Did it arrive in the inbox, not the junk folder?
• Does the reply-to address work — can you actually reply to it?
• If more than one person should receive it, did they all?

Do this today. Then put a monthly reminder in the calendar and do it again. Monthly is enough to cap your worst case at four weeks rather than six months.

Making it fail loudly instead

Prevention is better than testing, and there are three practical steps:

Send an autoresponder to the customer. "Thanks, we have got your message and will reply within a day." This is good service, and it doubles as a canary: if you stop receiving copies of your own autoresponders, something is wrong.

Copy submissions somewhere other than email. A dashboard, a spreadsheet, anywhere they are recorded independently. Then email failing does not mean losing the enquiry — it means noticing it.

Use a proper sending service rather than the web server. Dramatically improves deliverability and, importantly, actually reports failures instead of dropping them.

The variants worth checking too

The contact form is the one people think of. These fail the same silent way:

• Booking confirmations — the customer books, you never see it
• Order notifications
• Password reset emails, if you have accounts
• The phone number, which can be wrong or unclickable on mobile
• The email address in your footer, which may be an old one

Test each once. A wrong digit in a phone number sitting on a site for a year is not unusual, and it is invisible until someone mentions they could not reach you.

Making it fail loudly by default

The reason this failure is so damaging is that nothing tells anyone. Helm records form submissions in the dashboard as well as sending them, so a delivery problem means a notification you did not receive rather than an enquiry you never knew about.

That is the pattern worth insisting on wherever your forms live: submissions should be stored somewhere, not only emailed.

The habit

Once a month, send yourself a message through your own website, from your own phone, as though you were a customer.

It takes two minutes. It is the single highest-return maintenance habit for a small business site — because unlike almost every other failure, this one costs you the customers who were actively trying to give you money.