The site works but the leads stopped: the silent failure ordinary monitoring never sees

July 2, 2026 · 7 min read

There's a failure worse than the site going down. When a site is down, at least everyone quickly agrees there's a problem. But when the site is up, the ads are running, the form opens, the button clicks, the thank-you page appears — and the leads never arrive — that's the truly nasty one. Everything looks fine. Right up until the client writes: “We haven't had a single lead in three weeks. Did you change something?”

Why the contact form stops working — and nobody sees it

A lead form is a small thing on the page, but there's a whole chain behind it. The browser sends the data, the server accepts it, a script validates it, the mail module sends the email, anti-spam lets the message through, the CRM accepts the lead, the integration stays up, the thank-you page loads, the manager gets a notification.

If any link in that chain breaks, the business loses a lead. And the site looks completely alive the whole time: the homepage returns 200 OK, the form renders, the button clicks. A plain availability check notices nothing — because it only looks at “did the page load”, not at “did the email arrive”.

The most uncomfortable question a client can ask

When a client says “we're not getting leads from the site”, the agency rarely has a good, fast answer. The investigation begins: since what date, from which form, have you checked spam, is the mailbox accepting mail, did you send a test. All the right questions. The problem is they're being asked after the client noticed the drop.

And if the ad budget ran for a week while the form silently dropped every submission, the argument won't be about PHP or webhooks. It'll be about the money that already drained into a broken pipe.

Why a manual test at launch doesn't save you

You sent a test submission when the project launched, it arrived — great. But the form can break later, and it almost always breaks silently:

• after a CMS or plugin update;
• after mail settings change or SMTP limits kick in;
• after the site moves to different hosting;
• after a reCAPTCHA change or a template edit;
• after a new anti-spam filter starts eating the emails.

One test at launch isn't enough. If the form makes money, it needs to be checked continuously — as regularly as the site's uptime itself.

What a proper form check looks like

Not “the form page loaded”, but “the form actually accepts leads”. You need to submit test data and confirm the system responds as expected. Ideally — verify the lead's entire route: from the form to the email in the mailbox.

On a simple landing page, a synthetic submission plus a response check is enough. On an online store, the critical flows deserve their own checks: cart, checkout, payment, notifications. The core idea is the same: monitor the site as a business process, not as a picture in a browser.

How to explain this to a client

Don't lecture a business owner about POST requests, SMTP and IMAP. Say it in plain terms: “We'll be regularly verifying that the forms on your site don't just open, but actually accept leads. If the chain breaks, we'll know before you see the drop in enquiries.”

The owner isn't afraid of a technical error. They're afraid of paying for ads that lead into a broken pipe. And that's exactly the worry you're taking off their shoulders.

What Pingvera actually checks in a form

Pingvera doesn't just watch a site's availability — it checks that forms work, on two levels:

• Synthetic submission. The service POSTs test data into the form and verifies the site responds as expected — with the right status code and the key content of the thank-you page.
• All the way to the inbox. Pingvera sends a test lead with a unique marker and then finds that email in the mailbox via IMAP. So what's verified isn't “the form responded something” but “the lead email actually landed in the inbox”.

That's the crucial difference. Most monitoring tools stop at “the page loaded”. Pingvera follows the chain to the very end — to the mailbox where the leads drop in.

For an agency this is a strong support argument: most clients can't tell “the site is up” from “the site is selling”. And the gap between the two can cost a week's ad budget. If the form breaks, an alert beats a client calling to ask “where are our leads?”.

Frequently asked questions

Why did the contact form on the site stop sending leads?

A contact form can break silently after a CMS or plugin update, a change in mail settings, a hosting migration, a reCAPTCHA change, a template edit, SMTP rate limits, or a new anti-spam filter. Behind the Submit button there's a whole chain: the browser sends the data, the server accepts it, a script validates it, the mail module sends the email, anti-spam lets the message through. If any link breaks, the lead is lost — while the site still looks perfectly alive.

How do I verify that form submissions actually arrive?

It's not enough to check that the form page loads. You need to submit test data into the form and confirm the system responds as expected — and ideally, that the lead really lands in the inbox. Pingvera can do a synthetic form submission and an end-to-end check: it sends a test submission with a unique marker and then finds that email in the mailbox via IMAP. So what's verified isn't “the form responded” but “the email actually arrived”.

Can I monitor automatically that a form keeps working?

Yes. One manual test at launch isn't enough — the form can break later, and silently. Pingvera checks forms automatically every minute on every plan, including the free one, and sends an alert to Telegram or email the moment the chain breaks. The agency finds out about the failure before the client notices the drop in leads.

Read next: How to check if a website is really down, Know your client's site is down before they call, what to include in a monthly maintenance report, Pingvera vs WP Umbrella, and ManageWP client reports vs Pingvera.