SoftVolt AISoftVolt AI
From the blog

Notes from the people doing the work.

Scoping decisions, build notes and the reporting agencies forward to their clients — written up as the job finishes.

WordPress form submission not working? The checklist we run on every client site

A form can look fine and still fail twice: the email never reaches the inbox, or the entry is never saved. The eight checks we run on every WordPress form we build for agencies.

Published
Written by
Md Alamgir Hossen
Reading time
10 min read
Two colleagues checking a website form on a laptop together

The form on a client site is the page nobody looks at until the client asks why the leads stopped. By then the enquiries have been sitting in a spam folder for a fortnight, or they were never stored anywhere, and the agency is the one explaining it.

We build and look after WordPress sites for agencies under their brand, and when a WordPress form submission is not working, the cause is almost always one of the eight checks below. This is the order we run them in, on every form we hand over.

Quick answer: a form works only when two separate things work. The notification email has to reach the inbox, which on WordPress means sending through SMTP from an address on the site’s own domain, with SPF, DKIM and DMARC published in DNS. And the entry has to be saved in the dashboard, which some plugins, Contact Form 7 included, do not do on their own. Test both with a real submission on desktop and on a phone, and test again whenever the site, the host or the mail provider changes.

One form submission, two checks: the email reaches the inbox and the entry is saved

Why WordPress form emails go missing

  • WordPress sends mail through PHP by default. Its wp_mail function hands the message to the server’s own mailer, from an address that starts with wordpress@. The server has no proof it may send for the client’s domain.
  • “Sent” is not “delivered”. The same wp_mail documentation says a true return value does not mean the email was received. WordPress only knows it passed the message on.
  • Inboxes now insist on authentication. Since February 2024, Google’s email sender guidelines require SPF or DKIM from every sender, and SPF, DKIM and DMARC from bulk senders. Outlook.com began enforcing the same three for high-volume senders in May 2025.
  • The fix is common enough to be one of the biggest plugins there is. WP Mail SMTP is active on more than 4 million sites, and its listing says most hosts are not set up properly for PHP mail (checked 20 November 2026).

None of this shows on the page. The visitor sees a thank-you message either way, which is why a broken form can go unnoticed for weeks.

Step 1: Submit the form as a visitor would

Log out, open the page in a private window and fill the form in with real answers. Half of all form problems show up here, before email is even involved.

You should land on a success message or a thank-you page. If the button spins forever or nothing happens, look for a JavaScript error in the browser console, a caching or optimisation plugin that delays the form’s scripts, or reCAPTCHA keys that were created for the staging domain and never replaced for the live one. Then check the validation: a phone field that rejects numbers with spaces or a country code turns real customers away without telling anyone.

Step 2: Check where the notification goes, and who it comes from

Most “missing” form emails were sent, just to the wrong place or from an address the inbox does not trust. Open the form’s notification settings and read four fields.

Form notification settings: To the client, From the site's own domain, Reply-To the visitor
  • To: the inbox that should receive the enquiry. Confirm it with the client in writing; developers often leave their own address here after testing.
  • From: an address on the website’s own domain, such as noreply@clientdomain.com. Never the visitor’s email: the client’s domain cannot vouch for a Gmail address, so the message fails authentication.
  • Reply-To: the visitor’s email, so pressing Reply in the inbox answers the person who filled in the form.
  • Body: every field the form collects, so nobody has to log in to read the enquiry.

If the form also sends an auto-reply to the visitor, check it on its own. It is a second email with its own To, From and subject, and it fails in its own ways.

Step 3: Send through SMTP, not PHP mail

An SMTP plugin such as WP Mail SMTP or FluentSMTP changes the route the email takes. Instead of the web server sending it unsigned, the message goes through a real mail provider: the client’s Google Workspace or Microsoft 365 account, or a transactional service such as Amazon SES, Brevo or Postmark. The provider signs it, and the receiving server can check that signature.

PHP mail lands in spam; an SMTP plugin sends the same email through a trusted provider

Once it is connected, send the plugin’s test email to an address outside the client’s domain, such as a personal Gmail account. Testing to an inbox on the same domain proves very little, because the message never leaves the provider.

Step 4: Publish SPF, DKIM and DMARC for the domain

These three DNS records are how a receiving server decides whether an email really came from the domain it claims. The mail provider supplies the exact values; the agency or the client adds them at the DNS host.

SPF, DKIM and DMARC records explained, with example DNS values for example.com
example.com             TXT  "v=spf1 include:_spf.google.com ~all"
google._domainkey       TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkq..."
_dmarc.example.com      TXT  "v=DMARC1; p=none; rua=mailto:dmarc@example.com"
  • SPF lists every service allowed to send for the domain. A domain gets one SPF record, so when a new service is added, it goes into the existing record rather than a second one.
  • DKIM signs each message with a private key; the matching public key sits in DNS for receivers to check.
  • DMARC tells inboxes what to do when SPF and DKIM fail, and sends reports back. Start at p=none, read the reports, then tighten it.

The values above are examples for example.com. Real ones come from the client’s mail provider.

Step 5: Make sure every entry is saved in WordPress

