
credit card deposit restaurant | restaurant deposit cost | no-show deposit friction
Why credit card deposits are costing your restaurant money
You added the deposit to stop no-shows. Fair enough. It makes sense on paper.
Here's the problem: it's working. Just not the way you think.
The deposit stops some no-shows. But before anyone no-shows, it stops people from booking in the first place. Between 20 and 30% of them, depending on the amount. They land on your reservation page, see the card field, and leave. No explanation, no cancellation β they just never finish the booking.
You never see these people. They don't show up in your no-show stats. They're invisible. And that's exactly the problem.
The maths most restaurants don't run
Let's say your restaurant gets 100 people to the booking page on a Tuesday.
With a deposit: 70 complete the booking. Maybe 3 no-show. You're left with 67 covers β plus β¬60 in penalties collected.
Without a deposit: 90 complete the booking. Maybe 12 no-show (no-show rates without deposits typically run 10-15%). You're left with 78 covers.
Same Tuesday. Eleven extra covers. At a β¬60 average ticket, that's β¬660 in additional revenue β against β¬60 in penalties you didn't collect.
The deposit didn't protect your revenue. It reduced it.
The illusion of the penalty
There's another problem. Even when a no-show happens, the penalty rarely gets charged.
Talk to any restaurant owner honestly and they'll tell you: half the time, they don't pull the trigger. The guest sends a message after the fact. There's a family emergency. They dispute it with their bank. There's a 1-star Google review waiting to happen.
So the deposit creates friction for 100% of your customers β the ones who book and show up, the loyal ones, the ones who were never going to no-show β in exchange for recovering maybe 50% of the penalty from the small percentage who don't come.
It's a bad trade.
Why the phone call works better
Before online booking existed, restaurants confirmed reservations by phone. Not to be polite. Because it worked. A guest who's spoken to someone β even briefly β feels expected. They've made a commitment that exists in their mind, not just in an app.
No-show rates for phone bookings have always been a fraction of those for online bookings. The mechanism is simple: friction creates commitment. Not financial friction β social friction. The kind that comes from saying "yes, I'll be there" to another person.
The problem was never the phone call. It was the time it took. At 30 reservations a week, calling every guest the day before is two hours of work your team doesn't have.
What the alternative looks like
Remove the deposit. Recover the 20-30% of bookings you're currently losing before they even start. Then confirm every reservation with an outbound call β automated, the day before, handled before your team walks in the door.
No-show rates drop. Volume goes up. And you've stopped penalising the 90% of guests who were always going to show up.
That's the logic behind Luigi. A voice AI that calls your guests to confirm, handles cancellations in real time, and gives you back the tables you can still fill.
No deposit required.
Luigi is a voice AI for premium restaurants. It confirms reservations by phone β automatically, the day before service β without requiring a credit card deposit. Pilots currently running in London and Paris.
INTEGRATIONS
Luigi works with your reservation system
Whether you're on OpenTable, Zenchef, SevenRooms, or another platform β Luigi connects without changing your setup.