The enquiry nobody answered

A contact form is a promise. Fill this in and a person will read it. Businesses break that promise constantly, and almost none of them know they are doing it, because the breakage is silent by design.

The enquiry gets submitted. The form hands it to a plugin, the plugin hands it to an email server, and the email lands in an inbox nobody checks, or a spam folder, or nowhere at all because a setting changed eight months ago. The customer waits a day, feels ignored, and calls a competitor. The business sees nothing. There is no error, no alarm, no gap in any report. Just a quiet absence of work.

The research here is old and it has never been contradicted. A study published in Harvard Business Review timed how firms responded to web leads: the ones that responded within an hour were nearly seven times more likely to qualify the lead than those that waited even an hour longer, and the average firm took far longer than that. Speed of reply is not politeness. It is the deciding variable.

So I treat an enquiry as a piece of infrastructure with three requirements. It must arrive by more than one route, so a single broken link cannot lose it. My own forms send an email, push a notification to a phone, and write the enquiry into storage that no inbox can eat. It must acknowledge the sender immediately, in plain language a person would actually write. And it must be tested from the outside, on a schedule, because the only honest test of a contact form is submitting one.

Count your enquiries from last month. If the number is lower than your foot traffic suggests it should be, the form may not be unpopular. It may be broken. This is the kind of thing I fix.