Contact Form Not Sending Emails? Trace the Missing Enquiry
If your contact form is not sending emails, trace one labeled test enquiry through four stages: submission, any saved record, notification generation and inbox delivery. A success message confirms only what the website reports. It does not prove that the intended person received the enquiry.
Start with a controlled test
Test only your own website or a site whose owner has authorized the check. Use a contact address you control, a recognizable subject such as “Website test — no action required,” and a timestamp. Do not use real customer details. Avoid forms that create bookings, payments or urgent dispatch requests unless a safe test method has been agreed.
Write down the page URL, browser, device, test time and expected destination. Use the contact-test worksheet to keep the observation and the outcome together. Before submitting, check that you have filled required fields and that an error message has not appeared elsewhere on the page.
Follow the enquiry through the system
| Stage | What to inspect | What remains unknown |
|---|---|---|
| Submission | Does the page show a clear success or error state after the action? | A success message alone does not establish storage or delivery. |
| Saved record | If the system stores enquiries, can an authorized operator find this exact test? | A saved enquiry does not establish that its email notification was generated. |
| Notification | Does the authorized email provider or application show the matching attempt and result? | Provider acceptance does not prove arrival in the intended inbox. |
| Receipt | Can the intended recipient find the matching test, including spam and filtering locations? | One received test does not guarantee every future submission will arrive. |
Not every form has all four stages. A form may forward directly to an email provider without saving a record, or it may prepare an unsent draft in the visitor’s email app. Establish the intended design first. MDN explains how a form’s action and method send data to a destination; that request is separate from later email handling.
Use the first failed stage to narrow the work
No usable response on the page
Look for missing required-field instructions, a button hidden by another element, a stalled loading state, or a visible error. Check the mobile contact path before assuming the email system is at fault. An authorized developer can inspect the relevant request and application error without exposing credentials or customer messages.
The page reports success, but there is no record
First confirm whether storage is part of the form’s design. If it is, verify that the success message depends on the actual save result. Do not remove error handling or disable validation simply to make the interface appear successful. A developer may need to inspect application configuration and the exact failed request.
The record exists, but the notification is missing
Check the configured recipient, the notification rule and the sending service’s recorded outcome. A disabled rule, wrong address, failed request or unavailable transport can each require a different correction. Retain the matching provider response when available; do not paste secret keys into a support request.
The provider accepted the message, but the recipient cannot find it
Review the intended mailbox, filtering, spam folders, quarantine and forwarding rules with the account owner. Verify the sender configuration against the sending provider’s own instructions. DNS authentication changes require authorized access and accurate provider-specific values. Installing an SMTP plugin at random is not a diagnosis.
A worked example: what can you conclude?
Illustrative example, not a customer result. At 10:15, a test form displays “Thanks.” The site stores the test, but the notification rule points to an old mailbox. The evidence supports correcting the notification destination. It does not support rebuilding the entire website or claiming a particular amount of lost revenue.
After changing the destination, repeat a labeled test. Check the record and receipt in the new mailbox. Record the old and new behavior and the test conditions. If a required stage cannot be inspected, mark it “not checked” rather than “passed.”
Agree what a successful repair means
A useful acceptance checklist names the exact form, required fields, expected confirmation, intended record and intended recipient. Include relevant mobile and keyboard checks. The W3C’s guidance on form notifications explains why people need clear feedback about errors and success. Accessible feedback and email delivery are separate checks; both may matter to the agreed work.
If the fault is contained, compare a focused repair with a wider rebuild. LeadFlowCheck’s website repair scope starts with evidence and written acceptance criteria. The free diagnostic covers public observations; private routing and implementation require separately agreed access.
Want evidence from your own website?
Request a free one-page diagnostic with up to three verified issues, supporting screenshots and recommended fixes. Implementation is optional and separately quoted.
Request a free diagnostic