If website form submissions are not coming through, first check whether the enquiry was saved anywhere outside the inbox. A saved enquiry with a missing email needs a different fix from a form that never captured the customer's details.
A thank-you message alone does not prove that an enquiry was saved or that its notification reached staff. Treat the journey as four separate checks: what the browser showed, whether an entry exists, whether an email service accepted the notification, and what happened at the receiving mailbox.
Where a Website Enquiry Can Disappear
Trace one test enquiry from the form to the receiving inbox. Each check shows where it may have stopped.
Start with one controlled test rather than changing plugins or email settings. That gives your website provider a specific enquiry to trace and helps preserve evidence of where delivery stopped.
1. Submit a test you can identify later
Use the public form as a customer would. Enter synthetic customer details, an email address you control and a distinctive message such as “Website delivery test TEST-ALPHA”. Do not include real customer information or sensitive documents.
Record these details before you submit:
- The exact page address and form name.
- The test reference, submission time and time zone.
- The mailbox that should receive the notification.
- Any selection that could change the destination, such as branch or enquiry type.
Then note what the browser does. Does it show a confirmation, flag a field, display an error or keep spinning? Save the exact error text or a screenshot.
A field error points towards validation. A stalled submission needs investigation at the website or form service. A confirmation lets you continue the trace, but is not evidence that all the later steps succeeded.
Also establish the scope: is this happening on every form, only one page, only one enquiry type or only for one recipient? That distinction can narrow the search considerably.
2. Look for the saved enquiry before changing anything
Open the website administration area or hosted form service and look for entries, submissions, responses or messages. Search for your test reference and time. Check any spam, rejected or deleted-entry views too.
Not every form stores entries. Storage may depend on the product, configuration or subscription. If you cannot find an entry screen, ask your provider whether submissions are stored, where they are held and whether storage was enabled at the time.
- The entry exists: the form captured this test. Continue with the notification checks below.
- The entry is in a spam or rejected view: inspect the reason before changing filtering.
- No entry exists, but storage is enabled: investigate capture or storage first.
- The form does not store entries: absence of an entry tells you nothing about whether this particular submission was processed. You need form-processing and email logs.
If genuine enquiries are saved, recover and respond to them through an approved business process before troubleshooting further. Keep access restricted and avoid exporting personal information into a broadly shared spreadsheet.
3. If no entry was saved, trace the form itself
Ask the website provider to check the test against the form service or website logs. They should establish whether the submission reached the server, passed validation and spam checks, and completed the save operation where storage is configured.
Useful checks include required fields, file-upload restrictions, spam protection errors and whether the form is connected to the intended account. A form that works without an attachment but fails with one offers a more useful clue than “sometimes it fails”. Use only harmless test files within the stated limits.
Give the provider the approximate date the problem began and any nearby changes: a website release, form edit, hosting move or plugin update. Ask them to compare those changes with the logs rather than assuming the latest change caused it.
Avoid replacing the form plugin as the first troubleshooting step. It can alter the behaviour you are trying to diagnose and leave older entries harder to locate. On a live website, potentially disruptive conflict tests should be handled by the provider in a suitable test environment.
4. If the entry exists, follow the notification in order
Check that the form was meant to send this email
Inspect the notification settings for the specific form. Confirm that notifications are enabled, the recipient address is correct and any conditional rule includes your test. Check for an old staff address or a branch selection that sends the enquiry elsewhere.
Use a sender address authorised by your sending service. Where supported, put the customer's address in Reply-To, which controls where staff replies go, rather than making the notification appear to come from the customer's domain.
Check the website's sending service
Ask for the email log entry matching your test. Was a notification generated? Did the sending service accept it, defer it for another attempt or reject it? Record the message identifier and any error or rejection text.
For WordPress sites, the official mail documentation explains that website email relies on an underlying mail transport. A remote SMTP server, an email-sending route, may need to be configured if the server lacks an appropriate local mail setup. Changing that route can address a sending problem, but does not guarantee inbox placement.
A successful generic test email is useful, but it does not prove that the actual form uses the same sender, recipient or notification rules. Retest through the public form.
Check the receiving server and mailbox
If the sending service reports delivery, ask what that status means. Acceptance by the recipient's mail server is not proof that the message appeared in the intended inbox or that anyone read it.
Search the destination mailbox using the test reference, sender and time. Check junk, deleted items, forwarding and inbox rules. Ask the email administrator to inspect organisation-level filtering and quarantine, which staff may not see. For Microsoft 365, administrators can review messages using the Microsoft Defender quarantine controls.
If the logs indicate authentication failures or spam filtering, have the email administrator check the sending domain's configuration. SPF, DKIM and DMARC are mechanisms used to authorise and authenticate domain email; Google's sender guidelines explain their role in delivery. Do not replace DNS records blindly, since the same domain may also support staff email and other sending services.
Trace a missing website enquiry
Submit a harmless test. The browser confirms it, but staff cannot find the enquiry email.
Find the test in the form's entry list, then match it to the notification log and message status.
The sending service accepted it; the email administrator found it in quarantine.
A worked example: the entry exists, but the inbox is empty
Illustrative example: a customer reports receiving a thank-you message after submitting a quotation request. Staff cannot find an email.
You submit TEST-ALPHA and see the same confirmation. The form's entry list contains the test, so capture succeeded for this submission. Its notification log then shows acceptance by the sending service. That confirms a hand-off, not inbox delivery.
The email administrator finds the matching message in quarantine. This locates the failure after capture and sending, within the receiving organisation's filtering. The next action is to inspect the quarantine reason and correct the relevant configuration, then repeat the full form test.
If instead there were no notification log entry, the investigation would stay with the form's notification settings or the connection to its sending service. Rebuilding the form would not be justified by either finding alone.
Keep an email failure from losing the only copy
Where practical, save the enquiry securely before attempting its email notification. This makes the enquiry and the notification separate records, so a failed email leaves something recoverable.
Storage still needs controls: limit who can view submissions, collect only necessary information and set a retention period suited to the data and business need. Someone also needs a way to detect failed notifications, such as a failure alert or a regular check of saved entries against delivery failures.
When reviewing website form handling, check that a notification failure cannot silently remove the only copy of an enquiry. A targeted repair to capture, storage or delivery may be sufficient without replacing the website or CRM.
Send your provider a precise fault report
Use this handover template rather than reporting only that the website contact form is not sending emails:
- Form: page address, form name and relevant selections.
- Test: synthetic reference, exact time and time zone.
- Expected destination: recipient mailbox.
- Browser result: confirmation, exact error or stalled submission.
- Saved entry: entry reference and location, absent, or storage status unknown.
- Email evidence: sending service, message identifier, status and rejection details if available.
- Receiving checks: inbox search, rules, spam and administrator quarantine results.
- Scope and changes: affected forms or recipients, when it began and recent website or email changes.
- Last confirmed successful step: browser response, saved entry, sending-service acceptance or recipient-server acceptance.
Share logs through an appropriate private channel, removing passwords, access tokens and unrelated customer details. After each fix, repeat the same controlled test through to the intended mailbox. Confirm capture and delivery separately before considering the fault resolved.
Find where your website enquiries are disappearing
Tell ZappFlow which website platform and form you use, where enquiries should arrive, and what happened during a recent test. We can help identify the failed step and scope a fix that keeps enquiries recoverable.