Your contact form might be sending enquiries nowhere

This is the most quietly expensive fault a website can have. Everything appears to work. The visitor sees a thank you message. The enquiry arrives nowhere, and nobody finds out for months.

Have the agents build my site

Forms fail silently for several common reasons: a changed email address, messages landing in spam, an expired plugin or integration, a mail service rejecting the sending domain, or a spam filter discarding legitimate enquiries. Test by submitting a real enquiry yourself from outside your organisation, and repeat the test monthly.

Why silent failure is so common

A form has several parts and only one of them is visible. The visitor sees the page and the confirmation message. Behind it there is a submission handler, an email service, a receiving mailbox, and one or more filters, and the visible part usually keeps working even when a later part stops.

So the site continues to say thank you while the message goes nowhere. There is no alert, no error, and no complaint, because the person who submitted it assumes you received it and is waiting for you.

The usual causes

When a form stops delivering, the reason is nearly always one of a short list, and none of them announce themselves.

  • The receiving address changed, or the person who owned it left.
  • Messages are landing in a spam or junk folder nobody checks.
  • A plugin or integration updated, expired, or lost its connection.
  • The sending domain fails authentication checks and mail is rejected.
  • A spam filter on the form is discarding genuine enquiries along with the rest.
  • A redesign moved the form and the new one was never connected.

How to test it properly

Testing from your own computer, logged in, from your office network, is the least reliable test available. Do it as an outsider would.

Submit a real-looking enquiry from a phone on mobile data, using an email address that has nothing to do with your business. Then confirm the message arrived in the inbox a person actually watches, that the automatic confirmation reached the address you submitted, and that replying to it works.

  • Use an address outside your organisation.
  • Submit from a phone on mobile data, not from the office.
  • Check the inbox a person genuinely monitors, including junk folders.
  • Confirm the automatic reply arrives and can be replied to.
  • Repeat monthly, and always after any change to the site.

Make failure visible

The real fix is not testing once, it is making a failure impossible to miss. Have submissions recorded somewhere besides email: a database, a spreadsheet, or a simple log. Then a missing email is obvious because the record exists without a corresponding reply.

Recording submissions as analytics events helps too. If the event count and the number of emails you received disagree, something in the chain is dropping messages.

The related leak: enquiries that arrive and are missed

A second version of this problem is organisational rather than technical. The message arrives correctly, in a shared inbox, and everybody assumes somebody else is dealing with it.

One named owner per enquiry, and a rule about the time within which a first reply is sent, fixes more revenue than most website changes. It costs nothing and can be arranged this afternoon.

What to tell the visitor

Whatever happens behind the scenes, the visitor should never be left wondering. A confirmation on the page and an immediate automatic email should both say the message arrived, when a person will reply, and give a number for anybody who cannot wait.

That confirmation also acts as a canary. If people start telling you they never received one, you have learned about a delivery problem from the outside rather than months later.

How Licheo builds this

Lead capture is part of the site rather than a widget, so submissions are recorded independently of email and a delivery failure cannot make an enquiry disappear entirely.

The whole path is tested from outside the organisation before launch, and the confirmation message is written properly rather than left as a default.

Part of a larger guide

This page is one part of Where the money escapes. The other parts:

Questions people ask

How do I know if my contact form is working?
Submit a real enquiry from a phone on mobile data, using an email address unconnected to your business, then confirm it arrived in the inbox somebody actually watches and that the automatic confirmation reached you. Repeat monthly.
Why do form emails go to spam?
Usually because the message is sent from an address at your own domain by a server that is not authorised to send for it, so it fails authentication checks. Check junk folders first, then have the sending setup reviewed.
Should form submissions be stored somewhere besides email?
Yes. If submissions are recorded independently, a delivery failure becomes visible rather than invisible, because you can see an enquiry with no reply against it. Email alone gives you no way to notice what never arrived.
How often should I test?
Monthly, and after every change to the site, the mailbox, or any plugin. Most silent failures start with a change that nobody connected to the form at the time.
What if enquiries arrive but nobody answers them?
That is the organisational version of the same leak. Give each enquiry a named owner and a time within which a first reply must be sent. It costs nothing and recovers more revenue than most website changes.

Make sure enquiries actually arrive

Capture built into the site, submissions recorded independently of email, and the whole path tested from outside before launch.

Have the agents build my site Read the full guide