A contact form can fail in a way that looks like success. The visitor fills it in, sees “Thanks, we’ll be in touch,” and leaves. The page did its job. Somewhere after that—the form service, the email, the forwarding rule, the CRM sync—the lead stopped. Nobody gets an error. The only symptom is that it gets quiet, and quiet looks exactly like a slow week.
I learned this the uncomfortable way in my own business. Alerts I depended on were sent correctly and landed in one inbox, but the forwarding rule that was supposed to pass them to the inbox I actually read had stopped working. Every system reported success. The messages simply never reached me until I went looking.
So here is the test I now run, and the one I’d run on your site.
The 5-Minute Test: Follow One Fake Lead All the Way Through
Do this from a private/incognito browser window on your phone, not while logged in to your own site.
- Submit the form like a real prospect. Use a name you’ll recognise (“Test lead — your initials”) and an email address that is not your business address.
- Check the destination, not the confirmation screen. Did the notification arrive within five minutes in the inbox someone on your team actually reads every day?
- Check spam and forwarding. If it isn’t there, look in spam, then in any inbox the form sends to first. If it landed somewhere nobody reads, you’ve found your leak.
- Check the next hop. If leads are supposed to reach your CRM, email platform or a spreadsheet, confirm the test lead appeared there too, with the right fields (name, email, message).
- Check the reply. If the prospect should get an automatic confirmation or first reply, did the test address receive it?
If any step fails, you’ve found a potential lead leak. The next question is how long that step has been broken and whether any real inquiries were affected.
The Usual Suspects (In the Order I’d Check Them)
- The form service’s destination email was set to an address nobody monitors, or was never confirmed.
- A forwarding rule between inboxes stopped delivering (some email providers limit forwarding on free plans).
- Spam filtering started catching the notifications because they all look alike.
- The CRM/automation step (Zapier, Make, a native integration) was switched off, lost its login, or started failing after a field was renamed—many tools pause a workflow after repeated errors and tell you only by email.
- A site change (new page builder, new form, a redesign) replaced the form but not its connection.
- Anti-spam settings (CAPTCHA, honeypots) are blocking real people, not just bots.
How to Stop It Happening Silently Again
A one-time test only tells you about today. The fix is a check that runs on a schedule and tells you when it fails:
- Put the test on your calendar weekly (5 minutes, same fake lead, same checklist). Cheapest option; relies on you remembering.
- Use a free uptime/keyword monitor on the pages that matter (contact page, booking page, checkout link) so you’re emailed if the page or the button disappears.
- Send leads to two places, e.g. the inbox and a spreadsheet or CRM, so a failure in one is visible in the other.
- Watch the count. If you normally get a few inquiries a week and you get none, treat it as a possible break, not a slow week, until you’ve run the test. A quiet inbox also slows the first reply that decides most deals.
For my own sites I use small scheduled checks that monitor key pages and links and alert me when something is wrong. They’re simple, inexpensive to run, and remove some of the guesswork from wondering whether a critical page is still working.
If you’d rather not dig through form settings, inbox rules and integrations yourself, our free AI Agent Scan traces how a lead actually moves through your business today—from the form to the first reply—and shows you the one place it’s most likely leaking.
Get Your Free AI Agent Scan →