The most expensive leak is the invisible one
A lost sale you can see is annoying. You know the price was wrong, or the date did not work, and you can do something about it next time.
This one never appears. The request arrived at 9 PM, sat in an unread chat, and by the time you opened your phone the next morning that person had already booked somewhere else. It never entered your calendar, your notes or your figures. You cannot miss what you never saw.
Nobody stole that booking. It expired.
260
missed bookings a year, at just one a day. Nobody ever writes that number down.
Before you blame the price
Most owners assume they lost on price, because price is the only thing they can see. Run the audit on the next page first. Price is rarely what shows up.
Step 1 — Find your three leaks
Take the last thirty enquiries. Not your impression of them — the actual messages. Sort each one into a column:
| Where it died | What it looks like in the chat |
|---|---|
| After closing time | Message timestamped outside your hours, first reply the next morning |
| Needed an answer, not a date | They asked a question; you offered a slot |
| Replied, but late | Your answer is more than four hours after theirs |
| Genuinely lost on price | They saw the number and said no |
Count each column. In almost every business we have looked at, the fourth column is the smallest one — and it is the only one most owners were worrying about.
Thirty messages, twenty minutes. This is the whole diagnosis.
Step 2 — The five-message script
The aim is not to sell in the chat. It is to keep the conversation warm until a human can take it, and to collect what you always end up asking anyway.
Instant receipt
«Got it — I have your message. Two quick things so I can check availability properly.»
The two questions
Ask only the two you ask every single time. Usually the date and the size or type of job.
Offer before it cools
Two concrete slots, not «when suits you?». An open question restarts the wait.
Hold it out loud
«I am holding Thursday 10am for you until tomorrow noon.» A deadline they did not have to invent.
One nudge, then stop
A single reminder before the hold expires. One. More than one reads as desperate.
Step 4 is the one that changes the numbers. Until a slot is held, there is nothing to lose by waiting — so they wait, and then they book with whoever answered first.
Step 3 — What to say when you do not know yet
The usual objection to answering at night is: I cannot confirm anything at 9 PM, so what is the point?
The point is that the customer is not asking for a confirmation. They are asking whether they are in the right place. Those are different questions, and only the second one needs answering immediately.
- «Yes, that is exactly what we do» — answers the real question
- «I will confirm the slot first thing tomorrow» — sets the expectation
- «Meanwhile, here is what it usually costs for a job like this» — removes the reason to shop around tonight
- «Anything else you want me to check before I call?» — keeps the thread open
An answer that says «not yet» still beats silence by a mile.
Step 4 — Decide what a machine handles
Once the script exists on paper, automating it is a small job. And the boundary matters more than the tool:
| Let it run on its own | Keep it human |
|---|---|
| The instant receipt | Anything about a complaint |
| The two standard questions | A price outside your normal range |
| Offering slots you have marked free | A customer who sounds unhappy |
| The single reminder | Anything the script did not anticipate |
The handover has to be obvious
The customer should never be surprised to find a person. «I am checking with the team, someone will confirm this morning» does that job in one line.
5 msgs
is the whole system. If your script needs fifteen, it is trying to sell instead of hold.
Start with the thirty
Do not buy anything yet. Open the last thirty enquiries and sort them into the four columns. The size of the first three columns is your answer — and it usually surprises people who were sure it was the price.