Twenty Seats. Forty People Waiting. No System.

The Real Problem

Kenji runs a 20-seat ramen shop on Ponsonby Road. The ramen is excellent. The problem is everything that happens before you sit down.

At 12:15pm on a Saturday, every seat is full. There are eight people standing outside the door, and more walking up. Three of them look at the queue, check their phones, and keep walking. They'll grab a burger somewhere else. Kenji watches this happen from behind the counter and there's nothing he can do -- he's making ramen.

There's no host. There's no waitlist clipboard. There's no buzzer system. There's just a loose crowd of people standing on the footpath, some of whom have been there for 10 minutes and some who just arrived, and nobody is quite sure who's next. Occasionally someone pokes their head in the door and asks "how long?" and whoever's closest to the door shrugs and says "maybe 15 minutes?"

This is the reality for small-format Asian restaurants across Auckland. Twenty to thirty seats, perpetual queues at peak times, and zero infrastructure to manage the wait. Research shows 75% of customers abandon a queue if the wait exceeds 20 minutes -- but without a system, customers don't know if the wait is 10 minutes or 40 minutes. So they leave at the first sign of a line.

Kenji estimates he loses 30% or more of potential lunch customers to walkaway. At an average spend of $22 per person, that's hundreds of dollars every service. Multiply that across a week and it's thousands in revenue that walked past his door and kept going.

Why Existing Tools Don't Solve This

Virtual queue apps exist. Carbonara and NextMe both offer digital waitlists. But very few small NZ ramen shops or noodle bars use them. The setup assumes you have a host at the door entering names into an iPad. Kenji doesn't have a host. He has himself, a kitchen hand, and one floor person who's clearing tables and running bowls.

First Table -- New Zealand's most popular restaurant booking app with over 1,200 restaurants -- is designed to fill empty tables at off-peak times. It's a booking platform, not a queue management tool. It doesn't help when you have 40 people wanting to eat right now and only 20 seats.

Your POS tracks what's sold but has no idea who's waiting outside. Google Waitlist (via Reserve with Google) exists but requires specific POS integration that most small operators don't have. And none of these tools learn from your actual service pace to give accurate wait times.

How AI Solves This

There's a small sign next to Kenji's door with a QR code and a simple message: "Scan to join the queue. We'll text you when your table's ready."

A customer scans the code. It opens a WhatsApp chat:

AI: "Welcome to [Kenji's Ramen]! How many in your group?"

Customer: "2"

AI: "Got it -- party of 2. You're number 6 in the queue. Estimated wait: about 14 minutes.

You're free to wander -- grab a coffee at the place next door, check out the shops. I'll message you when your table is 5 minutes away, and again when it's ready.

While you wait, want to look at our menu? Our tonkotsu and spicy miso are the most popular today."

The customer walks next door, orders a flat white, and browses the menu on their phone. Ten minutes later:

AI: "Heads up -- you're next! Your table should be ready in about 3-4 minutes. Head back when you're ready."

Two minutes later:

AI: "Your table is ready! Head inside and take any open seat."

No standing in the cold. No awkward crowd at the door. No uncertainty about how long the wait will be. The customer had a good experience before they even sat down.

What Staff See

Kenji's floor person has a simple dashboard on a tablet behind the counter:

• Current queue: 8 parties (14 people total)
• Average wait: 16 minutes
• Next 3 up: Party of 2, Party of 4, Party of 1
• Table status: 3 finishing up, 2 just seated, 1 paying

When a table clears, the floor person taps "seat next" and the AI messages the next party. That's it. One tap. No names to call out, no head-counting the crowd, no arguments about who was here first.

Pre-Ordering While Waiting

Customers in the queue can browse the menu and even pre-select their order:

Customer: "I'll do the tonkotsu with extra chashu and a karaage starter."

AI: "Noted! I'll pass your order to the kitchen as soon as you're seated so it comes out faster. Your friend can order from the table when they're ready."

When they sit down, the kitchen already has their order. The bowl hits the table three minutes after they're seated. Table turnover speeds up. More customers served per hour.

Smart Wait Time Predictions

The AI doesn't just count the queue -- it learns. After two weeks of data, it knows that:

• Average dining time for a party of 2 is 28 minutes
• Parties of 4 take about 40 minutes
• Saturday lunch from 12-1pm has the longest average wait
• After 1:30pm, the queue drops and walk-ins can be seated immediately

Wait time estimates get more accurate over time, which means fewer customers leave because they were told "15 minutes" and waited 30.

How We Set This Up

None of this works if the AI is just a standalone chatbot with no connection to your actual restaurant operations. That's why BestAI builds a custom integration program -- a piece of software that bridges your AI assistant with the systems you already use.

For this kind of setup, that means:

• Creating a QR code sign for your entrance that connects customers to the queue via WhatsApp
• Building a simple staff dashboard (tablet or phone) for managing table status and seating
• Connecting the queue system to WhatsApp so customers get real-time updates automatically
• Setting up smart wait-time prediction that improves as the system collects data on your actual service pace

Here's our process:

1. We map your current workflow -- We visit during a busy service, observe the queue situation, and figure out how tables turn over and where the bottlenecks are.
2. We build the connections -- Our developers write a custom program (an API connector) that powers the queue, the messaging, and the staff dashboard. No off-the-shelf software that almost-but-doesn't-quite fit.
3. We test end-to-end -- We run the system during a real service before going fully live. We adjust wait-time estimates, notification timing, and the customer flow based on what actually happens.
4. We maintain it -- When you change your hours, expand your seating, or want to add features like pre-ordering, we update the system to match.

You don't need to be technical. We handle all the development -- you just tell us how your restaurant runs, and we make the AI fit into that.

The Result

• 30% fewer walkaways -- customers join a virtual queue instead of seeing a line and leaving
• No crowd at the door -- people wait at nearby cafes, shops, or just walk around the neighbourhood
• Accurate wait times -- AI learns your actual table turnover, so estimates are honest and trusted
• Faster table turnover -- pre-ordering means food arrives minutes after seating, not 15 minutes after
• Staff stay in the kitchen -- nobody has to manage the door or shout names into a crowd
• Fair, transparent queue -- no more "who was here first?" disputes

What AI Can't Do Here

• AI won't seat people -- your staff still need to clear tables and signal when a seat is available
• AI won't stop no-shows -- some people will join the queue and wander off. The system skips them after two unanswered notifications
• AI won't manage reservations -- this is a walk-in queue tool, not a booking system
• AI can't account for unusually slow tables -- a group that lingers over drinks will throw off the estimate until the system adapts

Who This Is For

• Small-format restaurants (under 30 seats) with regular queues at peak times
• Ramen shops, dumpling bars, noodle houses, and similar fast-casual spots
• Any restaurant without a dedicated host to manage walk-in flow
• Owner-operators who lose customers every service because people see the line and leave