WordPress Contact Form Emails Not Sending? 12 Checks to Protect Leads
A visitor fills out your contact form, sees a success message, and assumes your team will reply. But the enquiry never reaches the inbox. If WordPress contact form emails are not sending, the problem may be in the form, notification rules, sending server, receiving mailbox, or CRM integration.
That distinction matters. A working form and a delivered email are not the same thing. WordPress documentation notes that a successful result from wp_mail() does not prove the recipient received the message. This guide gives business owners and website teams a practical way to find the break, protect genuine leads, and improve follow-up.
First, identify where the lead journey failed
Before changing plugins, submit one clearly labelled test enquiry using a safe test address. Note the time, page URL and outcome. Check the form’s saved entries, notification settings, mail log, recipient mailbox, CRM and analytics separately.
| What you observe | Likely cause | First check |
|---|---|---|
| No success message or saved entry | Validation, JavaScript, security or server failure | Required fields and form logs |
| Entry saved, no email arrives | Notification or delivery failure | Recipient, sender and mail logs |
| Email arrives, CRM empty | Integration feed or API issue | Feed and integration logs |
| Lead arrives, analytics shows none | Event or consent configuration | Analytics debugging |
Work through the following checks in order. They apply to many WordPress form plugins; Gravity Forms is used as a concrete example.
12 checks when WordPress contact form emails are not sending
1. Reproduce the issue without customer data
Test the published form on desktop and mobile. Complete the required fields and observe the confirmation. Test a second destination mailbox on another provider to distinguish a site-wide issue from one inbox problem. Do not use a real customer’s information for troubleshooting.
Record: test timestamp, form URL, submission result, entry ID (if available) and destination mailbox.
2. Confirm whether the form saved an entry
In Gravity Forms, open the form’s Entries screen. If the entry exists, the submission probably reached WordPress; investigate what happened afterward. If it does not, check field validation, JavaScript errors, CAPTCHA, caching, security rules and server-side processing.
Some plugins are configured not to retain entries. Confirm the intended storage behavior before treating a missing record as proof of failure. A success message alone should not be your only evidence of lead capture.
3. Check notification settings
Confirm the notification is enabled, the recipient is correct and conditional routing matches the submitted fields. Review notification settings for each form separately.
4. Set a valid sender and Reply-To address
Do not use the visitor’s email address as the message’s From address. Your server may not be authorized to send on behalf of that domain. Use a verified sender identity at your own domain and put the visitor’s address in Reply-To when needed. Verify the identity with your email provider.
5. Use a tested outgoing mail service
WordPress hands messages to the configured mail transport through wp_mail(). A transactional email service connected through SMTP or an API can improve observability and delivery reliability. Configure one intended sending path, authenticate it and send a test. Avoid stacking several plugins that compete to control outgoing mail. The WordPress mail reference explains why a successful function result does not prove inbox delivery.
6. Verify SPF, DKIM and DMARC
SPF identifies permitted senders, DKIM adds a verifiable signature, and DMARC sets domain-alignment and policy rules. Follow the records supplied by your email provider. Check for conflicting SPF records, missing DKIM keys and a visible From domain that does not align with the authenticated sender. DNS changes may take time to propagate. Authentication helps, but does not guarantee inbox placement. See Google’s email authentication guidance.
7. Read form and email delivery logs
Look for message IDs, accepted or rejected status, SMTP authentication errors, bounces and provider responses. A mail service accepting a message is not proof that the recipient read it. Enable detailed logging only when necessary, restrict access and avoid retaining sensitive form contents longer than required. Fix the specific failure before resending.
8. Check the receiving mailbox
Inspect spam folders, quarantine, inbox rules, forwarding, shared-mailbox access and storage limits. Send the same test to an independent mailbox. If one destination consistently fails while others work, investigate the receiving system with its administrator rather than rewriting the WordPress form. For business enquiries, prefer a monitored shared inbox with a named owner.
9. Test spam protection without blocking real visitors
CAPTCHA, honeypots, rate limits and security plugins can reduce junk submissions, but overly strict settings may reject legitimate enquiries. Test mobile browsers and the intended audience’s locations. Look for hidden validation errors, blocked scripts and challenges that do not load. Do not permanently disable protection to make a single test pass: isolate the failing control, adjust it safely and retest.
10. Test CRM feeds independently from email
If enquiries flow into a CRM or automation platform, check the integration connection, field mapping, permissions, conditional feeds and background processing. A saved form entry does not prove the CRM accepted it. Review API errors, token expiry and webhook logs. The Gravity Forms integration troubleshooting guide provides a starting point. Assign responsibility for retries when a service is unavailable.
11. Verify conversion events
Check that the successful form submission triggers one measurement event. A button click alone is not proof of a valid enquiry.
Keep identifiable enquiry details in your approved lead-management system, rather than including them in analytics event parameters or page URLs. Check that the tracking respects the website’s consent configuration.
12. Assign monitoring and a recovery owner
A form can stop working after a plugin update, mailbox change, expired API credential or hosting migration. Assign someone to review enquiries and run periodic end-to-end tests. Use independent failure alerts where supported, and confirm authorized staff can access stored entries if email notifications fail.
Document the form owner, destination mailbox, mail provider, CRM owner, test schedule and escalation contact. A defined WordPress maintenance arrangement can clarify ongoing responsibilities.
A practical 15-minute triage sequence
- Minutes 0–3: Submit a labelled test enquiry.
- Minutes 3–5: Check whether the form entry exists.
- Minutes 5–8: Review notification and sender settings.
- Minutes 8–11: Inspect mail logs and a second mailbox.
- Minutes 11–13: Check spam folders and CRM status.
- Minutes 13–15: Assign the next action and retest.
This is a prioritization exercise, not a promise that every issue can be resolved in 15 minutes. DNS and provider problems may need deeper investigation.
What should an ongoing form QA checklist cover?
| Check | Pass condition | Owner |
|---|---|---|
| Public form | Valid test creates an entry | Website administrator |
| Notification | Correct inbox receives the test | Mail administrator |
| Authentication | Sending domain passes intended checks | DNS/mail administrator |
| CRM | Correct record appears with expected fields | Sales operations |
| Analytics | One event per successful test | Marketing team |
| Recovery | Authorized staff can access stored leads | Site owner |
Frequently asked questions
Why does my WordPress form say “sent” when no email arrives?
The confirmation may mean the submission was accepted, not that an email reached the recipient. Check saved entries, notification rules, sending logs and the receiving mailbox separately.
Does every WordPress site need an SMTP plugin?
Not necessarily. Some hosting environments already provide authenticated mail delivery. What matters is a tested sending path with clear ownership and useful logs.
Can I use the visitor’s email as the From address?
Use an authorized sender at your own domain and place the visitor’s address in Reply-To. This avoids pretending your server can send on behalf of an unrelated domain.
Should I track form submissions as analytics conversions?
When enquiries are a business outcome, a successful-submission event can be useful. Validate it against accepted entries and follow applicable consent rules.
What if the form stores entries but the CRM has none?
Check the integration feed, field mapping, authorization and API logs. Email notifications and CRM synchronization can fail independently.
Make sure a website enquiry becomes a real conversation
A contact form is part of your sales process, not merely a design element. Reliable lead capture needs sound development, authenticated delivery, integration testing and a person accountable for following up.
