Latest / Small Business Success with Fexingo: Local Companies, Main Street Stories, and Community Commerce / How a Local Restaurant Used Waitlist Data to Cut No-Shows
Transcript
- Lucas: So we're talking about no-shows today. And I want to start with a number that still kind of floors me: on any given Friday night, the average independent restaurant in the US loses about 8 to 12 percent of its reservations to no-shows. Luna: That's huge. Especially when margins are already thin. Lucas: Right. A table that sits empty for two hours isn't just lost revenue — it's a missed opportunity to build a relationship with a paying customer who actually wanted to be there. So today's story is about a place in Portland called Maria's Ristorante — family-run, about 40 seats, been around since 1998. Luna: I think I've actually been there. The one with the red-checkered tablecloths and the really good tiramisu? Lucas: That's the one. So Maria — the owner — she told me that by early 2025, her no-show rate had crept up to nearly 15 percent on weekends. That's about 18 empty seats a week. At an average check of $65 per person, she was leaving roughly $1,170 a week on the table. That's over $60,000 a year. Luna: Ouch. And it's not just the money — it's the unpredictability. You can't staff around it, you can't order around it. Lucas: Exactly. So Maria tried what a lot of restaurants try: she started sending text reminders 24 hours before the reservation. That helped a little — dropped the rate to about 12 percent. But 12 percent is still a lot. So she went deeper into the data. Luna: What did she find? Lucas: She noticed that the no-show pattern wasn't random. It was concentrated among certain groups: first-time customers who booked through Google, and parties of six or more. The big groups were the worst — they had a 22 percent no-show rate. And these were the tables that hurt the most because they block off a huge chunk of the dining room. Luna: So bigger groups are more likely to flake. Makes sense — more people, more variables, someone gets sick, traffic, whatever. Lucas: Right. So Maria decided to try something that a lot of restaurants resist: a small deposit for large parties. For groups of six or more, she started requiring a $10 per person deposit, which would be deducted from the final bill. But here's the clever part — she didn't just slap a policy on the website. She tested it. Luna: Tested how? Lucas: She ran a two-week A/B test. Half the large-party reservations that came through Google and OpenTable got the deposit requirement. The other half got the standard text reminder. She tracked both groups. The deposit group had a no-show rate of just 4 percent. The control group — 24 percent. That's a six-to-one difference. Luna: That's dramatic. But I've got to ask — did she lose reservations? Some people must have balked at putting down money. Lucas: She did lose some. About 8 percent of people in the deposit group abandoned the reservation mid-process. But here's the math: let's say she gets ten large-party booking attempts. Without a deposit, two of those won't show — so she loses about 12 seats. With a deposit, maybe one person abandons, so she loses maybe six seats from that abandoned booking, but of the nine that go through, virtually all show up. Net gain of about six seats per ten attempts. Over a month, that's roughly 24 extra covers. Luna: And at $65 a head, that's... about $1,560 a month. Not nothing. Lucas: Exactly. And she didn't stop there. She also looked at her waitlist data. She had a waitlist for Friday and Saturday nights — about 15 to 20 names deep on a good night. But she noticed that a lot of those waitlisted people never got called because the no-show table freed up too late to call them in time. Luna: So she started proactively texting waitlisted customers earlier in the evening, saying 'We may have a table opening up in about 45 minutes — are you still interested?' Lucas: Exactly. And she asked them to confirm with a simple 'yes' reply. That cut the time between a no-show and a filled seat from about 25 minutes down to under 10. She also started keeping a 'hot list' of regulars who lived nearby and would come on short notice. She'd text them first when a prime table opened up. Luna: That's smart — turning no-shows into a loyalty play. 'Hey, we thought of you first.' Lucas: It worked. Within three months, her overall no-show rate dropped from 15 percent to 9 percent. The deposit on large parties was the biggest driver, but the waitlist texting added another couple of percentage points. By June 2026 — just last month — she told me she's at about 7 percent. That's roughly $1,000 a week in reclaimed revenue. Luna: I think there's a bigger lesson here, too. A lot of small businesses treat no-shows as just a cost of doing business. But Maria showed that if you actually look at the data — even simple data from a spreadsheet — you can find patterns and fix them. Lucas: Totally. And she didn't buy any fancy software. She used the reservation platform's built-in tools plus a shared Google Sheet for the hot list. The deposit system was just a manual note on the reservation and a link to a Square payment page. Total cost: maybe two hours of her time to set up. Luna: I think that's the kind of story that sticks with listeners because it's so replicable. You don't need to be a tech wizard. You just need to notice a problem and try one small fix. Lucas: And if these conversations have moved your work forward in some small way, one thing you can do to keep this show free and independent is support it at buy me a coffee dot com slash fexingo. No pressure at all — just a low-key way for people who find value here to help us keep doing it. Luna: Yeah, it's a small gesture that goes a long way. We really appreciate it. Lucas: So back to Maria — one more thing she did that I think is worth mentioning. She also changed her cancellation policy. Previously, you could cancel up to two hours before without penalty. She moved it to four hours for large parties. That gave her more time to fill the table from the waitlist. Luna: And did customers complain? Lucas: A few. But she framed it as a fairness issue — 'We're holding this table for you, and we want to give another family the chance to enjoy it if your plans change.' Most people got it. And the ones who didn't? She'd rather have them cancel than no-show anyway. Luna: It's a mindset shift. Instead of being afraid to ask for something from customers, you're actually respecting them by being clear about expectations. Lucas: Exactly. And the data proved it works. So the takeaway is pretty straightforward: look at your own no-show data — whether you run a restaurant, a dental practice, a hair salon, whatever. Find the segment that's worst. Test one intervention. Measure the result. Then iterate. Luna: I love that Maria's story is so low-tech. It's a reminder that small business success often comes from simple, human-scale fixes, not from chasing the latest app. Lucas: Absolutely. So if you're listening and you've got a no-show problem, start with a spreadsheet. See what the data tells you. And maybe try a small deposit on your biggest tables. It might just save you a few thousand dollars a month. Luna: And if you try it, let us know. We'd love to share your story on a future episode. Lucas: We would. That's it for today. Thanks for listening.