Front-Door Queue Management: Mobile Wait List for Walking-In Guests

A popular brunch spot in Galata, Istanbul, used to have 18 people clustered on the sidewalk every Saturday at 11:30. Now the host sends an SMS: "You're on the list, ETA 28 min, we'll text when ready." Guests grab coffee at the cafe next door and walk back when pinged. The sidewalk is clear, no-shows dropped, and revenue per turned table climbed.

Why SMS-Based Waitlists Work

The host enters the guest's phone, party size, and notes (high chair, terrace preferred) into an iPad. The system auto-sends an SMS with 28-minute estimate, queue position, and a confirmation prompt when the table is ready. If the guest doesn't reply "Coming" within 5 minutes, the next party is bumped up.

The ETA algorithm looks at the last 14 days of table-turn averages, current open tables, and party-size distribution in the queue. Galata's pilot ran 22 min for 2-tops, 38 min for 4+ — deviation under 10% from actual.

OpenTable, Yelp Waitlist, and thMenu API Options

Two big external players: OpenTable Waitlist (shares POS hooks with their reservation product) and Yelp Waitlist (a "Join the line" button on the Yelp profile). thMenu's Platinum tier bundles waitlist with table sessions — once a guest is seated, the same session token carries into the ordering flow without a re-scan.

Key contract points: webhook for "party seated," 15-min no-response cutoff, party-size override, VIP flag, allergy note. SMS cost is roughly $0.05 per guest — under $30/month for a 200-cover restaurant.

Wins, Pitfalls, and Host Training

The Galata pilot, 6 weeks in: walk-away rate dropped from 34% to 11%, perceived wait fell from 30 min to 18 min (actual wait unchanged — pure expectation management), and Google rating rose from 4.2 to 4.5. Bonus: guests post Instagram stories from the wait-cafe, generating organic reach.

• WhatsApp Business API instead of SMS cuts cost but reduces response rate by 12% (especially tourists).
• Always pad ETAs by 10%: promise 28, seat at 22. Never the reverse.
• Host training is critical — wrong phone number = lost guest. Use input masks and read-back.

FAQ

What if the guest can't receive SMS? The host shows a QR code; the guest scans it and tracks live queue position via a web page with push notifications.

How do reservations and waitlist coexist? Reservations are fixed slots, waitlist is dynamic. The system blocks reservation holds first, then opens remaining capacity to the waitlist pool.

Any penalty for no-shows? No legal penalty in most regions, but flag guests after three consecutive no-shows so the host sees a "high-risk" warning at check-in.

Found this helpful? Share it.