Contact form not working: a fix checklist for forms that do not send leads

By Ranjit Bhinge, founder of Blur Studio · Updated · 11 min read

Short answer: A contact form that does not send leads is almost always failing in one of four places: the form never submits, the form saves the message but the email is never delivered, the email lands in spam, or the lead reaches your CRM (customer relationship manager, the tool that stores your leads) and gets rejected. Submit a real test, find which of the four it is, then fix only that part. The checklist below takes about 10 minutes to run and ends with a test that proves the fix.

Ranjit Bhinge

You suspect your website form is losing enquiries, or you just found one that never reached you, and you want to find the break and fix it today.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Start with a test, not a guess. Fill in your own form, then follow that one message. Where it stops tells you what to fix. Most fixes are small: a wrong address, a message sent from the wrong sender, a spam folder, or a form that a browser script is blocking. This page works for any website, whether it was built with WordPress, an AI website builder, a hosting service for static sites or a custom build.

This is general information. The steps are the same on most platforms, but the menu names differ, so check your own platform's help pages.

The four places a lead can die

Think of a lead as a parcel with four hand-offs. It can drop at any of them.

Hand-offWhat goes wrongHow you can tell
1. Visitor to formThe submit button does nothing, a script error stops it, an ad blocker or an old cached page breaks itNo entry in the form log at all, and the browser console shows an error
2. Form to logThe form is saved but nobody is toldThe entry is in the form log or dashboard, but no email arrived
3. Log to inboxWrong recipient, typo, full mailbox, spam filter, sender rejectedEmail exists in spam, quarantine or the mail server log, or never leaves the sender
4. Form to CRMThe CRM refuses the lead because a field is missing, a limit was hit or the form was not recognisedEntry is in the form log and the inbox, but not in the CRM

Many people assume hand-off 3 and keep changing the email address. Check the form log first, because it tells you whether hand-offs 1 and 2 worked.

The 10 minute diagnosis test

  1. Submit from a phone on mobile data. Use mobile data, not your office wifi, so you see what a customer sees. Use an email address on a different domain from your site (for example a Gmail address if your site is on your own domain).
  2. Submit a second time from a Gmail address and a third time from an address on your own domain. Note the exact time of each.
  3. Check the form's own log. Most form tools and builders keep a list of submissions (in Ploy, an AI website builder, this is the Submissions page in the dashboard; in other tools it may be called entries, responses or inbox). If your test is there, the form works and the problem is email or CRM. If it is not, the problem is the form itself.
  4. Check the recipient's inbox, spam or junk folder, and any quarantine. On Google Workspace or Microsoft 365 business email, an admin may need to look in the admin quarantine. Search for a word from your test message.
  5. If nothing arrived, open the browser's developer tools (in Chrome, press F12 or right click and choose Inspect). Look at the Console tab for red errors, then the Network tab, submit again and find the request the form sent. A status of 200 is success. Any code starting with 4 or 5 is a failure, and the number tells your developer or the support team where to look.
  6. Turn off ad blockers and privacy extensions and test again. If it now works, a blocker may have been stopping the form script.
  7. Check the CRM. If the lead should flow into a CRM, look there with the same time stamp.

Write down the result for each of the three test submissions. The pattern tells you the cause. If the Gmail test arrives and the own-domain test does not, that points to how the email is being sent or filtered.

Fix hand-off 1: the form never submits

  • Clear the cache. If you changed the form recently, an old copy of the page may still be served, with the old form address in it. Purge the cache in your hosting, builder, caching plugin or CDN (content delivery network, a service that stores copies of your pages near visitors), then reload in a private window.
  • Read the console error. A script error that appears when you click submit usually means a plugin or script conflict. Disable recently added plugins or scripts one at a time and test after each.
  • Check required fields and size limits. Some builders limit what a form can carry. Ploy's documentation (updated November 18, 2026) says a form submission over 128 KB returns a form error. Netlify, a hosting service for static sites, caps file uploads at 8 MB per request with a 30 second timeout. A large photo upload can fail while a text-only test passes.
  • On Netlify, check the form is detected. Its docs say the form needs the netlify attribute and must be found at deploy time. A form drawn by JavaScript needs a hidden static copy of the form, or a hidden form-name field. Each form needs a unique name.
  • Look for a silent failure. On some sites the form shows a thank-you message even when the email was never sent. Do not trust the thank-you page. Trust the form log and the inbox.
  • On WordPress, check how mail is sent. Many sites send form email through the web server's basic mail function, which receiving systems often distrust. Sending through a proper email service (an SMTP plugin or your email provider) is the usual fix. Menu names vary, so use your plugin's help pages.
  • Check the browser and phone. If the form fails only on one phone, it is often a script that does not run there. Test Safari on iPhone and Chrome on Android.

Fix hand-off 2 and 3: saved, but the email never reaches you

This is the most common case, and the form log is your proof. If the entry is in the log, no lead is lost yet. You have a notification problem.

