LEAD GENERATION

The enquiry delivery test: how to check your WordPress forms actually deliver

There's a category of website fault that produces no error message, no bounce, and no complaint: the enquiry form that submits successfully — for the visitor — and delivers nothing to you. The visitor sees "Thanks, we'll be in touch." You see nothing, because there's nothing to see. The homeowner assumes they were ignored and calls the next company on their list.

In our experience across WordPress sites, this is the most common serious fault on sites that otherwise "work fine." It usually starts silently: a hosting migration changes how email sends, a plugin update alters a setting, a notification address belongs to someone who left, or a spam filter starts eating the messages. Because some enquiries still get through — the phone keeps ringing — the gap reads as "the website doesn't generate much," which owners treat as a marketing problem and solve by spending more on ads into a broken funnel.

Why receiving some enquiries proves nothing

Form failure is rarely all-or-nothing. The patterns we see most: one form breaks while another works (the quote-request form fails, the general contact form doesn't); one device breaks (mobile Safari fails, desktop works); one condition breaks (submissions with attachments fail, plain ones deliver). You cannot detect a partial failure by noticing that enquiries still arrive. You can only detect it by testing every path, on more than one device.

The 15-minute test

1. List every enquiry path on your site: every form (contact, quote request, booking, footer), plus your click-to-call and email links. Most sites have three to six paths; owners usually remember two.
2. Send a clearly labelled test through each one — put the word TEST and the date in the name and message fields so nobody wastes time on it. Use a personal email address, not your business one.
3. Repeat the two most important forms from a phone, on mobile data rather than Wi-Fi, in Safari if you have an iPhone. Mobile-only failures are common.
4. Now check delivery. Did each test arrive? Where — whose inbox? How long did it take? Check the spam folder specifically: delivered-to-spam is a failure with extra steps.
5. Check the visitor side: did you get any acknowledgement email as the "customer"? If a homeowner hears nothing instantly, many assume it didn't work and re-send — or move on.
6. Tap the phone number on your own site from a phone. Does it actually dial? Untappable numbers are one of the most common mobile faults and cost real calls.

Reading the results

Every test arrived, quickly, to an inbox someone owns, with an acknowledgement to the sender: your delivery layer is healthy — this test is worth repeating quarterly, because the failures are silent when they start. Anything else — a missing test, a spam delivery, a form that errored on mobile, an address nobody checks — is a live leak. Each path you found broken has been broken for every real homeowner who used it since it failed.

Fixing it — and keeping it fixed

The fixes are usually unglamorous: proper transactional email sending instead of the server default, delivery to more than one address so nothing hinges on a single inbox, an instant acknowledgement to the visitor, and — the part almost everyone skips — a scheduled re-test, because the next plugin update can silently break it again. If you'd rather have all of it measured for you, delivery testing across every path is part of the free Otto Growth Check: no cost, no obligation, and you keep the findings either way.

Related arms