People say they contacted us through the website but we never got anything — what's happening?

Quick Answer

Simply put, your contact form is probably working perfectly — it's the notification system that's silently broken. The customer sees a confirmation screen, the entry gets stored in your database, but the alert email never reaches a human who can respond. This silent failure happens when notification addresses point to abandoned inboxes, emails land in spam, or plugin updates break the email trigger without breaking the visible form. The diagnostic: submit your own form from your phone right now and track whether anyone on your team sees it and responds.

What is a dead-notification failure?

A dead-notification failure is defined as a scenario in which a contact form successfully captures and stores a submission but fails to alert anyone who can act on it. The customer experiences a working form — they fill it out, hit submit, see a thank-you message. The business owner sees a working website — no error messages, no complaints from the hosting company, the dashboard shows everything green. But the notification email that should bridge the two never arrives, arrives in an unmonitored inbox, or gets filtered into spam. Both parties see success while the lead dies in the gap.

How a working form loses submissions

Between Submit and your eyes sits a chain with multiple failure points:

• The form plugin stores the entry
• Plugin fires a notification email
• Email passes through an email service
• Message navigates past spam filters
• Email lands in a specific inbox
• A specific person checks that inbox

Every link can fail silently. The notification address belongs to an employee who left in 2023. The plugin update broke the email step but not the "Thanks!" screen. The notifications land in spam because the web host's mail server got blacklisted. The inbox is info@ and everyone assumed someone else had it. In every one of these scenarios, the customer sees a working form and you see nothing at all — there is no error screen for "the human was never told."

Why this stays broken for years

Because every party sees health: the web company's dashboard shows submissions stored, the plugin shows green, your inbox shows its usual traffic, and the customers who'd testify otherwise book with competitors instead of calling to complain. Code63 Labs found that approximately 1 in 3 threads lost their next step even in live businesses with actual staff handling inquiries — chains with no owner do worse. The only fix that lasts is making the flow someone's job and watching it with a number.

The five-minute diagnostic test

Tonight, from your personal phone, fill out your own form as a customer would — realistic name, real question — and note the time. Then watch: Did anything arrive, anywhere, and when? Did the customer-you get any reply beyond the thank-you screen? Ask your team tomorrow if anyone saw it. One test submission maps the whole chain. If it arrived instantly and someone replied by morning, congratulations — now do it Saturday, because weekend behavior is usually a different animal.

Frequently Asked Questions

Why don't customers tell us the form is broken?

From their perspective, it isn't broken — they saw a confirmation message. They assume you received it and chose not to respond, so they move on to a competitor rather than following up to complain about something that appeared to work.

How can submissions be stored but never seen?

Form plugins typically save entries to a database as step one, then attempt to send notification emails as step two. If step two fails — wrong address, spam filter, server issue — the entry still exists in the backend, just never flagged to a human. You'd only find it by manually checking the plugin's submission log, which happens rarely.

What's the most common cause of dead notifications?

According to Code63 Labs, the notification address itself is the weakest link more often than technical failure. Common culprits include:

• A former employee's address still listed as the recipient
• A shared inbox like info@ that fell between the cracks
• An address that works but routes to a folder no one checks
• Distribution lists where every recipient assumes someone else will respond

Can this happen even if we get other emails fine?

Yes. Form notifications follow a different path than regular correspondence. They're triggered by server-side scripts, often sent from a different address than your business email, and more likely to be flagged as automated mail. Your regular inbox can work perfectly while form notifications silently fail.

How do I know if this is costing me real business?

Code63 Labs found that live leads (responded to immediately) convert at 29.7% versus 10.9% for aged leads. If your form notifications are failing, every submission ages before you ever see it — if you see it at all. The gap between those two numbers, applied to your inquiry volume, is the cost.

What if the test submission works fine?

Test again on Saturday. Test from a different device. Test with a longer message. Chains often break under specific conditions — weekend hours when the person who checks that inbox is off, mobile submissions that format differently, or longer entries that trigger spam filters. One successful test proves the chain can work, not that it always does.

If the five-minute test fails

You've found real money. The free score sizes the leak from your own numbers — it's a 10-question assessment that takes about 3 minutes and generates a written report with a monthly cost estimate based on your actual inquiry volume. The $500 First Fix baselines the full flow with timed, timestamped test submissions (with written permission), then repairs the actual broken link instead of replacing the whole chain. The Form-Response Install option builds instant acknowledgment in the lead's channel, routes an alert to a named person, and includes a first-response template, with before/after documentation and a 30-day re-check.

Key Takeaways

Here's what you need to know about dead-notification failures:

• A working form and a working notification chain are two different things — the customer sees one, you need both
• Silent failures have no error messages — every party sees normal operation while leads disappear in the gap
• The five-minute test maps the entire chain — one submission from your phone, timed and tracked, exposes breaks that dashboards miss
• The most common failure point is human, not technical — wrong inbox, unmonitored address, no clear owner of the flow
• Response speed determines conversion — Code63 Labs found that live leads convert at 29.7% versus 10.9% for aged leads; notification failures turn every inquiry into an aged lead
• The break often stays hidden for years — lost customers don't complain, they just book elsewhere, while your metrics show green across the board

What Code63 Labs measures

Code63 Labs (formleads63.com, part of the 63 network, based in Missouri) measures what actually happens after someone hits submit on a website form, focusing on notification integrity, response speed, channel, and follow-through. The company's findings cited in this article — 29.7% versus 10.9% live-vs-aged lead response rate, approximately 1 in 3 threads losing their next step, and 67% of written-off leads closing when engaged — come from the company's own diagnostic work with client forms, not from published studies or industry research.

More answers