The silent lead leak
Contact Form Stopped Sending Leads: Find the Broken Handoff Before Another Day of Inquiries Disappears
Nobody calls to tell you the contact form is broken. The form says thank you, the customer waits a day, then calls someone else. The first symptom is a quiet week, and the usual explanation offered is the economy.
November 20, 2026 · 10 min read
Host moved, sender records never updated: export the 41 entries and start calling
The short answer
When a contact form stops sending leads, submit a test from your phone, then check where the form stores entries before you check email, because a form that saves entries but fails to notify you has lost nothing yet. Next search spam folders, confirm the recipient address, look for recent changes to your domain's email records, and test any CRM connection. Export saved entries before replacing anything.
On this page
- Five handoffs between a visitor's thumb and your inbox
- The first hour of a lead leak, minute by minute
- Which runner dropped the baton: a symptom table
- Tempting fixes that delete the leads you were trying to save
- Places a lost inquiry can still be hiding
- Our part: same business day, priced before we touch it
- A form that clocks in every morning
Five handoffs between a visitor's thumb and your inbox
A contact form looks like one thing. It is a relay. The visitor's browser hands the message to your website. The website saves it somewhere, or does not. It hands a copy to a mail server. The mail server hands it to your inbox, where a spam filter decides whether you ever see it. Many sites add a fifth runner that passes the lead to a CRM or a spreadsheet. Every handoff is a place for the baton to hit the track.
The good news hides in that relay. If the website saved the entry and only the email failed, every lead from the dark period is still sitting on your server, waiting to be called back. If nothing was saved, the clock matters more, because each hour is another inquiry gone for good. The first hour is about finding out which of those two situations you are in.
Platform specifics live elsewhere on this site. Squarespace owners should read Squarespace forms not sending, and store owners missing order confirmations should read WooCommerce order emails not sending. This page is the platform-neutral emergency version: what to check in which order, what not to break while checking, and how to win back the people who already gave up on you.
The first hour of a lead leak, minute by minute
- 1
Minute 0: find the last lead that really arrived
Search your inbox and CRM for the most recent genuine inquiry. The gap between that date and today is the window of missing leads, and it tells you how hard to work the recovery later.
- 2
Minutes 5 to 10: send a test you can recognize
Fill in the live form on your phone, on cellular data, with a name like Test 1117 Phone. Note what happens: a thank-you message, a spinner that never stops, an error, or a button that does nothing. Each points to a different handoff.
- 3
Minutes 10 to 20: look in storage before email
Open the form's entries screen in your site admin or platform dashboard. If your test and other recent inquiries are there, nothing is lost yet. Export them to a spreadsheet now, before anyone changes a setting.
- 4
Minutes 20 to 30: search every place an email can hide
Search the inbox, spam, junk and any quarantine folder for the test name. Check the form's recipient address. Old addresses, typos and the mailbox of someone who left last spring are common, and boring, culprits.
- 5
Minutes 30 to 45: ask what changed with your domain
Did the site move hosts, did someone edit DNS, did the email provider change? Those moves can break the records that let your site send mail on your domain's behalf. Write down who made each change and when.
- 6
Minutes 45 to 60: test the forward to your CRM
If leads should land in a CRM, spreadsheet or email tool, open the connection settings and look for warnings, expired authorizations or error counts. Note any status code shown. It tells the person fixing it which way to look.

