Taking a table without losing the cover, the deposit or the guest. The TableSpark restaurant booking system →
Two parties both insist they were next, the paper sheet is already in the bin, and the dispute gets decided on whichever memory sounds most confident.
Forty places are sold, one guest changes their mind, and the no-refunds line at checkout may not bind. The exposure is the term itself, and the price shown before it.
Bookings agreed in message threads can bind the restaurant, yet the only copy of what was promised walks out with the phone long before any dispute arrives.
Ring at 19:15 and the cancellation lands on a docket. The four-top is released at cash-up, long after the cover was lost, and nothing in the building counts it.
Most restaurants have one or two tables a wheelchair user can actually be seated at, and only the longest-serving member of staff knows which. Nothing records it, so the wrong table gets given away.
A regular tries to book and the form says nothing is available. Nothing was wrong with the night: a no-show flag from last winter refused her, with no human involved.
On a Friday the line goes quiet, and the card terminal sharing the socket goes with it. BT retires the analogue network by January 2027, and attached equipment may fail.
A table is held all evening for a guest who simply forgot the time they agreed, the confirmation never reached their calendar, and the cover is lost.
An unprotected booking form fills the inbox with automated submissions, and the cost is not the noise. It is the real table request nobody saw in time.
A booking form can look complete on desktop yet hide labels, trigger the wrong phone keyboard or lose a guest’s correction before submission.
A guest can choose one branch and receive confirmation for another, leaving both venues with an avoidable service dispute.
A booking reminder can be enabled yet fail before reaching the guest, leaving staff without dependable delivery evidence.
