The Booking Nobody Confirmed
A booking taken is not a booking held. Where confirmations fail, why reconfirming large parties changes the no-show rate more than any policy, and the wording that gets a real answer.
The booking was taken on Tuesday. Nobody has spoken to them since. On Saturday, they do not arrive.
Between Tuesday and Saturday, nothing happened that would have told you.
Where confirmation fails
It was never sent. Taken verbally, written in the book, and that was the entire process.
It was sent and not read. An automated message into an inbox nobody opens. ⚠️ Sent is not received, and a confirmation nobody read is doing none of the work you think it is.
It confirmed the wrong thing. It confirmed that you have a booking. It did not confirm that they still intend to come, which is the thing you actually need to know.
Nobody reconfirmed close to the date. ⚠️ The single largest gap. A booking made three weeks out and never touched again is substantially less reliable than one made two days out, and nothing in the process accounts for that.
The two different messages
They do different jobs and most venues send only the first.
The confirmation, at the time of booking. Records the details, gives them something to check. Its job is accuracy, not commitment.
The reconfirmation, shortly before. ⚠️ Its job is to get an answer. It should ask something, not merely inform — and it should be easy to answer either way, including with a cancellation.
Making cancellation easy
Counterintuitive, and it is the thing that works.
A guest who cannot come will simply not appear if cancelling is awkward. ⚠️ Give them a frictionless way to cancel and a share of your no-shows convert into cancellations — which are a completely different thing, because you can resell the table.
Do not make them explain. The explanation is the friction.
Thank them for cancelling. It sounds odd and it is correct — you want this behaviour repeated.
The wording
The reconfirmation has to invite a real answer.
Ask, do not announce. "Still good for Saturday?" gets a reply. "Your booking is confirmed for Saturday" does not.
Include the specifics. Time, size, anything requested. ⚠️ Errors surface at this moment or at the table, and the table is much more expensive.
Give the deadline plainly. When you need to know by, and what happens after — without a threat, which converts a cancellation into a silent no-show.
Which bookings deserve the effort
Not all of them, or the process will not survive.
Large parties. Where the loss is proportional to size. Peak slots. Where the table could have been resold. Long lead times. ⚠️ A booking made a month ago is the highest-risk category there is and rarely treated differently. First-time bookers. No history, no relationship.
Not: regulars booking two days out. The friction costs more than the risk.
What to do with an unanswered reconfirmation
Decide in advance, or it gets decided at 19:00 by whoever is nearest.
Silence is not a cancellation — but it is information, and a second attempt on a large party at a peak slot is warranted.
⚠️ Releasing a table on silence alone will eventually release a real booking, and that is a much worse outcome than an empty table. Two attempts, then a decision by a named person.
Three places confirmation fails
Sent to the wrong place
Sent and not seen
Seen, and it is unclear whether a reply is required
⚠️ The third is the most common, and it is fixed by one sentence: "if this is still right, no reply is needed."
Do not confirm everything
Confirming every booking the messages stop being read
Confirming what cannot be refilled they keep working
⚠️ Large parties, peak slots, exclusive use. ⇒ Volume is what destroys a confirmation system, not wording.
The two messages do different jobs
The first reminds them
The second makes cancelling easy
⚠️ Almost nobody sends the second, because it feels like inviting a cancellation. ⇒ But someone who is not coming is not coming either way. Told early, the table sells. Told late, it stands empty.
The wording that gets answered
"To cancel, click here" reads as a door out
"If your plans change, let us know — we are holding the table" reads as being looked after
⇒ ⚠️ The second gets more replies, including the cancellations you wanted to know about.
Count the right thing
No-shows will not fall much
Advance notice will rise
⚠️ The number to watch is the share who told you beforehand. ⇒ You cannot make people come. You can make them tell you, and every percentage point of that is a table you can sell again.
Three to hold
No-shows as a share of bookings, split by whether they were reconfirmed. ⚠️ The number that settles whether reconfirmation is worth the effort — and it usually settles it decisively.
Cancellations received after a reconfirmation. Rising is good. These are no-shows that became recoverable tables.
Reconfirmations unanswered. If most go unanswered, the wording is announcing rather than asking.
Where the record has to sit
Reconfirmation only happens if somebody can see which bookings are due and which have been answered. If that lives in a book and a separate message thread, it happens on quiet days and stops on busy ones — which are exactly the days it matters.
tasteck keeps booking status and guest contact on the same record, so which bookings still need an answer is visible rather than remembered.
They did not decide not to come on Saturday. They decided somewhere in the four days nobody spoke to them.
Read next
Related articles
Who Types The Request In
A guest asks for somebody by name. Between that sentence and the figure on your monthly sheet, three or four people handle it. Every one of them is a place where it can quietly vanish.
What One More Regular Is Worth
Venues in this trade know what a quiet Tuesday costs them. Far fewer can say what one additional regular is worth over a year — which is the only number that tells you what you can sensibly pay to find one.
What a Listing Is Worth To One Room
A single-room salon and a twelve-room clinic get the same price from the same portal. Only one of them can work out whether that price is defensible, and it is the small one — because the arithmetic is smaller.
Map out your operations in 5 minutes
Eight questions cover reservations, customer management, shifts, and settlement. Results shown instantly with industry benchmark. Sales emails only if you request them.
Your answers are not stored. The assessment runs entirely in your browser.
Try tasteck free for 30 days
No credit card required. Full access to reservations, cast shifts, dispatch, and analytics.
- No card required
- Free data migration support
- All features unlocked for 30 days