An email is a notification, not a record. When one goes missing, the saved entry is what lets you find the lead and call them back, but only if the form plugin keeps entries at all.

Form plugin Keeps entries? Where to find them
Contact Form 7 No, not on its own. Add Flamingo Flamingo → Inbound Messages
Elementor Forms Yes, while Collect Submissions is in Actions After Submit Elementor → Submissions
Other form plugins Check the plugin’s documentation: some keep entries only on paid plans Usually an Entries screen

Flamingo, the companion plugin by Contact Form 7’s author, is active on more than 800,000 sites (checked 20 November 2026). Elementor’s Collect Submissions action is on by default but can be removed from a form or switched off site-wide, so open the form and check rather than assume.

Then send a test and open the stored entry. The date, the time and every field should be there.

Step 6: Read the logs in the right order

When a client says an email never arrived, the logs tell you where it stopped. Most SMTP plugins can keep an email log, and the mail provider’s dashboard shows whether each message was accepted, delivered or bounced.

  1. Nothing in the WordPress email log: the form never asked WordPress to send. Go back to steps 1 and 2.
  2. Logged, but rejected by the provider: authentication or the From address. Go back to steps 3 and 4.
  3. Delivered by the provider: the problem is on the receiving side. Check the client’s spam and junk folders, quarantine and any inbox rules that move mail.

Step 7: Test the spam protection on real people

Spam protection should stop bots, not customers. On every live form we add reCAPTCHA, Cloudflare Turnstile or a honeypot, with keys made for the live domain, and then submit the form on a phone to make sure a real person still gets through.

Then use the form badly on purpose: leave required fields empty, type an invalid email, enter a phone number with spaces and a country code. Each mistake should produce a clear message next to the field. A form that fails silently loses the visitor and leaves no trace.

Step 8: Run the final test on the live domain

A form is not finished on staging. Domains, keys and DNS all change at launch, so this last round happens on the live site.

Final form test grid: desktop and phone checked for inbox, spam, auto-reply, entry and reply-to
  1. Submit from a desktop and from a phone, with an email address you can open.
  2. Check the client’s inbox, and the spam or junk folder if it is not there.
  3. Check the auto-reply reached the visitor’s address.
  4. Open the saved entry and confirm every field, the date and the time.
  5. Press Reply on the notification and check it is addressed to the visitor.

The form setup every client site needs

Area In place before handover
Email SMTP plugin connected to a real provider, From on the site’s own domain, Reply-To set to the visitor, test email delivered to an outside inbox
DNS One SPF record covering every sender, DKIM published, DMARC in place and reporting
Entries Every submission saved with date, time and all fields, visible in the dashboard
Protection reCAPTCHA, Turnstile or honeypot with live-domain keys, validation that accepts real phone numbers and addresses
Testing Desktop and phone, inbox and spam, client and visitor emails, reply-to, repeated after any change

Form entries are personal data: UK and EU rules

  • Every entry falls under GDPR. Names, email addresses and phone numbers stored in Flamingo or Elementor Submissions are personal data under the UK GDPR and the EU GDPR.
  • Set a retention period. The ICO’s guidance on storage limitation says personal data must not be kept longer than it is needed. Agree a period with the client and delete old entries on a schedule.
  • Say it in the privacy policy. What the form collects, why, where it is stored and for how long.
  • Protect the dashboard. If someone gets into the stored entries, that is a personal data breach, and one that risks people’s rights must be reported to the ICO within 72 hours of becoming aware of it.

Frequently asked questions

Why is my WordPress contact form not sending emails?

In most cases WordPress is sending through the server’s PHP mail with no authentication, so the receiving inbox rejects the message or files it as spam. Connect an SMTP plugin to a real mail provider, set the From address to the site’s own domain, publish SPF, DKIM and DMARC, and send a test to an outside inbox.

Why are my WordPress form submissions not saving?

Because some form plugins do not store entries at all. Contact Form 7 needs the Flamingo plugin, and Elementor Forms needs Collect Submissions in Actions After Submit. Check the plugin’s settings, send a test, and look for the entry in the dashboard.

How do I stop WordPress form emails going to spam?

Send through SMTP instead of PHP mail, use a From address on your own domain, and publish SPF, DKIM and DMARC records. Put the visitor’s email in Reply-To, never in From. Then test with both a Gmail and an Outlook address.

How do I test that a WordPress form is working?

Submit it while logged out, on a desktop and on a phone, with an email address you can check. Then confirm the notification reached the inbox, the auto-reply reached the visitor, the entry is saved in the dashboard, and pressing Reply answers the visitor.

Do I need an SMTP plugin for WordPress?

For any form that brings in business, yes. WordPress’s default PHP mail is unauthenticated, and many hosts are not set up to deliver it reliably. An SMTP plugin sends through a provider that inboxes trust, and most can keep a log of every email.

Hand form checks to a team that runs them on every build

We set up, test and look after WordPress forms for agencies and their clients, from SMTP and DNS records to saved entries and spam protection, under your brand. Your client sees a form that works; you never have to explain a lost lead.

Comments

No comments yet. Yours would be the first.

Leave a comment

Your email is not published. Comments are read before they appear, so give it a few hours.

Not published.