Before you buy more enquiries, measure how long the last twenty waited

The conversation almost always starts with the website. Enquiries come in, nothing much comes of them, and the conclusion is that the site is not working hard enough. Could we look at the copy, the forms, the ad budget.

Sometimes it is the site. More often the enquiries were fine and the business took two days to answer them.

That is an uncomfortable thing to be told, so it is worth saying at the outset that this is not a diagnosis anyone should accept on my word. It is measurable, you already hold the data, and it takes about an hour.

The measurement nobody runs

Open the mailbox where your form notifications land and take the last twenty. For each one, find your first real reply in the sent folder and write down both timestamps. A real reply means a person addressing what they asked. The automatic acknowledgement does not count, and neither does an internal forward.

01Take the last twenty form notifications
02Find your first human reply to each
03Write the two timestamps side by side
04Sort by the gap, worst first

Then resist the urge to average them.

The average is the number that hides the problem

Say eighteen of the twenty were answered inside half an hour and two took three days. The average comes out somewhere around seven hours, which reads as "we are a bit slow" and suggests a general tightening up.

That is the wrong conclusion twice over. You are not a bit slow, you are fast almost always and absent occasionally, and the two that went missing are worth more than the eighteen because nobody else had to compete for them. Sort by the gap instead and look at the worst three. You will usually find they have something in common.

In my experience that something is the clock. The enquiries that rot are the ones that arrive after about five, on a Friday, or during the week somebody is away. Nothing is wrong with the process during office hours. There simply is no process outside them, and an enquiry sent at nine on a Tuesday evening sits until somebody opens a laptop.

What an automatic reply can honestly do

It cannot answer the question. Anyone who has had a reply that gestured at their enquiry without reading it knows the difference inside a sentence, and that is a worse first impression than silence.

What it can do is end the silence truthfully. Say that the message arrived, say when a person will reply, and name the person. "Andy will come back to you tomorrow morning" is a promise with somebody's name on it. "One of our team will be in touch shortly" is a clock with nothing behind it.

An acknowledgement that sets a clock and tells the reader nothing is worse than no acknowledgement at all.

Then make the wait useful. Whatever you would normally send in the first exchange can go out immediately: the brochure, the range a job of that type usually falls into, the two questions you always have to ask before you can say anything sensible. Half the back-and-forth of a first conversation is predictable, and sending it up front means the reply you write on Wednesday is the second step rather than the first.

There is a line it should not cross. Once an automatic message starts answering on your behalf, it is a reply, and readers judge it as one. Keep it short, keep it obviously automatic, and let it do one job.

I would also say plainly that plenty of firms do not need one. If your worst gap in twenty enquiries is forty minutes, an acknowledgement adds a message to somebody's inbox and nothing else. Measure first.

What we built, and which half of it mattered

The lead capture in Opus Resource Planner exists for this problem. It is our own software, used daily by a renovation firm, and the relevant part of it is small: when an enquiry arrives it sends the brochure and a templated response immediately, records the enquiry as a lead, and carries it through the CRM to whatever it becomes.

The useful thing we learned building it is that the sending was the easy half. Consumer enquiries to a trade business do not keep office hours, so the acknowledgement closes a gap that would otherwise last until somebody opens a laptop. But the enquiry still has to end up on a list that a named person works through, and no amount of automation decides whose list it is. That part is a conversation, not a feature.

The ownership problem underneath

Speed is the symptom. The cause, nearly always, is that nobody is responsible for the first reply on any given day.

Enquiries land in an address two or three people can see, which feels like redundancy and behaves like the opposite: each person assumes one of the others has it, and the ones that fall through are invisible because no individual ever had them. The fix is dull and it works. One name per day, written down, including Saturdays if you accept enquiries on Saturdays. The software can route, remind and escalate, but it cannot decide whose job it is.

So the useful thing to do this week is the twenty-enquiry measurement, and then one of two things. If the worst gaps cluster in the evenings and at weekends, you want an acknowledgement that buys you until morning. If they are spread evenly through the working week, no amount of software will help, because what you have is a rota problem wearing a technology costume.

Either way, it is a cheaper place to start than the ad budget. If you want a second pair of eyes on what the twenty tell you, get in touch.