Which runner dropped the baton: a symptom table
Match what your test did to a row. The row tells you where the break is, and roughly who should fix it.
| Handoff | What the test shows | Usual cause | Who fixes it |
|---|---|---|---|
| Browser to website | Button does nothing, or a spinner forever | A script error, a spam widget failing to load, a consent tool blocking the form | Your web developer |
| Website to storage | Thank-you message, but no entry saved | A plugin or platform update, a server error, a full database | Your web developer or host |
| Website to mail server | Entry saved, no email sent | Changed mail settings or an expired mail account password | Your web developer |
| Mail server to inbox | Email sent, never seen | Missing or broken sender records, a strict spam filter, the wrong recipient | Whoever manages your domain's email |
| Website to CRM | Email arrives, CRM stays empty | An expired connection, a renamed field, too many requests | Your developer or the CRM's admin |
The fourth row causes most of the arguments, because three different vendors can each say the problem belongs to someone else. Cloudflare's DNS record types reference describes the records involved: an SPF record lists the IP addresses and domains allowed to send email for your domain, and DKIM signs email so receivers can check it is genuine. When a site moves to a new host and nobody adds the new server to those records, receiving mail systems have good reason to distrust its messages. Our page on email that stopped after a website move covers that repair.
The fifth row has its own language. Under the IETF's RFC 9110, a 401 means the request lacked valid credentials, which in practice is usually an expired token or a changed password. A 403 means the server understood the request and refused it, often after a permission change. A 429, defined in RFC 6585, means too many requests in a given amount of time. Each is a different fix, and our page on a broken API integration goes further.
Tempting fixes that delete the leads you were trying to save
The most common bad idea arrives fast: rip out the form and install a new one. It looks decisive. It can also delete the very entries that were sitting safely in storage, and it destroys the evidence of what broke. Here is the short list of things to hold off on until the export is done and the cause is known.
- Deleting or replacing the form, or uninstalling its plugin, before exporting every stored entry.
- Turning spam protection off entirely. Within days the inbox fills with junk, and the real inquiries drown again in a different way.
- Editing MX records to fix a form. Cloudflare's reference says an MX record is required to deliver email to a mail server, so a wrong edit can stop every email to your domain, not just the form's.
- Giving a stranger from a forum your email admin password to look at it.
- Pointing the form at a personal Gmail address as a permanent fix. It hides the problem until that person leaves.
Places a lost inquiry can still be hiding
Even when the entries screen is empty, the lead may have left tracks. Check these before you write the period off. Some hold the full message, some only prove a message existed, and that proof alone tells you how big the leak was.
The form's own entries
Most form plugins and site builders keep a copy of each submission in the site's database or dashboard, separate from the email. This is the first and best place to look.
The mail service's logs
If the site sends through a mail delivery service, its activity log can show messages that were sent and then bounced or blocked, with the reason attached.
Delayed mail queues
The IETF's email standard, RFC 5321, says that when delivery hits a temporary error the message must be queued and retried later. Some missing mail is late, not lost.
The CRM's failed records
Many CRMs and automation tools keep a log of rejected or failed records. A lead that bounced off a required field may be sitting in that log with its details intact.
Your analytics conversions
If form submissions are tracked as conversions, the count shows how many people pressed submit during the outage, even if their details are gone.
If submissions are not tracked as conversions, that is the second lesson of this week. Conversion tracking setup is how a form that goes quiet shows up as a line falling to zero, instead of a vague feeling that business is slow.
Our part: same business day, priced before we touch it
We respond the same business day, during the hours on our contact page. We test every handoff, recover what can be recovered, fix the break and test again from a phone and a desktop before calling it done. Broken forms are one of the most common jobs behind our fixing broken websites service, and the form and script repair page covers the wider work.
On WordPress, the repair is a fixed-price Fix it now job, paid online: a theme, builder or plugin conflict is $199, and a WordPress error fix is $149. We start within one business day of payment, with a full refund if we can't fix it. See WordPress repair for the full list. Squarespace, Wix, Shopify, custom sites and CRM connections are from $575, depending on complexity, with a written estimate before work starts. Connections to a CRM or other API integrations are restored the same day once we have access. The emergency website repair page lists the logins we will ask for, and emergency pricing explains what moves a quote.
Call us today if
- Entries are missing from storage as well as email
- Your test produces an error or the button does nothing
- Leads stopped after a website move or DNS change
- The CRM connection shows errors you cannot clear
You can likely fix it alone if
- The test landed in spam: mark it safe and add a filter
- The recipient was an old address: change it and retest
- Entries are saved and only the email failed: export and call
- The CRM asks you to reconnect: sign in again and test
A form that clocks in every morning
The fix for silence is noise you control. Send every submission to two places, such as storage plus an inbox, or two inboxes owned by different people. Put a test submission on someone's weekly calendar, from a phone, with a recognizable name. Set an alert on the conversion count so a day of zero is a message, not a mystery. If spam is what made someone switch protection off in the first place, our post on why WordPress forms get spammed explains a calmer fix.
Forms often break along with something bigger. If the whole site is failing, start with website down: what to do first. If email to your domain stopped too, read the domain and DNS emergency page. If customers also cannot pay, see checkout and payments down. A hosting and maintenance plan from $55 a month puts someone on watch. DataCram is a web studio in San Antonio, Texas, building for the web since 1999, working with businesses across the US by phone, video and a shared project page. See our work, the full emergency repair section, or call (210) 346-0848.
Questions owners ask in an emergency
The form saved or accepted the message, and a later handoff failed: the email was never sent, it was sent to the wrong address, or a spam filter caught it. Check the form's stored entries first. If the submission is there, the lead is safe and the problem is delivery, which is usually sender records or the recipient setting.
Often, yes. Many form tools keep each submission in the site's database or dashboard even when the email fails, so export those entries and call the people back. Mail service logs and CRM error logs can hold more. If nothing was stored at all, your analytics conversion count can at least show how many inquiries were missed.
A new server often sends mail from a new address that your domain's sender records do not list. Receiving mail systems then distrust the messages. Adding the new server to your SPF record and setting up DKIM signing usually fixes it. Change DNS records carefully, because a wrong MX edit can stop all email to your domain.
On WordPress it is a fixed-price Fix it now repair: $199 for a theme, builder or plugin conflict or $149 for a WordPress error, with a full refund if we can't fix it. Other platforms and CRM connections are from $575, depending on complexity, with a written estimate first. We respond the same business day.
Not until you have exported every stored entry and know why the old one failed. Swapping plugins can delete saved submissions, and if the cause is your domain's email records or a CRM connection, the new form will fail the same way. Find the broken handoff first, then decide.
Send submissions to two destinations, run a test submission from a phone every week, and track form submissions as conversions with an alert when the count drops to zero. Those three habits turn a silent failure into a message you see within days.
Keep reading
- Silent failures, real costsAPI Integration Stopped Working? Read the Status Code Before You Touch a KeyCRM or API integration stopped syncing? Read the 401, 403 or 429, find what changed, replay what failed, and get the connection restored the same day.
- The website offerEmergency Website Repair: Who to Call When the Site Is Down, and What Happens After You DoWebsite down and no one to call? A same-business-day reply, fixed WordPress repair prices, from $575 for other platforms, and the checks before we sign off.
- The software offerEmergency Software Repair: Triage, Containment and a Written Root Cause for Broken Custom SoftwareCustom software or a web app broken today? Triage, stop the damage, restore, find the root cause, and a written estimate first. From $575, depending on scope.
- The mobile offerEmergency App Repair: An iOS and Android Developer for Crashes, Store Trouble and Expired CertificatesApp crashing, rejected or pulled from the store? Crash triage, store fixes, certificates and the access we need, from $575 with a written estimate first.
- Prices, in writingEmergency Website Repair Cost: Fixed WordPress Prices, From $575 for Everything Else, and the Fees That Are Not OursEmergency website and app repair costs: five fixed WordPress prices, from $575 for other work, what raises an estimate, and store fees as of November 2026.
- The first fifteen minutesWebsite Down? The First 15 Minutes, Before Anyone Touches AnythingYour website is down. Check it from outside, rule out renewals and DNS, read the error code, and skip the moves that turn a short outage into a long one.
- Everything in Emergency RepairSee the section
From the Insights desk
- Why Your WordPress Form Gets Spammed — and the Fix That Doesn't Annoy Real CustomersForm spam isn't the problem — it's what the spam does: buried leads, a poisoned CRM, and an inbox you've learned to ignore. Why CAPTCHAs make it worse, and the silent fix that stops bots without costing you real customers.
- Next.js or PHP? The Better Question Is Who Patches Your SiteApache, NGINX and PHP all shipped urgent fixes between November 11 and 19, 2026. PHP is not the villain, and Next.js has patch days too. The real difference is who installs the fix, how fast, and how much of your site runs code at all.
Get your leads flowing again
Tell us what platform the form runs on, when the last real lead arrived and what changed recently. We reply the same business day with a fixed price or a written estimate.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.