The Real Problem
Mei owns a 60-seat hotpot restaurant in Auckland CBD. It's 6:45pm on a Saturday. Every table is full. Two groups are waiting near the door, checking their phones. The phone is ringing -- it hasn't stopped since 5pm.
Her floor staff are busy. One is helping a table of first-timers understand how the soup bases work. Another is restocking the sauce bar. A third is clearing a table and resetting it for the next booking. Nobody can answer the phone.
Mei picks it up herself, wedged between the host stand and the kitchen pass.
"Hi, can I book a table for tonight? There's six of us."
"Sorry, we're fully booked tonight. I can put you on the waitlist -- maybe 45 minutes?"
"How long exactly? We have kids."
"I'm not sure, it depends on --"
Another call is ringing on the second line. A group of walk-ins has just arrived at the door. Mei puts the caller on hold, seats the walk-ins, goes back to the phone -- the caller has hung up.
This plays out every Friday and Saturday. Mei estimates 15 to 20 missed calls per weekend. Some of those are groups of 8 or 10 -- the most profitable tables. She has no waitlist system beyond a scribbled notebook. No way to tell walk-ins how long the wait actually is. And no way to confirm bookings automatically -- she or her staff have to call or text each one manually.
Auckland's hotpot market is growing fast. Haidilao has opened. Little Sheep, Happy Lamb, and a wave of independents are competing for the same diners. The restaurants that make booking easy win the customer. The ones that don't answer the phone lose them.
Why Existing Tools Don't Solve This
Hotpot restaurants have needs that generic booking platforms don't address. A standard booking system takes a name, time, and party size. But hotpot bookings involve:
- Soup base preference -- individual pots or shared? Spicy, mild, tomato, mushroom?
- Dietary needs -- vegetarian broth options, shellfish allergies, halal requirements
- First-timer vs. regular -- first-timers need guidance; regulars already know what they want
- Group composition -- families with kids need different seating than a group of adults
Chowbus, the best POS for hotpot restaurants, is US-only. ResDiary and OpenTable have minimal NZ traction and no hotpot-specific features. None of them handle bilingual booking -- and for Auckland hotpot, that's essential. Mei's customer base is roughly split between Chinese-speaking and English-speaking diners. Her Chinese customers prefer to book in Mandarin. Her Kiwi customers book in English. No existing tool handles both seamlessly.
And the waitlist problem? There's no affordable waitlist management for a 60-seat restaurant. Enterprise solutions exist, but they're designed for 200-seat venues with dedicated host teams.
How AI Solves This
Mei's AI booking assistant works across phone, WhatsApp, and her website -- in both English and Chinese.
English Booking
A customer calls at 5:30pm Saturday:
"Hi, thanks for calling Mei's Hotpot! I can help you with a booking. How many in your group, and what time were you thinking?"
"Six of us, around 7pm tonight."
"Let me check... 7pm is fully booked, but I have a spot at 7:30 -- would that work?"
"Yeah, that's fine."
"Great! A couple of quick questions -- have you been here before?"
"No, first time."
"You're going to love it. I'll send you a quick 'How to Hotpot' guide so you know what to expect -- soup bases, how the cooking works, our sauce bar. Any dietary requirements in your group? Allergies?"
"One person is vegetarian."
"No problem -- we have a mushroom broth that's fully vegetarian, really popular. I'll note that down. Can I grab a name and mobile number for the booking?"
The customer gets an instant confirmation text with:
- Booking details (6 pax, 7:30pm Saturday)
- A link to the "How to Hotpot" first-timer guide
- Note that vegetarian broth has been reserved
- Cancellation policy
Chinese Booking (Mandarin)
A customer messages on WhatsApp in Chinese:
"你好，周六晚上7点可以订位吗？4个人。"
"你好！周六7点有位置，4位没问题。请问需要什么锅底？我们有麻辣、番茄、菌菇、清汤可以选择。拼锅也可以。"
"一个鸳鸯锅，半边麻辣半边番茄。"
"好的，鸳鸯锅已经帮你备注了。请问有忌口或过敏的吗？"
"没有。"
"好的！请留一下姓名和手机号码，我帮你确认预订。"
Same system, same data, seamless language switching.
Waitlist Management
When the restaurant is full, the AI doesn't just say "sorry, we're booked." It manages a live waitlist:
"We're full right now, but I can add you to our waitlist. Current estimated wait is about 35 minutes. I'll text you when your table is ready -- you don't need to wait at the door. Want me to add you?"
The customer gets a text when they're 10 minutes away from being seated. No more hovering awkwardly by the entrance. No more "how much longer?" questions to staff.
No-Show Prevention
For groups of 6 or more, the AI sends:
- 24-hour reminder with booking details and an option to modify
- 2-hour reminder with a deposit link for large parties
- If no response to either reminder, Mei gets flagged to follow up or release the table
Mei was losing 2 to 3 large-group no-shows per weekend -- tables of 8 or 10 that had food pre-prepared based on expected headcount. Each no-show cost $400 to $500 in wasted prep and lost revenue from turning away other diners.
How We Set This Up
None of this works if the AI is just a standalone chatbot with no connection to Mei's actual restaurant. That's why BestAI builds a custom integration program -- a piece of software that bridges the AI assistant with the systems Mei already uses.
For this kind of setup, that means:
- Connecting the AI to WhatsApp, the restaurant's phone line, and the website so bookings flow in from every channel
- Building a real-time table availability system that the AI checks before confirming any booking
- Setting up automated SMS confirmations, reminders, and waitlist notifications in both English and Chinese
- Creating the bilingual "How to Hotpot" guide that gets sent to first-time diners automatically
- Integrating with Mei's POS so reservation data syncs with table management
Here's our process:
- We map your current workflow -- We sit down with Mei and understand how bookings, walk-ins, and the waitlist currently work. Every restaurant handles this differently.
- We build the connections -- Our developers write a custom program (an API connector) that lets the AI talk to your booking system, POS, and messaging channels. No manual data entry, no double-handling.
- We test end-to-end -- We run test bookings through the full pipeline -- phone call to confirmation text to table assignment -- before going live. Nothing launches until it works reliably.
- We maintain it -- When Mei changes her hours, menu, or seating layout, we update the AI 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
- Zero missed booking calls -- AI handles unlimited concurrent enquiries across phone, WhatsApp, and web
- Bilingual service -- Chinese and English customers both get a seamless experience in their preferred language
- First-timer education -- new customers arrive knowing how hotpot works, reducing staff explanations on the floor
- Live waitlist with SMS updates -- walk-ins get estimated wait times and text notifications, no more crowding the entrance
- Fewer no-shows -- automated reminders and deposit links for large groups cut no-shows significantly
- Staff stay on the floor -- nobody gets pulled away from tables to answer the phone during service
What AI Can't Do Here
- AI won't manage table turns in real time -- it books based on availability you configure, but floor decisions (extending a table, moving guests) are human calls
- AI won't handle complaints or service issues -- if a customer is unhappy with their experience, that needs a person
- AI can't predict exact wait times -- it estimates based on booking data, but walk-in flow is unpredictable
- AI won't replace the personal touch -- regulars who want to chat with Mei about the new seasonal menu deserve a human conversation
- The bilingual system works for English and Chinese -- other languages would need additional configuration
Who This Is For
- Hotpot restaurants with heavy weekend booking demand and no reservation system
- Asian dining venues with bilingual customer bases (Chinese + English)
- Restaurants losing bookings because phones go unanswered during service
- Venues with regular walk-in waits and no waitlist management system
- Any restaurant where no-shows on large group bookings are a recurring problem