Skip to content
OrionX
An open silver laptop with a dark blank screen sitting in the centre of a light wooden desk, with gold file organisers on the left and a small gold geometric ornament and a succulent in a white pot on the right
Web Development

Your website form said "Thanks, we'll be in touch." Nobody got the enquiry.

OrionX Editorial Team11 November 20268 min read

A new customer rings and, halfway through the call, mentions they filled in your website form three weeks ago. Nobody replied, so they rang someone else first. You check the inbox. Nothing. You check junk. Nothing there either.

The form told them "Thanks, we'll be in touch." As far as the website was concerned, the job was done.

That's the problem with website forms. When they break, they usually break quietly. The page still loads, the button still works, the visitor still sees a thank-you message. The only sign anything is wrong is the work that doesn't turn up.

Why the thank-you message proves nothing

Most website forms do two separate jobs. First they accept the visitor's details. Then they hand an email to something that's meant to deliver it to you. The thank-you message usually only confirms the first job.

On WordPress, which runs a lot of small business sites, that handover goes through a function called wp_mail. WordPress's own developer documentation is blunt about it: a successful result "does not automatically mean that the user received the email successfully. It just only means that the method used was able to process the request without any errors."

In other words, the website handed the email to the server, the server said "got it", and the form said thanks. What happened after that, nobody checked.

The usual ways enquiries go missing

The email is the only copy. Plenty of form plugins don't keep submissions at all. They send an email and forget. Contact Form 7, one of the most widely used WordPress form plugins, says so in its own documentation: it "doesn't store submitted messages anywhere. Therefore, you may lose important messages forever if your mail server has issues or you make a mistake in mail configuration." If the email doesn't arrive, the enquiry is simply gone.

The web server sends the email, badly. By default WordPress sends through the server's built-in PHP mail function, often from an address like wordpress@yourdomain. Gmail's sender rules require every sender to personal Gmail accounts to set up SPF or DKIM for the sending domain and have valid reverse DNS, and say unauthenticated messages may be marked as spam or rejected outright. On shared hosting, Google also notes that the behaviour of every sender on a shared IP address affects the reputation of all of them. So your form notification can be judged by what the website next door is sending. (We covered the domain side of this, SPF, DKIM and DMARC, in our post on invoices landing in junk.)

It goes to an address nobody reads. The form was set up years ago to email the office manager who has since left, or an alias that forwards somewhere that no longer exists, or a shared mailbox with a rule that files anything with "enquiry" in the subject into a folder no one opens.

The spam protection blocks real people. Spam protection is necessary, but it's another thing that can fail. Cloudflare Turnstile, a common CAPTCHA replacement, only works on hostnames listed against its key. If the site moves domain, or switches from www to the bare domain, every visitor gets error 110200, "Domain not authorized", and Cloudflare's docs list it as not retryable. The form looks fine to you because you're not filling it in. Going the other way, an over-keen spam filter can quietly delete genuine enquiries along with the junk.

An update or server move breaks it. A Melbourne web agency, xCreative, wrote up the problems it found and fixed across client sites in October 2026: a form plugin whose settings expired once page caching was switched on (every submission then failed, and the plugin stored nothing), a Turnstile key rejecting a site after a domain change, and websites moved to new servers that couldn't send mail at all. None of these announced themselves. Someone had to go looking.

Why "check the junk folder" isn't a fix

Every one of these failures has the same shape: nobody knows a lead is missing, because a missing lead looks exactly like a quiet week.

And in most small businesses nobody owns the form. Marketing paid for the website, someone in the office reads the emails, whoever built the site moved on, and the hosting company only cares whether the server is up. The form sits in the gap between all of them. It gets tested on launch day and then never again, until a customer happens to mention it.

What you can do this week, without new software

1. Fill in your own form, properly. From your phone, on mobile data, using an email address outside your business (a personal Gmail is good). Then do it again from a desktop. Time how long the notification takes to arrive, and where it lands: inbox, junk, a folder, nowhere.

2. Find out where submissions are stored. Log in to the website and look for an entries or submissions list. If there isn't one, the email is your only record. That's worth fixing first.

3. Check who the form emails, and the reply-to. Look at the actual recipient address in the form settings. Is it a person who still works there, or a mailbox someone checks every day? When you hit reply on the notification, does it go to the customer, or back to wordpress@yourdomain?

4. Check the email passed authentication. In Gmail, open the test notification, choose "Show original" and look for SPF and DKIM both showing PASS. If either fails, the next one might not arrive.

5. Put a test in the calendar. Once a month, plus after every website update, plugin update, domain change, hosting move or email change. Name the person who does it.

That will catch most of today's problems. The weakness is the same as any manual check: it relies on someone remembering, and a form can break the day after you tested it. That's the part software can take over.

What OrionX would build

We'd turn your website form from "sends an email and hopes" into a small enquiry pipeline that records everything and tells you when it stops working. Roughly:

1. Store first, then send. Every submission is written to a database before any email is attempted, and the visitor gets a reference number on screen and in their confirmation email. If email fails for a week, nothing is lost: the enquiries are sitting in the queue.

2. Proper, authenticated delivery. Notifications go out through a transactional mail service set up on your own domain with SPF and DKIM, From your domain and Reply-To the customer, not through the web server. Delivery, bounce and deferral events come back and are logged against each enquiry, so you can see "sent, delivered 09:14" or "bounced: mailbox doesn't exist" next to each one. Failures retry and get flagged.

3. Spam held, not deleted. We verify reCAPTCHA v3 or Turnstile on the server, checking the score, the expected action and the hostname, and add a hidden honeypot field and a few simple rules. Google's own guidance for reCAPTCHA v3 is to act behind the scenes rather than block outright, so low-scoring submissions go to a "held" list that someone skims weekly. A real customer who trips the filter isn't silently thrown away.

4. A robot that fills in your form every day. A scheduled test (a headless browser) submits your real, live form, then checks each step: stored in the database, sent, arrived in a test mailbox, SPF and DKIM passed. If any step fails, two people get an alert. We also add a silence alert: if real enquiries drop to zero for longer than is normal for your business, someone hears about it, because that's often the only symptom.

5. An enquiry queue with an owner. Each enquiry lands in a simple queue with an owner, a status and a first-response time, with a ping to the right person during business hours and a nudge if it's sat untouched. The inbox is still there, it's just no longer the system of record.

6. Know where enquiries come from. Each submission records the page it came from, any campaign tags (UTM parameters, Google Ads click ID) and device type. A weekly report shows enquiries received, spam held, median first-response time and anything still unanswered.

7. A change guard. The same end-to-end test runs automatically after plugin updates, site deploys, domain changes and mail changes, and the form's configuration is kept in version control so a bad edit can be rolled back.

8. Customer details handled properly. Stored enquiries contain people's contact details, so they sit behind a login, have a retention period you choose, and can be exported or deleted for a single person when asked.

Nothing here is exotic: a small database, an authenticated mail service, a scheduled browser test and a simple queue. It works with the website you already have. Most of the value comes from the form finally being something that someone monitors, instead of something that gets tested at launch and then trusted forever.

Want to know if your form actually works?

If you're not completely sure every enquiry from your website reaches a person, have a chat with us. It's free. If it looks like a fit, we'll build one free, tailored demo for your business: we'll run an end-to-end test against your live form, show you exactly where a submission goes (and where it could get lost), and demo the store-first queue and daily monitor on a copy of your form. Then you can decide if it's worth doing properly.

Book a free chat →


Sources

Trying to solve a problem with AI, cloud, or software? Let's talk it through.