How a family-run restaurant cut no-shows to a reasonable number
Casa Marcelo migrated from Excel and TheFork to their own system in two months. Result: more direct bookings, less phone time, and an own customer base for campaigns.
- Weekend dinner no-show rate
- 5%
- before: 22%
- Direct vs platform bookings
- 85% / 15%
- before: 65% / 35%
- Daily phone time
- ~20 min
- before: ~75 min
- Yearly platform cost
- ~€1,100
- before: ~€3,000
Starting point
Casa Marcelo is a 35-seat family restaurant in the old town of Santiago. Five employees, three main weekly services (Thursday, Friday, Saturday dinner), and a clientele split between neighbourhood regulars and occasional tourists — with strong weekend concentration.
Reservation management had grown organically without changing tools: a shared spreadsheet between the maître d’ and two operators. When someone came in to dine, one of the three picked up the phone or checked the door camera; when someone cancelled, it got crossed out with a pen.
The obvious operational problem was the phone: it rang at 12:30 while setting up lunch service, at 5:30 pm while cashing up, and at 10:30 pm mid-dinner. The second operator had to stop to pick up, often with two bookings queued.
The invisible problem was no-shows: on weekend dinners it ran at 20-22%, but nobody had measured it precisely. The perception was “a fair number of people stand us up”, and the default response was to “overbook a bit”.
Why they changed
The trigger wasn’t economic. It was that on an October Saturday, with the terrace full and 8 people standing at the door, they discovered that a booking marked for 4 had no table assigned because someone wrote “table 7” instead of “table 2” in the sheet. Two bookings overlapped. The waiting group left for the competition.
Marcelo roughly calculated the three categories of real cost:
- TheFork and Tripadvisor Reservations: ~€3,000/year in commissions.
- Staff phone time: ~75 minutes/day × 3 strong days × 52 weeks = 200 h/year.
- Empty tables from no-shows: ~18 tables/year at ~€50 ticket = €900.
Estimated total: ~€5,200/year in partially or fully avoidable costs.
Implementation
They migrated in a slow January week, when volume was down. Plan:
- Week 1: Signed up for Reserver Pro, configured a single zone (35 seats), one dinner service (20:00-23:00, Thu-Sat), minimum 3 h policy. Widget installed on site. Reserve with Google requested.
- Week 2: Team training (45 minutes, mostly for the maître d’). First bookings taken in Reserver, with Excel running in parallel as a fallback. Guest records created on the fly whenever a regular showed up.
- Week 3: Excel switched off. Everything operating only in Reserver.
They didn’t activate pre-authorization in the first month. They wanted clean baseline data on their actual no-show rate first.
What they found by measuring
The real no-show rate, with clean first-month data, was 22% on weekends, 8% midweek. With automatic reminders (email 24 h + SMS 2 h) active from day one, it dropped to 14% weekends / 5% midweek by week 6.
Phase two was activating pre-authorization: €10 per person, only on Friday/Saturday dinners, only for parties of 4+. Four months later, no-show in that segment was at 5%.
What didn’t work at first
Not everything was clean. Two initial mistakes they corrected:
Default duration too short
They set 75 minutes for dinner. Too tight; several bookings overlapped on the same table with guests who hadn’t finished. They bumped to 105 minutes and the problem disappeared.
Duplicate records in the first weeks
Because the team created records on the fly whenever a regular showed up, duplicates appeared (some as “Juan Pérez”, some as “Juan P.”). Reserver’s duplicate detector flagged them automatically when a new record was created; even so, once a month they spent an afternoon reviewing and merging by hand. Retrospective recommendation: agree from day one how to type names and phone numbers.
Results at 6 months
- Weekend dinner no-show: 22% → 5%.
- Direct vs platform bookings: 65/35 → 85/15.
- Phone time: 75 min/day → 20 min/day.
- Platform cost: €3,000/year → €1,100/year (they keep a reduced TheFork presence for tourist acquisition).
- Own guest base: from 0 active emails to ~1,100, with a quarterly dormant win-back campaign recovering 8-12% of sleepers.
What Marcelo would recommend
In his words during a recent conversation:
- “Don’t wait for the perfect moment.” January was easier, but any reasonable month works. The only critical thing is not the strongest month of the year.
- “Activate pre-auth by segment, not everyone.” Applying it only on weekends kept weekday regulars happy.
- “Spend an hour cleaning the CSV.” Saves days of work afterwards.
Note: This case study is illustrative. The numbers are representative of patterns we see with restaurants of similar profile, but “Casa Marcelo” is not a specific customer. When we have permission from real customers to publish their cases, we’ll add them.
If your restaurant matches this profile — independent, 30-50 seats, mixed clientele — request a demo and we’ll show you the configurator with data similar to yours.
“What you feel most isn’t the savings — it’s that we no longer argue with the maître d’ about whether table 5 was booked at 9 pm or 9:30. It’s all on screen.”