Form submissions stopped arriving: how to fix it
Diagnose a website form that has gone quiet in the right order and remove the single point of failure that made the enquiries vanish.
The form says thank you and nothing arrives
Enquiries were landing every day. Then a week passed with none. The page loads, the button works, the success message appears and the inbox stays empty. The temptation is to assume demand dried up because the website gives you no evidence to the contrary.
Almost always the form is submitting correctly and the notification is failing. A website form does two separate jobs. It records the submission and it sends you an email about it. Those two jobs break independently and most sites only ever show you the second one.
What this costs and what cannot be recovered
Submissions that were never stored cannot be recovered. If your form only ever sent an email and that email was rejected by the receiving server the content is gone. Check whether your form plugin or platform keeps its own entry log before you spend time anywhere else. Where a log exists the last fortnight of enquiries is usually sitting in it untouched.
The diagnosis itself is cheap in money and expensive in attention. One person needs an uninterrupted hour with access to the website administration panel, the hosting control panel and the email account that should be receiving notifications. Without all three you will guess. Transactional email services and form platforms are billed monthly and Indian suppliers add GST at 18% on the fee.
Who needs to re-engineer this and who does not
If your site takes a handful of general enquiries a month do not buy a form platform or a transactional email service. Fix the immediate fault, turn on the entry log and check the log weekly. Paying a monthly subscription to protect four messages is not a sensible trade and it adds a system somebody has to maintain.
Re-engineering is justified when a single lost enquiry is worth more than a year of the subscription. That covers most B2B suppliers, education admissions, healthcare appointments, real estate and anyone running paid media to a landing page. If you are buying traffic the economics change completely. You are paying per click for submissions you cannot prove you received.
The order to check things in
Start by sending a test submission from a phone on mobile data rather than from the office network, using an email address outside your own domain. Note the exact time. Then look in the form's own entry log. If the test appears there the form works and the problem is delivery. If it does not appear the problem is the form itself or something blocking the submission.
For a delivery problem check in this sequence. Look in the spam and quarantine folders of the receiving mailbox. Check for an inbox rule or filter that somebody created and forgot. Confirm the notification address is still correct because a staff departure often leaves it pointing at a deactivated mailbox. Then check the sending method. Many hosts disable the server mail function and a form that relied on it stops silently. Confirm that the authentication records for your domain are published and that the address in the from field belongs to a domain you control. A notification claiming to come from the visitor's own address is the classic reason a provider rejects it.
For a submission problem check whether a recent plugin or theme update changed the form, whether a spam challenge is failing and silently rejecting genuine visitors, and whether a security plugin or firewall rule is blocking the submission endpoint. Browser console errors on the page will usually name the culprit within a minute.
How to know it is genuinely fixed
The metric that matters is a reconciliation. Count the entries stored by the form over a period and count the notifications that reached the inbox over the same period. Those two numbers must match. Run the comparison monthly because a mismatch is the only reliable early warning of the next failure.
The metric that flatters is the success message on the page. It is generated by the website and proves nothing about the destination. A form can show a thank-you screen while rejecting the record and failing the email at the same time. Treat the confirmation message as decoration.
The common mistake
The mistake is making email the only copy. Email is a best-effort channel. Providers reject, delay and filter messages for reasons you will never be told, and a website that stores nothing has no record when that happens. Every form should write the submission to a database, a spreadsheet or a CRM first and send the notification second.
The second mistake is testing with your own address. Your mailbox already trusts your domain so the test passes while real visitors fail. Test with an outside address and have one person check the stored log on a fixed day each week. Discovering this in week one costs an hour. Discovering it in week six costs the pipeline.
A note on what you are storing
Once you store submissions you are holding personal data about identifiable people. India's data protection framework creates obligations for whoever collects such data, covering the purpose it was collected for, how long it is retained and who inside the business can see it. How the framework applies to your business depends on your circumstances and a qualified professional should confirm it for you.
This guide explains how something works. It is not legal, tax or financial advice, and rules change. Confirm anything regulatory with a qualified professional before you act on it.