Recipient checks

  • Open the form's notification settings and read the address letter by letter. One wrong character is enough.
  • Check the mailbox is not full and has no forwarding rule that sends mail somewhere else.
  • Send the notification to a second address while you diagnose, so a single mailbox problem cannot hide the leads.

Sender checks: why "from" matters

Many old forms send the notification as if it came from the visitor. Their email address is in the From line. But the message really comes from your web server, which your visitor's email domain has not approved. Receiving mail systems see a message that claims to be from one domain while being sent from another, and they often file it as spam or reject it.

The fix is the same in nearly every tool: send the notification from an address on your own domain (for example forms@yourbusiness.com) and put the visitor's address in the Reply-To field. You can still hit reply and answer the visitor. Ploy's documentation describes this same pattern, with the submitter's email as the reply-to address.

Authentication in plain words

Three short names matter here. SPF is a DNS record listing the servers allowed to send email for your domain. DKIM is a digital signature added to each message. DMARC is a rule that says what to do when a message claims your domain but fails SPF and DKIM. DNS is the public address book of your domain, edited at your domain registrar or DNS host.

  • Google's rules for sending to personal Gmail accounts, in effect since February 1, 2024, say every sender needs SPF or DKIM, valid forward and reverse DNS, TLS encryption, and a spam rate under 0.3% in Google Postmaster Tools. See Google's sender guidelines page in the sources.
  • The stricter bulk rules (SPF, DKIM and DMARC together, and one-click unsubscribe for marketing mail) apply to senders of more than 5,000 messages a day to Gmail. A contact form sends a few messages, so those do not usually apply to you.
  • Google's DMARC guidance says a message passes DMARC when SPF or DKIM passes and matches the From domain. Start with a DMARC policy of none, which only reports, and let SPF and DKIM run for at least 48 hours before you tighten it.
  • If you add your form service to SPF, edit the SPF record you already have instead of creating a second one, because mixed-up records are a common cause of failures. Google's SPF page also says one record can hold up to 10 include: entries. Your DNS host's help explains how to edit records, and our custom domain DNS and SSL setup guide covers the basics of changing them.

If your notification arrives in spam only when the visitor address is a Gmail address, the visitor-as-sender problem above is the likely cause.

Form service limits

If you use a separate form service, check its monthly limit. Formspree, a hosted form-handling service, lists these plans on its pricing page as of November 2026, in USD:

PlanPrice shownSubmissions per month
Free$050
Personal$15 per month ($120 per year)200
Professional$30 per month ($240 per year)2,000
Business$90 per month ($720 per year)20,000

The page does not say what happens above the limit, so check with the vendor if your busy month could pass it. Other tools have their own limits, so look for yours in your plan details.

When your own spam protection blocks real people

A honeypot (a hidden field that only bots fill in) and a CAPTCHA (a puzzle or hidden test that tries to tell people from bots) protect you from junk, but a bad setup can also block real visitors. Signs: your log shows far fewer entries than you expect, and a test submit from a phone fails while a desktop one passes. Test the form as a customer would: on a slow phone, with autofill switched on, and with a password manager. Autofill can fill a hidden honeypot field and make a real person look like a bot. If you suspect that, read how to stop spam bots flooding your contact form and test each protection separately.

Check the spam or "blocked" folder of the form tool too. Many tools keep rejected entries for a short time.

Fix hand-off 4: the lead reaches the inbox but not the CRM

  • Salesforce Web-to-Lead (Salesforce is a large CRM) accepts 500 leads per 24 hours. Per Salesforce's help FAQ, extra leads queue, up to 50,000 combined with Web-to-Case, and are then rejected. A big ad day can hit this.
  • HubSpot (a CRM and marketing tool) can miss forms that were not built with its own form tool. Its help lists nine reasons, including forms inside an iframe, submit buttons driven by JavaScript, forms that load late, single-page apps, hidden fields, a field that is not an email type, and non-standard submit buttons.
  • Pipedrive (a sales CRM) shares a daily API budget across a company. Pipedrive's page says requests get a 429 (Too Many Requests) error once the budget is used up, until the next daily reset. A busy day of imports can use it.
  • Required fields: if the CRM needs a phone number and your form does not collect one, the lead may be rejected. Compare the CRM's required fields with your form fields.

For more on connecting a form to a CRM, read how to connect your website to a CRM, payment or booking tool. If you sell to people who ask for a quote, the free quote request form guide shows a simple setup.

The lead-loss audit: count every week

The fastest way to catch a silent failure is to compare three numbers once a week: entries in the form log, emails received, and leads in the CRM. They should match.

Week (made-up numbers)Form logEmails receivedCRM leadsReading
Week 1121212All good
Week 214995 emails missing: notification problem
Week 3111165 leads missing from CRM: CRM rejects

