A contact form has one property that makes it different from every other part of a website: when it stops working, nothing tells you. The page still loads. The form still appears. The visitor still fills it in, presses send, and sees a message thanking them. The only thing missing is the part where it reaches you, and that part is invisible from both ends.
Every other fault on a website announces itself eventually. A broken page returns an error. A slow page is slow for you too. A form that silently drops enquiries looks exactly like a form nobody is using, and those two situations call for completely opposite responses.
How they break
Contact forms have more moving parts than they appear to. Something has to receive what was typed, decide it is not spam, and hand it to an email system that has to accept it and deliver it. Each of those can fail on its own without disturbing the others.
The common ones, roughly in order of how often I see them:
- The destination address changed. Somebody left, an address was closed, a business moved email providers. The form is still sending faithfully to an address that no longer accepts anything.
- Delivery started being refused. Forms often send mail that claims to come from the visitor's address rather than your own domain. Mail systems have grown much stricter about that, and a message that was accepted for years can start being rejected outright after a provider tightens its rules. Nothing about your website changed.
- It is arriving in spam. Not broken at all, just filed somewhere you do not look. This is the most common version and the easiest to miss, because the enquiries are technically arriving.
- A plugin or platform update. The form was provided by an add-on that has been updated, deactivated, or had its licence lapse. The form on the page can be a leftover that no longer connects to anything.
- The website moved. A rebuild or a change of hosting is where this most often starts. The visible page was carried across; the piece behind it that handles submissions was not.
- Spam protection got too enthusiastic. Filters that block automated submissions sometimes block real people, particularly on phones or older browsers. Those enquiries are stopped before they reach the sending stage at all.
How to actually test it
Most people test a form by filling it in and seeing whether it arrives. That catches the total failures and misses most of the interesting ones, because you are testing from a familiar device on a familiar network with your own email address.
A better test takes about ten minutes:
- Submit it from a phone on mobile data, not your office network, using an address you can check that is not your business one. A free address on a different provider is ideal, because it tests the delivery path a stranger's message actually takes.
- Check the spam folder of the receiving mailbox before concluding anything.
- Try it in a private browsing window, so you are not logged in to anything and no saved details are being filled in for you.
- Fill it in slowly and normally. Some spam protection scores fast, tidy submissions as automated.
- Do it again next quarter, and put a note in your calendar to that effect. This is the part that matters most, because a form that works today can stop next month without anything visible changing.
If you have had an enquiry arrive by another route recently, that is also worth a check. Somebody phoning to say "I filled in your form last week and heard nothing" is the loudest possible signal, and it usually arrives long after the fact.
If enquiries through your website have quietly dropped off over the last year, test the form properly before concluding that demand has fallen. Those are very different problems with very different responses, and they look identical from where you are sitting.
Why I often leave the form out
On smaller websites I frequently do not build a contact form at all, and I want to explain that rather than have it look like a shortcut.
A form is a piece of machinery that needs something running behind it. On a straightforward website that is otherwise just pages, adding a form means adding a service to receive submissions, which is another thing that can fail quietly and another thing to maintain. For a business whose enquiries mostly come by phone anyway, that machinery is carrying very little.
What I use instead is a phone number and an email address, both as links that work properly. Tapped on a phone, the number dials. Tapped anywhere, the email address opens a message already addressed. There is nothing to break, nothing to maintain, and no silent failure mode, because if an email does not send, the person sending it can see that immediately.
There is a genuine trade-off and it would be dishonest to skip it. A form asks the specific questions you need answered, so enquiries arrive with the information already in them. It gives people who dislike phoning a route in. And it can feed straight into whatever you use to track enquiries. Where those matter, a form is worth the machinery. The point is that it is a decision with a cost on both sides, not a box every website has to have.
If you do have one
Three things worth doing, none of them difficult:
- Send from your own domain, not the visitor's. The message should come from your website's address and put the visitor's address in the reply field. This is the single change that prevents most silent delivery failures.
- Send a copy somewhere else. A second address, or a record kept alongside the website itself. If the email path fails, the enquiry still exists somewhere.
- Make sure the person receives a confirmation. Partly courtesy, partly because if their confirmation stops arriving, somebody will eventually tell you, and that is the only early warning this problem has.
The underlying issue is not that forms are unreliable. It is that they are the only part of a website that can fail completely while looking perfectly healthy, so they are the one part that needs checking on purpose rather than when something looks wrong.