Confirm it is actually broken
Submit the form yourself, from a phone and from a desktop, using a real email address you can check:
- Does the on-screen confirmation appear?
- Does the notification email arrive?
- Does it land in the inbox or in spam?
- Is the submission recorded anywhere besides email?
Do this from outside your own network. An office IP address is sometimes whitelisted in ways a customer's is not.
The usual causes, in order of frequency
Mail deliverability. The most common by far. Notification emails are sent from your web server, and if the sending domain lacks proper authentication records, mail providers increasingly reject or silently discard them. Nothing appears broken — the mail just never arrives.
A plugin or platform update. Form plugins break on update, particularly when they interact with a page builder or a caching layer.
Spam protection failing. A challenge service whose keys expired, or a filter tuned so aggressively that real submissions are rejected.
A JavaScript error. Another script on the page throws, the form's submit handler never runs, and the button does nothing.
Caching. A cached page serving a stale security token, so every submission is rejected as invalid.
A changed recipient address. Someone left, the mailbox was closed, and mail bounces into nowhere.
Fix the delivery problem properly
Sending notification email directly from a web server is fragile. The reliable arrangement is to send through a proper mail service with authenticated sending on your own domain, so messages are accepted rather than filtered.
While you are there, set up the domain authentication records correctly. This affects every email you send, not just form notifications.
Store submissions, do not only email them
This is the single change that prevents the failure being catastrophic. Every submission should be written to a database or a system as well as emailed. Then a mail failure is an inconvenience rather than a loss, and you can recover the enquiries afterwards.
Many form tools do this by default and it is switched off. Check.
Recover what you can
If submissions were stored, work through the ones nobody answered, oldest first, and contact them with an apology and a direct answer. A meaningful share will still be interested — people forget they enquired and are often pleased to hear back.
If they were not stored, check server logs for POST requests to the form endpoint. That at least tells you how many were lost and over what period, which you need in order to understand the damage.
Monitor it from now on
Manual checks get forgotten. Practical monitoring:
- An automated submission on a schedule that alerts if the confirmation does not arrive
- An alert if no submissions are received for longer than your normal gap
- A monthly reminder to submit the form yourself
For a Pearland business relying on form enquiries alongside calls, that second alert is the one that catches this fastest — a quiet week is normal, a silent fortnight is not.
Keep the phone visible
A prominent phone number means a broken form costs you some enquiries rather than all of them. That redundancy is worth having regardless.
Frequently asked questions
What is the most common cause?
Mail deliverability. Notification emails sent from a web server without proper domain authentication are increasingly rejected or silently discarded. Nothing appears broken — the mail just never arrives.
What else breaks forms?
Plugin or platform updates, expired spam-protection keys or over-aggressive filtering, a JavaScript error elsewhere on the page stopping the submit handler, caching serving a stale security token, and a recipient address that no longer exists.
What is the single most important safeguard?
Storing every submission to a database as well as emailing it. Then a mail failure is an inconvenience you can recover from rather than lost enquiries you never knew about.
Can I recover lost enquiries?
If they were stored, yes — work through the unanswered ones oldest first with an apology and a direct answer; many will still be interested. If not, server logs of POST requests at least tell you how many were lost.
How should I monitor this?
An automated scheduled submission that alerts if the confirmation does not arrive, plus an alert when no submissions have been received for longer than your normal gap. A quiet week is normal; a silent fortnight is not.