A potential customer fills in a quotation request on your WordPress website. They click Submit, see a success message and expect your team to respond. But no enquiry email reaches your inbox.
Why is your WordPress contact form not sending emails? Common causes include incorrect notification settings, invalid sender addresses, hosting mail restrictions, SMTP authentication failures, spam filtering, plugin conflicts and unsuccessful submissions.
The important distinction is that your form might be working while its email notification is failing. Alternatively, the form may never have processed the enquiry.
Before installing another plugin or changing DNS settings, find out which stage has failed.
How to Tell Whether Your Contact Form or Email Delivery Is Broken
A WordPress contact form involves several steps:
Customer submits form → WordPress processes submission → Form plugin validates entry → Notification is generated → WordPress mail system handles message → Email provider accepts or rejects it → Recipient mailbox processes delivery
A problem at any stage can prevent your business from seeing the enquiry.
Common Symptoms and What They Mean
Symptom
What to investigate
Submit button does nothing
JavaScript errors or form validation
Form displays an error
Submission processing or configuration
Form shows success but no email arrives
Notification settings or mail delivery
Saved entry exists but notification is missing
Notification generation or sending
SMTP test email fails
Mailer authentication or connection
SMTP test succeeds but form notification fails
Form-specific notification settings
Email appears in spam
Sender authentication or mailbox filtering
Only certain enquiries are missing
Conditional routing or background processing
These are starting points, not definitive diagnoses.
What Should You Check First?
Submit a controlled test enquiry and record the time, form response and destination email address.
Check the intended mailbox, junk folder and any available quarantine. Then review saved entries, notification settings and email logs if your system provides them.
Also test whether other WordPress emails, such as administrator notifications, work.
Do not begin by changing SMTP settings without checking whether the form submitted successfully. Changing the email transport cannot fix a broken Submit button.
10 Reasons Your WordPress Contact Form Is Not Sending Emails
Fix 1: Confirm That the Contact Form Is Actually Submitting
Before investigating email delivery, verify that WordPress receives and processes the submission.
An apparently functional form may fail because of missing required fields, invalid input, broken JavaScript, AJAX errors or security checks.
Test the form on desktop and mobile. Complete every required field and observe the result after clicking Submit.
For Contact Form 7, different responses suggest different problems:
- A green success response means the sending method completed without reporting an error, not that the email reached the inbox.
- A red mail failure response indicates a sending failure.
- An orange response indicates suspected spam.
Review the response and any supported submission records.
Avoid: Assuming that a form displayed correctly or accepted a click means the customer's enquiry was saved.
If submissions fail consistently, a WordPress developer may need to inspect the browser console, server response or plugin integration.
Fix 2: Check the Notification Recipient Email Address
Sometimes WordPress sends an email successfully, but the notification points to an incorrect or outdated address.
For example, a company may change its general enquiries mailbox while its website continues sending messages to a former employee.
In Contact Form 7, open the relevant contact form and review the Mail → To field.
In WPForms, open the form builder and review Settings → Notifications → Send To Email Address.
Check for:
- Misspelled addresses and inactive mailboxes.
- Incorrect dynamic mail tags or Smart Tags.
- Incorrect separators between multiple recipients.
- Notifications directed to the visitor instead of the business.
WPForms uses commas to separate multiple notification recipients.
Temporarily test with a controlled business mailbox, then restore the intended routing once verified.
Never expose customer email addresses in public troubleshooting screenshots.
Fix 3: Review Disabled Notifications and Conditional Routing
Not every valid form submission automatically generates a notification.
WPForms allows notifications to be enabled or disabled for individual forms. Some configurations also use conditional notification logic.
Imagine a property services business with one enquiry form covering plumbing, electrical work and general repairs.
Each service selection may direct the enquiry to a different department.
If the conditional rule for plumbing is incorrect, those enquiries might submit successfully without generating the intended notification.
Open the form's notification configuration and check:
- Whether notifications are enabled.
- Whether the correct conditions are applied.
- Whether optional fields control important routing decisions.
- Whether dynamic recipient fields contain valid values.
Submit a separate test for each possible route.
For Contact Form 7, also check that the mail template references the correct form fields and that any additional mail integrations are configured correctly.
A notification disabled by a rule is different from an email rejected by a server. The solution depends on which happened.
Fix 4: Correct the From Email and Reply-To Configuration
Incorrect sender settings can make legitimate form notifications appear suspicious to receiving email systems.
A common mistake occurs when a business configures its form to send messages using the visitor's Gmail or Outlook address as the From Email.
That can make the notification appear to come from a domain the website is not authorised to represent.
A safer approach is to use an appropriate authenticated business sender, for example:
From Email: website@example.co.uk
Reply-To: The email address supplied by the visitor
The From address identifies the sender. Reply-To tells the recipient where a response should go.
In Contact Form 7, Reply-To can be configured through Additional headers, using the correct email field mail tag.
For example, if the form's field is named your-email, the header may be:
Reply-To: [your-email]
Use the tag that actually exists in your form.
Review the From Name as well, and confirm that the configured mail provider permits the selected sender.
Avoid: Impersonating the visitor's email domain or assuming any address on your website's domain is automatically authorised to send.
Fix 5: Investigate WordPress wp_mail() and Hosting Email Problems
WordPress normally processes outgoing emails through its wp_mail() function, which uses PHPMailer.
Without a separately configured sending service, WordPress commonly relies on the hosting environment's PHP mail transport.
Some hosting providers restrict outgoing mail, require specific sender addresses or do not provide a fully configured local mail service.
Your contact form may therefore operate normally while the hosting environment cannot send its notification.
Check whether other WordPress-generated emails work. If all emails fail, investigate the hosting mail configuration.
Where available, review email errors or ask your hosting provider to check server logs and outbound sending restrictions.
According to the WordPress Developer Handbook, a successful wp_mail() result does not guarantee recipient delivery.
Avoid: Editing live server configuration files without understanding their impact.
If the hosting service does not offer a suitable mail transport, an authenticated SMTP or API-based provider may be appropriate.
Fix 6: Check SMTP or Email Service Authentication
SMTP allows WordPress to use a configured email service rather than depending entirely on the web server's default mail handling.
Plugins such as WP Mail SMTP and FluentSMTP support authenticated email-sending configurations.
However, installing an SMTP plugin is not the same as configuring a working email service.
Common problems include incorrect server details, expired credentials, revoked OAuth access, blocked outgoing connections or unsupported authentication methods.
Check which mailer is selected, whether the account remains authorised and whether the service's test-email feature reports an error.
If your business uses Google Workspace or Microsoft 365, prefer a supported modern authentication or API-based connection where available.
Google Workspace no longer permits traditional less-secure username-and-password access for third-party applications. Microsoft 365 is also moving away from legacy SMTP Basic Authentication, making OAuth a more sustainable option.
For Microsoft 365, check the applicable tenant and mailbox sending permissions with your administrator.
Avoid: Disabling TLS, weakening account security or storing email passwords in public website files.
After fixing the mailer connection, test an actual contact form submission. A successful SMTP test alone does not prove the form's notification configuration works.
Fix 7: Verify SPF, DKIM and DMARC Authentication
Your website may successfully hand a message to an email service, but the receiving system may distrust its claimed sender.
Three important technologies help email providers assess sender identity:
SPF (Sender Policy Framework): Identifies infrastructure authorised to send mail for a domain.
DKIM (DomainKeys Identified Mail): Uses cryptographic signatures to help verify the message and its sending domain.
DMARC: Applies authentication alignment and domain policy, with reporting capabilities.
Check whether the sending service has supplied the required DNS records and whether they have been configured correctly.
A business using Google Workspace, Microsoft 365 and a separate transactional mail provider may need coordinated settings for all authorised senders.
An incorrect SPF configuration, missing DKIM signature or DMARC alignment problem can contribute to rejection or filtering.
Important: Do not create multiple separate SPF TXT records for the same domain. Existing SPF mechanisms should be reviewed and consolidated appropriately.
Never copy arbitrary DNS values from a generic tutorial.
If you are unsure which providers send mail for your domain, ask your email or DNS administrator to investigate before making changes.
Fix 8: Check Spam, Quarantine and Mailbox Filtering
A notification can leave WordPress successfully without appearing in the business inbox.
It may be rejected, quarantined, forwarded to another address or moved into a folder by an inbox rule.
For Microsoft 365, ask an authorised administrator to inspect quarantine and message-trace information where available.
For Google Workspace, check relevant email logs and filtering settings.
Also investigate blocked senders, forwarding rules, mailbox restrictions and any bounce messages.
It helps to distinguish four different outcomes:
- The sending service accepted the message.
- The receiving system accepted the message.
- The message was delivered to a mailbox.
- The message appeared in the primary inbox.
These outcomes are not interchangeable.
If messages consistently land in spam, review the sender configuration and authentication before changing recipient filtering rules.
For wider email deliverability issues, read XCONS Solutions' guide: Why Are My Emails Going to Spam?.
Fix 9: Investigate Plugin Conflicts, Security Tools and Website Updates
Did the contact form stop working immediately after a WordPress update or plugin change?
The timing may provide a useful clue.
Caching plugins, script optimisation, security firewalls, CAPTCHA integrations and incompatible extensions can interfere with form submissions.
A JavaScript optimisation change, for example, may prevent the form's submission request from completing.
Record recent changes and compare the affected form with a known working version.
Before troubleshooting:
- Create an appropriate backup.
- Check plugin and WordPress compatibility.
- Review relevant documentation and error logs.
- Use a staging environment for potentially disruptive tests.
Avoid disabling every security tool on a live website merely to identify the problem.
If a security service blocked the submission, that is not the same as an SMTP server rejecting its notification.
Complex JavaScript, AJAX or firewall problems may require a developer to investigate the affected requests safely.
Fix 10: Investigate Background Queues, Scheduled Jobs and Connected Workflows
Some WordPress configurations process notifications asynchronously rather than sending them during the form submission itself.
For example, WPForms includes an Optimize Email Sending option for asynchronous notifications.
Other sites may use WP-Cron, Action Scheduler, external automation tools or CRM webhooks.
A form could save the customer's details successfully while the scheduled notification remains delayed or fails in a background process.
First establish whether your website actually uses background sending.
If it does, inspect available job statuses, errors and scheduled tasks.
For WPForms, the documented email settings include an option to review asynchronous sending behaviour.
For CRM integrations, confirm whether a webhook completed and whether the receiving system recorded the enquiry.
Avoid: Installing unnecessary queue plugins or assuming that a failed CRM integration automatically caused an email failure.
Where the workflow is custom-built, a developer may need to trace each stage independently.
How to Test WordPress Contact Form Email Delivery Properly
A structured test is more useful than repeatedly submitting the form without recording the results.
Step-by-Step Testing Checklist
- Record the existing configuration. Identify the form plugin, notification settings and active email transport.
- Submit a controlled enquiry. Use a test address and non-sensitive information.
- Verify the submission. Record the visible response and check stored entries where supported.
- Check notification settings. Verify the recipient, sender, Reply-To and conditional rules.
- Test the mailer. Use the configured mail service's testing feature where available.
- Compare the results. If the mailer test works but form notifications fail, investigate the form-specific settings. If both fail, focus on transport or authentication.
- Review available logs. Look for relevant errors without exposing customer message contents.
- Check the recipient mailbox. Review spam, quarantine, forwarding and message status.
- Test multiple devices. Repeat the controlled submission on mobile and desktop.
- Retest after making changes. Confirm both successful submission and actual receipt of the correct notification.
Do not enable unrestricted debugging that records customers' private messages.
A successful test confirms that a particular route worked at that moment. It does not guarantee that every future enquiry will arrive.
Can You Recover Contact Form Enquiries That Were Never Emailed?
Sometimes, but only if the submission was recorded somewhere.
A missing notification does not necessarily mean the customer's enquiry disappeared.
Depending on the system, records may exist in form-entry storage, CRM records, email logs, webhook destinations, backups or a third-party form service.
For Contact Form 7, the plugin does not provide persistent entry storage by default. A previously installed solution such as Flamingo may have retained messages.
For WPForms, storage depends on the licence, enabled features and configuration. WPForms Lite does not provide standard local entry storage, although its optional Lite Connect feature can back up eligible submissions after activation.
Review the existing evidence before installing new tools.
An email log may show that an email was attempted without containing the complete original enquiry.
If the form never submitted successfully and no record was created, recovery may not be possible.
Installing SMTP or logging software today cannot reconstruct submissions that were never captured previously.
If older database backups may contain relevant entries, ask a developer to inspect them safely. Restoring an entire old database directly over a live website could overwrite newer business data.
How to Prevent WordPress Form Notification Failures in the Future
Businesses that depend on website enquiries should maintain a process for confirming that leads are actually being captured.
Useful preventive measures include regular test submissions, authenticated email sending, correct notification routing and monitoring after WordPress updates.
Review sending-domain DNS records whenever the email provider changes.
If appropriate, use secure form-entry storage and a secondary lead record, rather than relying exclusively on email notifications.
A correctly configured CRM can make it easier to investigate a missing notification while retaining a separate record of a successfully received enquiry.
XCONS Solutions also provides CRM & Automation Systems for businesses evaluating centralised enquiry management and follow-up processes.
Any storage or integration should be reviewed for data protection, access control and retention requirements.
What Should UK Businesses Consider When Collecting Enquiries Through WordPress Forms?
WordPress enquiry forms often collect names, email addresses, telephone numbers and personal messages.
UK businesses must handle this information appropriately.
Under UK GDPR, businesses should provide relevant privacy information when collecting personal data directly from individuals.
The Information Commissioner's Office explains the importance of providing that information at the point of collection.
Practical considerations include:
- Clearly explaining how enquiry information will be used.
- Collecting only the data necessary for the enquiry.
- Restricting access to stored submissions.
- Applying appropriate security and retention policies.
- Reviewing third-party email and CRM processors.
- Avoiding unrestricted storage of private information in logs.
If customers upload documents, review how attachments are stored, transmitted and accessed.
Replying to a genuine customer enquiry is different from automatically adding that person to an unrelated marketing mailing list. Separate marketing rules may apply.
Businesses handling sensitive data should seek appropriate professional data protection advice.
When Should You Hire a WordPress Developer to Fix Contact Form Problems?
Some issues are straightforward enough for a website administrator to investigate.
For example, checking a notification address or reviewing a spam folder usually does not require custom development.
Professional assistance becomes more appropriate when:
- Several forms fail after a website update.
- JavaScript or AJAX errors prevent submissions.
- SMTP authentication remains unsuccessful.
- DNS authentication requires specialist changes.
- Microsoft 365 or Google Workspace integration fails.
- Form entries are not recorded as expected.
- CRM or custom workflows stop processing leads.
A WordPress developer can investigate website behaviour, while a hosting provider or email administrator may be better placed to diagnose infrastructure-specific problems.
The objective should be to identify the root cause before making further configuration changes.
Is Your WordPress Website Missing Customer Enquiries?
A broken contact form can prevent a genuine customer from reaching your business, even when the website appears to be functioning normally.
XCONS Solutions Ltd is a digital agency based in Ilford, East London, supporting businesses across the UK with website development and relevant technical integrations.
If your WordPress forms are failing, notifications are missing or enquiry workflows are not functioning as expected, our team can discuss your website's requirements and the appropriate next steps.
Explore our WordPress Development services or contact XCONS Solutions to discuss your website.