Why it works is psychological before it's technical. Calling to cancel is awkward: the phone call is a confrontation, you risk the “but we were expecting you”, and many customers put it off until they never make it — the no-show. A personal link removes the confrontation: nobody answers, nobody judges, you confirm and it's done. The code also ties the cancellation to one precise booking: no “hello, I'm cancelling a table” to untangle, with date, time and name already set. The customer who cancels in two taps at 5 pm is a customer who wouldn't have shown up at 8 pm: same absence, opposite outcome for the dining room.
For the code to work it must be where the customer will find it: in the confirmation message, not in a lost email. A serious cancellation takes one step and gives a clear receipt — “booking cancelled, the table is free” — so the customer knows it's really closed. On the business side, every code cancellation updates the diary on its own and can trigger the waiting list automatically: the seat freed at 5:30 pm is offered to the first in line before 6 pm. Write down until when the cancellation carries no penalty: a code that works at any hour turns a last-minute cancellation into a right, not a favour.
Frequently asked questions
- How long should the cancellation link stay active?
- Write it at confirmation: many set the limit 3-6 hours before the service, so a seat freed late becomes a legitimate penalty and one freed early stays refillable. A code that always works is fine only if you have a very active waiting list.
- Does link cancellation replace the restaurant's phone number?
- No, it sits alongside it: there's always a number or a chat for the real cases — time changes, allergies, group cancellations. The link removes ninety per cent of the one-minute administrative calls that interrupt the service.