Website Enquiries Not Coming Through? The Lead Leak Audit for Singapore SMEs

If your website enquiries have gone quiet, the form on the page is almost certainly still working. What fails, nine times out of ten, is the hand-off between the form and a human. The notification email gets filtered or rejected before anyone reads it, it goes to an address belonging to someone who has left, or it lands in a shared inbox where everybody assumes somebody else has replied. You can prove which one it is in about twenty minutes: submit a test enquiry from outside your office, using a personal email address, then follow it by hand through every step until it reaches the person who is supposed to quote it. If it stops somewhere, that is your leak.

Why do website enquiries stop arriving without anyone noticing?

Because nothing announces the failure. A broken enquiry path produces silence, and silence looks exactly like a quiet month. There is no error message, no bounce, no alert. The owner concludes the market is slow, the marketing spend is not working, or the competitor has got cheaper.

The usual trigger is a change nobody connected to the website. A new mail provider. A security tightening at that provider. A plugin update. A staff departure. A phone number ported to a new plan. Each of these is routine on its own, and each can quietly cut the wire between a customer who wanted to buy and the person who could have sold to them.

The cost is not theoretical. If your average job is worth a few thousand dollars and three enquiries a month go missing, a quiet quarter is a five-figure hole that never appears in any report, because a lost enquiry leaves no record anywhere.

How do you test the paths a customer actually uses?

Test as a stranger, not as the owner. Five steps, done in order, on a phone:

1. Switch off office wifi and use mobile data. Your office network is often treated as trusted by your own systems, which hides the exact filtering a real customer triggers.
2. Submit every form, not just the contact page. Quote requests, product enquiries, careers, newsletter sign-up. They are frequently configured by different people in different years and fail independently.
3. Use two outside email addresses from different providers. One will sometimes get through where the other does not, and that difference tells you it is a filtering problem rather than a sending problem.
4. Tap the WhatsApp button and the phone number on the site. Confirm the message lands on a business line somebody is actually watching, and that the call connects to a person.
5. Write down the clock time of each submission and the clock time of the first human reply. Not the automated acknowledgement. The first reply from a person.

Then check the places a message hides: the junk folder of the receiving mailbox, and the quarantine inside your mail provider's admin console. Most owners have never opened the second one. It is common to find months of real enquiries sitting there.

What breaks most often on a Singapore SME website?

Seven failures account for nearly all of it:

1. The form sends mail through the web host instead of your mail provider. Your domain never authorised that host to send on its behalf, so your own mail system quarantines or rejects it. This is the single most common cause, and it usually starts the week the company moves to a business email service.
2. The notification goes to a departed staff member. The mailbox is closed, the address still sits in the form settings, and the mail vanishes.
3. An update broke the spam check. After a plugin or theme update the form can classify every submission as spam and discard it without telling the visitor. The page still shows a thank-you message.
4. Submissions exist only as email. If the form does not also save each enquiry into the website's own database, you have no record, no evidence, and nothing to recover when email fails.
5. Replies go to the wrong address. The form sets the sender as your own company address, so hitting reply writes back to yourself. Staff notice once, then stop trusting the inbox.
6. WhatsApp sits on one person's personal phone. When that person is on leave, in a meeting, or gone, the line is dead and the history leaves with them.
7. Nobody owns the shared inbox. The enquiry arrives correctly and is read by three people, each assuming one of the others has answered. In our experience this is the costliest failure of the seven, because the technology is working perfectly.

Who should own the enquiry inbox?

One named person, with a named backup, and a reply deadline in writing. Not a department, not a group alias, not whoever sees it first. Shared responsibility for a shared inbox reliably produces no responsibility at all.

Give that person three habits. Open the mail provider's quarantine once a week. Submit one test enquiry on the first of every month, through mobile data, and confirm it arrives. Keep the enquiry register, so the monthly count is visible and a drop is a question somebody asks rather than a mood somebody feels.

Why fix this in October rather than January?

Because the enquiries that pay for the first quarter of 2027 arrive now. Chinese New Year falls on 6 February 2027, and production, stock and staffing decisions for it are being quoted from October onwards. December brings customer shutdowns and staff leave. A leak you find in January has already cost you the season.

There is a second reason. Enquiry paths are cheap to fix when nothing else is on fire. In the middle of a rush, nobody will authorise a day of attention to a form that looks like it works.

What does the fix cost?

Most of it is configuration, not development. Pointing forms at an authenticated sending service, correcting the sender and reply-to settings, adding database logging of every submission, and moving WhatsApp onto a proper business account with multi-device access is typically half a day to a day of work for a small site.

The only recurring cost is usually the sending service, which is free at the volumes most SMEs produce and in the region of twenty to forty dollars a month above that. Set against one recovered job a quarter, the arithmetic is not close.

The outcome to aim for is simple to state: every enquiry is recorded in two places independent of email, one named person is accountable for the reply, and a test submission proves the whole path works on the first of every month.

Frequently asked questions

How do I tell whether enquiry emails are being filtered or were never sent at all?

Check whether the website itself holds a record of the submission. If the enquiry appears in the form's own stored entries but no email arrived, you have a delivery or filtering problem at the mail provider. If there is no stored entry either, the form never processed the submission, which points to a broken spam check or a script error on the page.

Should website forms send email from my own company domain?

Yes, but only through a properly authorised route. Sending as your own domain from a server your domain has not authorised is precisely what gets the message quarantined. Use an authenticated sending service, and set the customer's address as the reply-to so staff can answer with one tap.

Is WhatsApp a safer channel for enquiries than a web form?

It is more reliable at delivery and far weaker at record keeping. On a personal phone it creates a single point of failure and takes the conversation history with the staff member when they leave. Treat it as a second channel on a business account with multiple device access, not as a replacement for a form that logs every enquiry.

Digital Perpetual runs enquiry path audits for Singapore SMEs, usually inside a single working day, and reports exactly where leads are being lost before quoting season starts.