Customer Story·restaurants
B2

Bistro 23

Family-owned bistro · Brooklyn, NY

We cut no-shows by 62% in the first 90 days — and recaptured roughly $4,200 in revenue we used to write off every month.

MD

Marco Delgado

Owner & Head Chef

62%

No-show rate

reduction

$4,200

Monthly recaptured revenue

avg. per month

91%

Confirmation response rate

of reservations confirmed

3 days

Setup time

full rollout

7 min readPublished February 2026Illustrative case study

The Challenge

Bistro 23 seats 48 covers on a busy Friday night. For a family-run restaurant operating on thin margins, a table of four that doesn't show up isn't just annoying — it's the difference between making payroll or not. Before DMHub, Marco and his front-of-house manager Carmen were manually calling every reservation the afternoon before service. "We were spending 90 minutes a day on confirmation calls," Marco said. "Half the time we'd leave a voicemail and never hear back."

The restaurant used a basic online reservation tool that sent an automated email confirmation at booking, but open rates were abysmal — somewhere around 22%, according to their inbox analytics. Customers who booked on a Tuesday and didn't check email again until Saturday night would see the reminder too late to cancel.

The real cost wasn't just the empty table. When a large party no-showed on a Saturday in November, Bistro 23 turned away two walk-in groups earlier in the evening, expecting the reservation to fill those seats. That single evening cost them an estimated $480 in walk-in revenue on top of the no-show itself.

The Solution

Marco connected DMHub in early March. The setup took about three days — one afternoon to wire in the WhatsApp Business API, another to import the existing reservation contacts, and a third to tune the automation sequences. The first automation was too aggressive: it sent reminders at 48 hours, 24 hours, and 3 hours before the reservation. Customers who had already confirmed were getting a third message and finding it annoying. Marco scaled back to a two-touch flow — 24 hours and 2 hours — which dropped the complaint rate to near zero.

The 24-hour reminder asks for a simple "C" to confirm or "X" to cancel. Responses arrive as WhatsApp messages and route directly into DMHub's inbox. Carmen reviews any cancellations first thing in the morning and immediately opens the slot on the reservation system for walk-ins or waitlist guests. The 2-hour reminder is a softer "We're looking forward to seeing you tonight — your table for [party size] is confirmed at [time]" message, which doubles as a light upsell mentioning the evening's specials.

For parties of six or more, DMHub triggers an additional message 72 hours out requesting a credit card to hold the reservation. This was the change Marco had resisted making for years — he worried it would feel unfriendly. In practice, the drop-off rate on large-party bookings fell from 18% to 6%, and the few parties who did no-show after leaving a card were charged a $25-per-person fee that covered Bistro 23's food cost.

Before vs. After

MetricBeforeAfterChange
No-show rate14.2%5.4%−62%
Monthly revenue lost to no-shows~$6,800~$2,600−62%
Staff time on confirmation calls90 min/day10 min/day−89%
Reservation confirmation rate51%91%+78%
Large-party drop-off rate18%6%−67%
Walk-in revenue recovered (avg)$0$4,200/monew channel

Features Used

  • WhatsApp Business API
  • Automated reservation confirmation sequences
  • Two-way messaging inbox
  • Large-party credit card hold flow
  • Specials upsell in confirmation messages
  • Webhook-based reservation import

The first week I thought it was too simple. I was waiting for the complicated part. There isn't one. It just works.

MD

Marco Delgado

Owner & Head Chef, Bistro 23

How It Rolled Out

  • Week 1

    WhatsApp Business API connected, reservation contacts imported

  • Week 2

    First automation live — 3-touch sequence (later scaled back)

  • Week 3

    Refined to 2-touch flow, credit card hold for large parties enabled

  • Month 2

    No-show rate under 7% for the first time in two years

  • Month 3

    62% no-show reduction confirmed; $4,200 monthly recapture average

  • Month 4+

    Upsell tracking added; inbox check-in routine locked at 2x/day

The Results

After 90 days, the numbers were clear enough that Marco considered the investment paid back. The no-show rate fell from 14.2% of covers to 5.4%. Monthly recaptured revenue — tables refilled after cancellations came in early enough to resell — averaged $4,200. The 90-minute daily phone call routine dropped to a 10-minute inbox review.

There were some unexpected wins too. The specials mention in the 2-hour confirmation drove a measurable uptick in pre-orders for the chef's tasting menu — customers who saw the specials message were 2.3x more likely to order a tasting menu that evening, based on Carmen's informal tracking. And the WhatsApp thread became a natural place for guests to ask last-minute questions ("Is parking easy?", "Can you accommodate a birthday cake?"), reducing the volume of calls during service by about 40%.

The integration Bistro 23 uses today: reservation data flows from their booking system via a simple webhook to DMHub, which handles all outbound sequencing. Marco's team reviews the DMHub inbox once in the morning and once around 4pm. Everything else is automated.

Guests actually text back on WhatsApp. They never replied to email. That's the whole reason this works.

CR

Carmen Reyes

Front-of-House Manager, Bistro 23

Ready to see results like Bistro 23?

Join thousands of local businesses using DMHub to grow faster with WhatsApp.

How Bistro 23 Used DMHub | Case Study