Why website enquiries get missed — and how to fix the handover

An enquiry that never gets answered is the most expensive kind of lost work. You paid to get that person to your website. They raised their hand. And then nothing happened.

Almost none of this is caused by the form itself. It's caused by what happens in the ninety seconds after it's submitted.

Where enquiries actually get lost

Follow the path a typical enquiry takes:

1. Someone fills in the form.
2. It sends an email to a shared inbox — info@, sales@, enquiries@.
3. Somebody has to notice it.
4. Somebody has to decide whose it is.
5. Somebody has to tell that person.
6. That person has to remember to reply.

Six steps, five of them manual, and every one is a place the enquiry can stop. The most common failure is step three colliding with step four: everyone can see it, so everyone assumes it's being handled.

The other classic: it arrives at 4:55pm on a Friday, gets read, gets mentally filed as "Monday", and Monday brings its own work.

Why speed matters more than you'd think

Enquiry follow-up is unusually time-sensitive. Someone filling in a form is usually filling in several — yours and two competitors'. In that situation the first credible reply has an enormous advantage, and it decays fast. A reply the same hour lands very differently from one two days later, even if the second is better written.

Which means the goal isn't just "don't lose enquiries." It's "get them to the right person while the person still cares."

The fix, in four parts

1. A shared inbox is not an owner

This is the root cause. info@ belongs to everybody, which means it belongs to nobody.

Either name one person responsible for triaging it every day — a real name, not a rota nobody remembers — or get enquiries out of the shared inbox and onto individuals' lists. The first is a patch; the second is the actual fix.

2. Every enquiry becomes a job with a name on it

The moment an enquiry arrives, it should exist as a task, owned by one person, with a date. Not as an email that someone might convert into action.

That single change closes most of the gap, because a task with an owner shows up as overdue when it isn't handled. An unread email in a shared inbox never becomes overdue. It just gets older.

3. Decide the routing rule in advance

Don't decide who takes each enquiry when it arrives — decide the rule now, in a quiet moment.

It can be simple: by area, by service type, round-robin, or "everything to Sam unless it mentions installations." Whatever fits. The point is that routing shouldn't require a judgement call at the moment of arrival, because that's what creates the pause where things get dropped.

Have a fallback: if nobody matches the rule, it goes to a named person by default. Never to a group.

4. Set a promise, and make it visible

Pick a response standard you can actually hit — same working day, or within four working hours. Write it down. Then make it measurable: if enquiries are tasks with dates, you can see when you missed it, which is the only way you'll ever improve it.

If you're not tracking it, your response time is whatever you assume it is, which is usually optimistic.

The weekly check worth doing

Once a week, look at the enquiries from the past seven days and ask:

• Did every one get a reply?
• How long did each take?
• Did any sit in the shared inbox before someone picked them up?

That last question finds the leak. Most businesses that run this exercise are surprised — not by the enquiries they lost, but by how many took two days to reach the person who was always going to handle them.