The difficulty with deposits is almost never the money. It is the timing. Asked at the moment of booking, alongside the price and the section, a deposit is simply part of what the table costs. Asked two days later, in a direct message, it reads as suspicion.
Ask at the point of booking
If the deposit is part of the checkout, nobody has to chase it, and nobody has to decide whether this particular guest should be asked. The rule is the same for everyone, which is what makes it feel fair rather than personal.
Say what it does
A deposit either comes off the bill or it does not. Either is defensible. What is not defensible is leaving it unsaid until the end of the night. Put it in the same sentence as the price: what is taken now, what it goes toward, and what happens if the booking does not arrive.
- Set the amount per section rather than per guest, so bigger tables carry more of the risk
- Use a minimum spend where the table is the product and the deposit is only the hold
- Keep the wording on the booking page the same as the wording your team uses on the phone
Make the exception deliberate
There will be regulars you would never ask, and nights where a full room matters more than a held one. Those are good decisions. They are only bad when they are the default, made table by table, by whoever happens to pick up.
VenueStack collects deposits through the calendar, the booking widget, or an internal reservation your team creates, and keeps the deposit attached to the reservation so the floor can see what has been paid.
