The inquiry nobody answered was nobody's fault, and that is the problem
An event inquiry lands in a shared inbox on a Friday night. By Monday it is under forty other emails, and the coordinator who would have answered it was on the floor. Nobody owned it, so nobody was late with it — and that is a design problem, not a training one.
· 6 min
There is a well-worn sales statistic about responding to leads within five minutes. We do not quote it, because it is usually cited without a source and a number you cannot check is decoration.
What is worth examining is the mechanism underneath it — why inquiries go unanswered in a business whose entire product is answering people.
How an inquiry dies
Nobody decides to ignore a booking request. The failure is duller than that.
An inquiry lands in a shared inbox at 7pm on a Friday, which is the single worst moment in a restaurant’s week to receive anything requiring a considered reply. By Monday it is under forty other emails. The coordinator who would have answered it was on the floor all weekend.
An inquiry with no assignee has nobody to be late.
An inbox has no state — only read and unread.
"I'll do it tomorrow" is invisible to everyone but the person thinking it.
Being late requires somebody to have been responsible. A shared inbox is, structurally, an arrangement in which nobody is.
The three things that change it
None of them are glamorous, and all three have to be present.
An automatic acknowledgement, sent in seconds, telling the guest a human exists and when a real reply is coming. This is the one that buys back the afternoon — a guest who has heard something is not, at hour three, filling in the form at the restaurant down the road.
An owner on every inquiry from the moment it arrives. Not a queue somebody is notionally watching. A name. Lateness needs somewhere to attach.
An escalation when nothing happens. This is the one most systems skip, and it is the load-bearing one, because the entire failure mode is that nothing happening produces no signal. A ladder — the coordinator, then the manager, then the GM and the owner together — turns silence into an event.
:::key The one that is easiest to get wrong An escalation that is configured but has nobody to notify is worse than none at all. It runs, it succeeds, it reports nothing wrong, and it delivers to no one. When you set this up, the test is not “did it save” — it is “did somebody get an email”. :::
What to measure on your own inbox
You do not need software to find out whether you have this problem. Open your inquiry email, take the last fifty, and for each one write down the date it arrived and the date you first replied.
It takes about twenty minutes, and it is the most uncomfortable twenty minutes available to a venue this month.
Two numbers come out of it:
- The share you never answered at all. This is the one to fix first, and it is worth more than any improvement to the ones you did answer
- Your median hours to first reply, on the ones you answered
If the first number is above zero, you have found free money. An unanswered inquiry is the only kind of lost business that costs nothing to prevent — no discount, no comp, no marketing spend. Somebody just has to reply.
A caution about the causation
It is tempting to conclude that answering faster wins more events, and to treat response time as a lever. It might be. But a fast reply and a won event share a common cause worth naming: a good inquiry — right date, right party size, a room that is obviously free — is both easy to answer in ten minutes and easy to win. A vague one for a date nine months out with no headcount is slower to answer and less likely to become anything.
So treat response time as a discipline rather than a growth hack. The part that needs no causal argument at all is the unanswered pile: you cannot win an event you never replied to, and that is arithmetic rather than correlation.
heard, captain.