A form can show a success message even when your team gets no email. Treat those as separate events. Start by finding where the message stopped: submission, saved entry, notification, mail transport or the recipient inbox. Changing SMTP settings before checking the recipient can leave the real problem untouched.
This guide is for owners of a WordPress business website who need enquiries delivered reliably. Work with a developer for configuration changes, and use a controlled test rather than real customer information.
Before troubleshooting, check whether your form plugin stores entries and whether that feature is enabled. Not every plugin saves submissions. If entries exist, assign someone to review them while email delivery is being investigated. If they do not, arrange an approved temporary contact route and tell staff where to find incoming requests.
Record the form URL, a test submission time with timezone, and a harmless unique reference such as TEST-OCT13-A. Do not enter passwords or sensitive customer details. Capture the exact on-screen result, not just “it worked.” Avoid repeated live tests that create CRM records, trigger sales sequences or notify customers.
| Layer | What to check | What the result tells you |
|---|---|---|
| Submission | Required fields, validation, spam rejection and browser errors | No successful submission means mail settings are not the first suspect |
| Entry storage | Whether this plugin should save an entry, and whether the test reference appears | A stored entry shows data reached the form system, not the inbox |
| Notification | Notification enabled, conditions satisfied, recipient address correct | A disabled or misrouted notification can explain missing email |
| Transport | Mail provider logs, authentication errors and accepted-message evidence | Shows whether the sending service accepted the message |
| Recipient | Spam, quarantine, filtering rules and mailbox availability | Accepted mail can still be filtered or rejected downstream |
Open the actual form’s notification settings. A global test email may use a different recipient or template, so it does not prove that this form is configured correctly. Look for an old employee address, a typo, conditional notification rules and dynamic fields that become empty.
In Contact Form 7, its mail configuration guidance recommends a sender address on the site’s domain and placing the visitor’s address in Reply-To. Follow the equivalent guidance for your own plugin and sending provider. Do not copy settings blindly between plugins.
Also test an optional field left blank. A template that produces a malformed header or invalid address only in that situation can fail intermittently. Test the exact customer path that caused the complaint, including mobile submissions and any conditional fields.
WordPress documents that a successful wp_mail() result does not prove the recipient received the email. Likewise, a plugin’s success screen is not a delivery receipt.
If you use a mail service that signs in to send email, ask your developer to check its connection and logs. Keep the test timestamp, masked sender and recipient, provider message ID, and error or delivery status. Do not share SMTP passwords or full customer messages in support tickets.
Ask the person who manages your email domain to check the sender records required by your provider. Avoid editing SPF or DKIM records without understanding existing senders; the website may share the domain with your normal business email. A second SMTP plugin can make it harder to tell which tool controls sending.
One successful test proves that message worked. It does not guarantee that every future message will arrive. Agree how often the business will check its important enquiry paths and who responds when a check fails. This belongs in your website maintenance scope, rather than remaining an informal promise.
Use a short incident note: affected page and form name; first observed failure; test time and timezone; expected recipient; entry saved yes/no/not supported; notification condition; mail log status; recipient filtering checks; recent plugin, hosting or domain-email changes. Include masked screenshots where useful.
Do not disable security tools or all plugins on a live site to “see what happens.” Ask for a staging reproduction or a documented, reversible test window. Techfusion Gear can help review the enquiry path and its maintenance responsibilities through a website support discussion.
The success message and inbox receipt are separate checks. Review notification settings, sending logs and recipient filtering to locate the failure.
No. Authenticated sending can address transport problems, but wrong recipients, form conditions and inbox filtering still need separate checks.