Contact form "works" but leads disappear: the enquiry-system test for web designers

A contact form can pass every test a designer runs and still lose the lead. The form's job ends when the mail server accepts the notification. The enquiry's job ends when the customer is booked or told no. In Leadferno's 2024 test of 225 small-business forms, 4.8% of the forms were broken, but 42.6% of the inquiries sent through them never got a reply.¹ Most of the loss sits after the part designers test. The 10-point test below covers the whole path, from submit button to a second message from the business.

The symptom: "someone said they contacted us"#

The failure report arrives late and second-hand. Joe Seabrook, a web developer, describes the usual form of it: "Hey, someone said they contacted us but we never received anything."² By then the inquiry is weeks old and the customer has booked elsewhere.

Nothing alerted anyone in between. A Shopify merchant posted on 31 July 2024: "we are no longer receiving contact form submissions to our email. The last response I received was on June 3rd 2024."⁴ That is about eight weeks of silent loss with no error surfaced to the owner. A WordPress site owner wrote on 25 March 2022: "In the past 24 hours we are not receiving any notification emails of new leads, even though they have been saved."⁵

The failure can also run in the other direction. A thread in r/weddingplanning (10+ comments) describes a couple chasing a vendor who, it turned out, had answered: "she had replied and I just never got it."⁷ The form worked. The reply did not land.

The delivery path, hop by hop#

The path from a submit button to a booked customer has seven hops. Each one has its own failure mode, and only the first two are usually inside a designer's test plan.

Hops 1 to 5 are the wire. Hops 6 and 7 are a queue with no timeout. Leadferno's numbers put most of the loss in the queue: 4.8% of forms broken against 42.6% of inquiries unanswered, an average first human reply of 17 hours 49 minutes, and only 10.6% of businesses replying within one hour.¹

The misleading signal: "sent" means accepted, not read#

The success message on screen and the "sent" entry in the plugin log both report hop 2. They confirm that the handler passed the message to a transport. They do not confirm delivery to a folder a human reads, and they say nothing about a reply.

Designers test at launch, see the notification arrive in their own inbox, and sign off. That test runs once, at a quiet hour, to a mailbox the designer controls. It measures the happy path under conditions that will not hold in production: different mailbox, different filter history, a person who is not on a job site.

Seabrook lists one-time testing among the five reasons clients miss submissions, next to spam filtering, inbox neglect, single-channel dependency and email's slowness. His summary of the single-channel risk: "If the entire workflow depends on one thing (email), then all it takes is one small issue for a lead to be lost."²

Three hypotheses that were not the root cause#

When a client reports lost leads, three explanations get checked first. Each is worth checking. Each is usually not the main loss.

Hypothesis 1: the form is broken#

A broken form is real but rare. Leadferno found 4.8% of forms broken.¹ If your test submission succeeds and the entry is stored, the form is not the problem. Spam protection set too tight can block some real users, which a test from your own device will not show.

Hypothesis 2: DNS is wrong#

DNS and authentication failures are common and fixable. One Shopify merchant's missing notifications came back after adding an SPF record.⁴ A vendor guide's first fix is to "Set the 'From' field to your domain email."⁶ But a correct SPF, DKIM and DMARC setup only guarantees the notification reaches the mailbox. It does nothing for hop 6. Our contact-form leak guide has the record templates and the header check.

Hypothesis 3: the leads were junk#

Some form traffic is spam. That explains noise in the inbox, not silence in the sent folder. If real inquiries sit unanswered next to the junk, lead quality is not the cause.

Root cause: no state, no owner, no timeout#

The root cause sits above the mail protocols. The form system has no concept of an inquiry's state. A notification email is a stateless event: it arrives, and from then on nothing tracks whether it was answered, when, by whom, or whether anyone wrote a second time.

Seabrook's line for this is "A working form is not the same as a working enquiry system."³ In systems terms, a working enquiry system needs three properties the form lacks:

• An owner. One named person or process responsible for each inquiry.
• A state. New, answered, waiting on the customer, booked, or closed with a reason.
• A timeout. A deadline after which the next step fires: a reply, a follow-up, or an escalation.

