Contact form not working
The most expensive broken thing on a website looks completely fine.
A dead contact form doesn't error, doesn't warn, doesn't log — it just thanks the visitor and deletes their intent. Every lost submission was someone ready to hire you. This is the fix that pays for itself with the first recovered lead.
Same-day diagnosis. Flat quote before any fix.
What’s actually happening
'Form not working' is actually two different failures wearing one costume. Either the form itself fails — the button spins, validation rejects everyone, the request errors — or, far more often, the form works perfectly and the EMAIL it sends never arrives: swallowed by spam filters, refused by mail servers, or sent from an address the internet no longer trusts.
The distinction matters because the second failure is invisible from both ends: the visitor saw 'thanks, we'll be in touch,' and you saw nothing at all. Sites run for months this way. The tell is a quiet inbox that used to hum — and the test takes two minutes.
The usual causes, ranked
After twenty-seven years of these calls, the odds are well mapped. Start at the top.
Email delivery, not the form: missing authentication
Websites sending mail without SPF/DKIM records are treated as impersonators — because that's what spam looks like. The form 'works'; the notification dies in transit or lands in spam. The leading cause, by far.
The site's mail method itself
PHP mail() from shared hosting is the least-trusted mail on earth. Proper delivery goes through an authenticated service — which is exactly what we wire in the fix.
A plugin update or conflict broke submission
The form errors or spins — visible breakage, honest breakage. Often arrives with an update, and at least it announces itself.
Overzealous spam filtering on the form
A CAPTCHA misconfigured or an anti-spam rule too aggressive silently discards real humans along with the bots.
Notifications going to a dead address
The form faithfully mails an inbox nobody checks — an ex-employee, an old domain. Configuration archaeology, two-minute fix.
What you can safely try first
Nothing below can make things worse — that’s the selection criterion. Anything riskier belongs in professional hands, on a backup.
- 1
Submit your own form, right now
From a personal email, with a realistic message. Note the time. This single test — did it arrive, where, how fast — is half the diagnosis. Check spam thoroughly.
- 2
Check the form plugin's entry log
Most form tools store submissions in the dashboard. Entries present + emails absent = delivery problem, proven. Entries absent = the form itself. The fork in one look.
- 3
Confirm where notifications are pointed
The form's settings list recipient addresses. You're looking for the dead inbox, the typo, the address on a domain you dropped.
Stop and call when…
- Test arrived in spam — authentication (SPF/DKIM) needs proper setup, not hope
- Entries log full, inbox empty — the delivery pipeline needs rebuilding on an authenticated service
- The form spins or errors and an update is the suspect
From there it’s our job: same-day look, flat quote, and the $389 flat repair covers most cases of exactly this.
Form & Email Rescue — buy it now, skip the hunt.
Contact forms delivering again, order and notification emails reaching inboxes.
Covers form and site-email failure on one site: broken submissions, vanishing notifications, spam-folder exile. Includes deliverability setup (SPF/DKIM) where the fix needs it.
Questions we hear a lot.
How many leads have I actually lost?
The form plugin's entry log is the honest ledger — every submission it caught, arrived or not. Reading it after a delivery fix is bittersweet: there they all are. It's also your recovery list; a late reply beats none, and we've watched 'sorry for the delay' emails close jobs weeks after the fact.
Why do my form emails go to spam?
Because unauthenticated website mail is indistinguishable from spoofing, and mail providers stopped giving the benefit of the doubt. SPF and DKIM records — plus sending through an authenticated service instead of the server's default — are what legitimacy looks like technically. That's the core of the $389 fix.
Should I just put my email address on the page instead?
As a backup, sure — some visitors prefer it. As a replacement, no: forms capture structured details, feed tracking, and filter bots. And a visible address gets harvested by spammers. Fix the form; add the address as a courtesy.
What does the flat fix include?
Diagnosis across the whole pipe — form, submission, delivery, authentication — the repair, a monitored test series, and deliverability records set properly so it stays fixed. $389, refunded if we can't get your leads flowing.
Related symptoms & help
Errors travel in packs. If this one visited, check its friends.
Every lost submission was somebody ready to hire you.
Send the symptom, get a same-day look and a flat quote from the developer who's fixed this exact thing more times than either of us can count.