Scenario: fewer no-shows with confirmations, reminders and deposits

Typical problems

• Bookings arrive by phone, Instagram DM and LINE — nobody confirms them, and half of the "reserved" tables stay empty.
• The same guests fail to show up again and again, but the team has no history to see it.
• For large groups and holiday nights a no-show means real lost revenue, yet asking for a prepayment feels awkward.

How it can be implemented in ResoGuest

1. One booking channel. Connect the booking widget to your website, Google profile and social bios, and add a QR code at the entrance. All bookings land in one list with statuses: pending, confirmed, seated, cancelled, no-show.
2. Automatic confirmation. Right after booking the guest receives a confirmation in their messenger (LINE, WhatsApp, Telegram) or by e-mail — in their own language.
3. Reminder before the visit. Set a reminder a few hours before the booking with a one-tap "cancel" option: a cancelled table goes back on sale instead of standing empty.
4. Deposits for peak slots. For groups, set menus and holiday nights, turn on a deposit for the booking — the guest pays online when booking.
5. No-show history. The host marks "did not arrive"; the mark is saved in the guest profile, so the next booking from this guest is visible as risky.
6. Waitlist. With the Waitlist & Walk-in module, freed tables are offered to walk-in guests and those waiting in line.

What the client gets

• Every booking is confirmed and reminded automatically — the host no longer calls guests one by one.
• Tables cancelled in advance return to sale, and peak nights are protected by deposits.
• A no-show history per guest instead of guesswork.
• One tablet at the host stand is enough; mobile devices for waiters are optional.

Who it fits

Restaurants with busy weekends, rooftop and beach venues, places with set menus and group bookings. Bookings, reminders and deposits are in the core plan; the waitlist is in Growth and above. Contact us: [email protected]