The Enquiry That Never Arrived

Why this failure is invisible

A form that breaks does not usually break visibly. The page still loads, the fields still accept text, and the thank you message still appears.

The failure happens after that, in the sending, where nobody is watching.

The customer believes they contacted you. You believe nobody has been in touch. Both are behaving reasonably and there is no error anywhere either of you would see.

Which is why these outages run for months rather than hours. Nothing raises its hand.

The ways it fails

• The destination address changed and the form still points at the old one.
• Mail from the server is being rejected by the receiving provider.
• The messages land in junk and nobody checks that folder.
• A plugin update broke it, quietly, during routine maintenance.
• The form points at the developer's address, left over from testing.
• A hosting change altered how mail is sent from the site.

The fifth is the classic launch failure. The third is the most common ongoing one, and it is particularly cruel because the messages did arrive and were simply never seen.

A worked example

An accountant whose enquiry volume dropped over the winter, which she attributed to the season.

In March somebody mentioned they had contacted her through the site in November and never heard back. That prompted a test.

The form had been sending to an address that was decommissioned when the practice changed email providers in October. Every submission since had bounced into nothing.

Four months, and no way to recover the messages or know who had sent them.

The fix took ten minutes. What she could not fix was the four months of people who had made contact, heard nothing, and formed a view about the practice.

The seasonal explanation had been plausible enough to stop anybody investigating, which is what makes this failure durable.

Testing it properly

1. Use an address unconnected to the business, a personal one is fine.
2. Fill the form in as a customer would, including the awkward fields.
3. Submit it and note the time.
4. Check the destination inbox, including junk.
5. Reply to the message and confirm the reply reaches the test address.
6. Do it on a phone as well, since mobile layouts sometimes break submission.

The fifth step catches a separate problem: a form whose reply-to address is wrong means you cannot answer the enquiry even when it arrives.

Testing from inside the business proves less than people think. Internal mail frequently behaves differently from external.

Not relying on email alone

The structural fix rather than the routine one.

Email is a delivery mechanism with several points of failure. A form that only emails has no record of what it sent.

Better arrangements store the submission as well: in a database on the site, in a spreadsheet, or in whatever system you already use.

Then a delivery failure costs you a delay rather than the enquiry. The message is still there when somebody looks.

This is not complicated to add and it converts a silent total loss into a recoverable one.

The counter-case

Where storing submissions is the wrong choice.

If the form collects anything sensitive, storing it on the website creates a record on a system that is publicly reachable and may not be secured for the purpose.

Health information, financial details, anything a customer would consider confidential. For those, delivery to a secure destination without retention on the site is the better arrangement.

The middle position is storing only enough to recover the enquiry: name, contact details, timestamp, and a note that a message was sent, without the message body.

Which of those is right depends on what you collect, and it is a decision worth making rather than defaulting to whatever the plugin does.

Monitoring rather than remembering

A monthly test depends on somebody remembering, which lasts about three months.

Better: an automated check that submits the form periodically and alerts you if nothing arrives.

Simpler still: note roughly how many enquiries a normal week produces, and treat an unusually quiet fortnight as a prompt to test rather than a slow period.

Most businesses have an intuition about their normal volume. The failure is not acting on it, because a quiet spell always has a plausible explanation.

Confirming to the customer

A second protection with a different benefit.

An automatic acknowledgement to the person who submitted does two things. It reassures them, and it gives them a record showing they contacted you.

It also creates a second delivery path. If the acknowledgement fails to reach them, they will often try again by phone, which surfaces the problem.

Keep it short and human. A confirmation saying you will reply within a stated time is more useful than one restating what they typed.

The other silent routes

The form is the usual culprit and it is not the only one.

A voicemail box that is full rejects callers with no record. An email address on the site with a typo bounces mail nobody sees. A phone number with a wrong digit rings somebody else entirely.

Each fails the same way: the customer believes they reached you, and nothing on your side registers the attempt.

Which is why the sensible test covers every route at once. Phone your own number from an outside line, leave a voicemail, send a message to every published address, and submit every form.

Half an hour, once a quarter, and it covers the whole surface rather than the one part somebody happened to think about. Put it in the diary, because it is exactly the sort of task that never becomes urgent until it is expensive.

What to do if you find a gap

Practical rather than dramatic.

Fix the delivery first. Then look at whether anything is recoverable: server logs sometimes retain enough to identify submissions, and your host may be able to help for a recent window.

Where enquiries are genuinely lost, there is not much to do except improve the arrangement so it cannot recur.

And check the other routes at the same time, since a business that lost its form for four months usually has an unchecked voicemail as well.

The first-week checks that would have caught this at launch are covered in the week after it goes live.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.