Without those, follow-up is the first thing to go. Pied Piper's 2026 study found 72% of 3,211 home-services inquiries got no follow-up and 28% were offered a time.⁹ That is a hop 7 failure, and no form plugin is designed to see it.

How we could measure this across sites: a mystery shop of agency-built small-business sites would submit one realistic inquiry per site at a fixed time, then record hop-by-hop outcomes: delivered, first reply time, time offered, follow-up within three business days. Valet could run a study like that on 50 sites; we have not, and no result is reported here.

The fix: the 10-point enquiry-system test#

The 10-point test runs the whole path under production conditions. Run it at 17:00 on a Friday, because that is when the queue is least watched and an inquiry has to survive a weekend.

#	Check	Pass condition	Hop
1	Submit a realistic inquiry at 17:00 Friday from a phone on mobile data, using an outside Gmail address and a unique token (e.g. TEST-1003). Ask a question that needs a price and a date.	Success message; entry stored if storage is on	1
2	Check the sender address for an acknowledgement.	Arrives within 1 minute, from the client's domain, states when a person will reply	2
3	Search the client's mailbox for the token, all folders.	In the main inbox, not Spam or Promotions	4
4	Open the headers (Gmail: Show original).	spf=pass, dkim=pass, dmarc=pass; From on client domain; Reply-To is the customer	3
5	If the address forwards, check the final mailbox too.	Copy arrived; DKIM still passes	5
6	Check the second channel (log, sheet, or chat alert).	A copy exists outside email	2
7	Note who is named to read this inbox, and when.	One name and set check times, including weekends	6
8	Record the time of the first human reply.	Before Monday 12:00; note the hours elapsed	6
9	Read the reply.	Answers the question asked and offers a specific time or next step	6
10	Do not answer. Wait three business days.	A useful follow-up arrives, and the client can say what state the inquiry is in	7

Score it out of 10. Points 1 to 6 are yours to fix. Points 7 to 10 belong to the client, and the result belongs in the handover notes.

Point 6 comes from practice. A commenter on Seabrook's article, Pascal Cescato, reports logging submissions to a database with daily reports after similar silent failures.³ Seabrook adds that "Most clients respond faster to a WhatsApp message than an email, every single time,"³ which argues for a chat alert as the second channel.

Trade-offs and residual risk#

Every fix in the test adds a cost somewhere else. Name them in the handover so the client chooses with open eyes.

• Stored submissions are personal data. A database or sheet of inquiries holds names, emails and requests. Restrict access and set a retention period.
• Acknowledgements create a promise. An auto-reply that says "within 2 hours" sets an expectation the client must meet. Leadferno reports that 15.6% of the businesses it tested sent an auto-reply confirmation.¹
• More channels mean more places to forget. A chat alert helps only if it reaches the person who replies.
• Points 7 to 10 are outside your control. A designer can build a correct pipe and still hand it to an empty queue. The test makes that visible; it does not fix it.

The money case for running it is simple arithmetic. Illustration A client with 40 form leads a month at $1,500 average value, losing 42.6% to no reply, leaves about 17 inquiries and $25,000 of inquiry value unanswered each month. At a 25% close rate that is roughly $6,400 a month in bookings, or about $76,000 a year. A thread in r/Entrepreneur about cold-emailing Ontario small businesses (140+ comments) describes the same failure seen from outside: "sending someone to a broken contact form while a client is watching."⁸ For agencies whose clients get the leads and drop them, see the agency's lead follow-through problem.

Where Valet fits#

Valet covers hops 6 and 7 without replacing the form. The client forwards the form's notification address to a private Valet address; nothing is migrated, and replies go out from the client's own address once the domain is verified. Valet answers from the client's own facts, offers real times from their calendar, and gives every inquiry a state, a next step and a time in the Valet Inquiry States. Follow-ups stop at the Valet follow-up cap of two by default, and every reply has a Valet receipt. Money questions and complaints go to the owner. To see what a client's last 10 to 20 form inquiries actually got, start with the free lead check.