If the form log itself looks too low against your ad clicks or phone calls, the fault is at hand-off 1. A speed-to-lead habit helps too: if every new lead gets a reply within minutes, a missing one is noticed fast. See a speed-to-lead system for a small service business.

How to confirm the fix worked

Run the same three test submissions again, then pass or fail each one.

TestPassFail
Phone on mobile data, Gmail addressEntry in log and email in inbox (not spam) within 5 minutesMissing from log, or in spam, or later than 15 minutes
Own-domain addressSame as above, and Reply-To shows the visitorRejected or in quarantine
Ad blocker onForm still submitsForm silently fails
CRMLead appears with name, email, phone and sourceMissing, or missing fields
Next 7 daysWeekly audit numbers matchAny gap

Copy-ready checklist

  1. Submit three tests: Gmail, own domain, phone on mobile data. Note the times.
  2. Look in the form log. Present or absent?
  3. If absent: clear cache, read console errors, disable ad blocker, check size limits and (on Netlify) the form detection rules.
  4. If present but no email: check recipient spelling, mailbox space and forwarding.
  5. Check spam, junk and admin quarantine.
  6. Switch From to an address on your domain, with the visitor in Reply-To.
  7. Check SPF has one record and includes your form service; check DKIM is on; start DMARC at none.
  8. Check monthly limits on your form service.
  9. Check CRM required fields, daily limits and whether the form is recognised.
  10. Re-run the tests and start the weekly three-number audit.

When to ask for help

Ask your web person, host or builder support if: the form log is empty and the console shows errors you cannot read; the network request returns a 4xx or 5xx error code; SPF or DKIM changes are needed at your domain host and you are not comfortable editing DNS; or a CRM keeps rejecting leads with no clear message. Give them your test times, the three results and a screenshot of the console or network line. That saves a lot of back-and-forth.

How I'd approach this

I would treat a form that might be losing leads as urgent, because every missed enquiry is a customer who asked and heard nothing. First hour: run the three tests, find the hand-off that fails, and add a second notification address as a safety net. First day: fix the cause, then re-run the pass and fail table above. First week: start the weekly three-number count and keep it on your calendar for a month. If your form feeds a CRM, a text alert or a second system, test that link every time you change the site, because a redesign is the usual moment a form breaks.

If the fixes keep coming back, the real issue is often that the form, the email sender and the CRM were set up separately by different people. Blur Studio builds the joined-up version: forms, CRM and calendar connections that report their own failures, plus ongoing care. You can see what that includes. If your setup is simple, the checklist above is all you need.

Related guide: a landing page with a built-in form.

Questions people ask

Why is my contact form not sending emails?

The form usually saves the message but fails to deliver the email. Common causes are a wrong recipient address, a notification sent as if from the visitor (which many mail systems treat as fake), a spam folder, or a form service that hit its monthly limit. Check the form's own log first. If the entry is there, you have an email problem, not a lost lead.

Where do form submissions go if I do not receive the email?

Most form tools and website builders store each submission in their own dashboard, even when the email fails. Look for a submissions, entries or responses page. Ploy's documentation, for example, says submissions are saved and emailed, and that you can view them in the dashboard. Check your own tool's help page to find the equivalent.

Why do my form notifications go to spam?

Often because the email claims to be from the visitor's address but is sent by your web server, which fails the checks mail systems run. Send notifications from an address on your own domain and put the visitor in Reply-To. Then check that SPF and DKIM are set up for your domain. Google's sender rules (in effect since February 1, 2024) require SPF or DKIM for all senders to Gmail.

Do I need DMARC for a contact form?

Google requires DMARC only from bulk senders, meaning more than 5,000 messages a day to Gmail. A contact form is far below that. Still, a basic DMARC record set to none costs nothing and gives you reports, and it is wise to set it up after SPF and DKIM have run cleanly for at least 48 hours.

Can an ad blocker stop my form from working?

It can, if the form depends on a script that the blocker treats as tracking. The simple test is to turn the blocker off and submit again. If it works, ask your developer to send the form through your own domain or a plain HTML post, so it does not depend on blockable scripts.

How do I stop losing form leads from now on?

Count three numbers weekly: entries in the form log, emails received and leads in the CRM. They should match. Add a second notification address, and retest after every site change. For fast replies, see a speed-to-lead system for a small service business.

My form works for me but not for customers. Why?

You may be testing with a logged-in browser, on office wifi, with a fast desktop. Customers use phones, autofill, privacy settings and in-app browsers. Test on a phone on mobile data, with autofill on, and with an ad blocker. Also check whether your honeypot or CAPTCHA is blocking real people.

Is a CRM rejecting my leads?

Check whether the lead is in the form log and your inbox but not the CRM. Then look for required fields the form does not collect, daily limits (Salesforce Web-to-Lead allows 500 leads per 24 hours), and forms that the CRM does not recognise. Our guide on connecting your website to a CRM covers the setup.

More in this topic: Websites: fixing migration, DNS, forms, speed and CRM problems (6 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…