AI Support Platform · Restaurants & Cafés
Every table request answered, even mid dinner rush.
A guest messages during service asking for a table for four tomorrow at 7pm, or whether a dish is vegetarian. Your AI assistant answers from your real floor plan and your real menu — books the table, quotes the price, and never double-books a seat. If it can't help, your staff take over in one tap.
The table you don't confirm is the one you lose
What's actually happening during service
Nobody can pick up at 7:30pm
The phone rings during the rush and stays unanswered — the caller books somewhere else instead of waiting.
"Do you have vegetarian?" sits unread
A DM asking about allergens or spice level goes unanswered for hours — and often decides whether they book at all.
Two staff, one table, double-booked
The phone log and the walk-in book don't talk to each other — and the same table gets promised twice.
Reservations that hold, menu answers you can stand behind
What you get
Bookings without a phone call
Party size, date and time are checked against your real floor plan, service hours and last-seating cutoff — right in the chat.
No double-booking, structurally
Two guests can't be assigned the same table for the same time — it isn't a policy staff have to remember, it's enforced by the system.
Menu questions, answered from your menu
Vegetarian, spice level, portion size, allergens, live price and currency — pulled from what you actually serve, never guessed.
Live on your site in four steps
How it works
Pick the Restaurant preset
Seeds a host-stand persona, starter FAQs, and switches on table-booking mode for you.
Set your tables & service hours
Table types, zones, capacity, and lunch/dinner service periods with slot length and last-seating cutoff.
Upload your menu
Dishes with price, tags and allergen info — or upload the PDF you already hand to guests.
Paste one line into your site
A single <script> tag from the dashboard. No app to install, nothing for guests to download.
What you and your guests actually see
See it
Representative mockups of the real dashboard and widget — not stock photos.
Availability, day view
One lane per table across the evening — click any cell to prefill a new booking.
Menu item
The assistant searches these exact fields — vegetarian, spice level, allergens, price.
Staff inbox
Handoffs land here in real time — claim, reply, and resolve without leaving the dashboard.
Reservation drawer
Staff bookings use the same live availability check the chat assistant uses.
Built for how a restaurant actually runs
Everything inside
Table types & zones
Indoor, terrace, private room — each with its own capacity range, all bookable from chat.
Real service periods
Lunch and dinner windows with slot length, table turn time and a last-seating cutoff — not a generic time picker.
Honest "no" reasons
"Fully booked" and "we're closed" are told apart — no confusing dead-end answers.
Opening hours, answered live
Including holiday exceptions and past-midnight closing — the assistant always knows if you're open right now.
Bilingual menu
Dish names, descriptions, variants and inventory — searchable in Vietnamese and English.
FAQs in your own words
Answered verbatim, instantly — no LLM paraphrasing your policy.
Lead capture
Name, phone or email and intent — captured mid-conversation, ready for you to follow up.
Instant human handoff
By keyword, by the guest asking, or by your staff claiming a chat — the bot goes silent the moment a human takes over.
Guest directory
Names, phone numbers and visit counts build up automatically as bookings come in.
Any language your guests speak
The AI replies in whichever language a guest writes — far more than Vietnamese and English. Your own dashboard is available in those two today, with more on the way.
Team notifications
A signed webhook fires on every handoff, lead and booking — route it to your existing workflow (e.g. via n8n).
One embed line
A single script tag with your key — works on any website, positioned left or right.
The questions every owner asks first
Before you ask
It won't make things up
Prices, dishes and hours come only from your menu, FAQs and documents — a hard rule blocks the assistant from guessing.
Your guest data stays yours
Chat runs on a local-first language model — nothing is required to leave your infrastructure to answer a routine question.
It never pretends to be a human
And it never names its own internal tools or source documents to a guest — those are hard rules, not a style choice.
Protected against abuse
Domain allow-listing, short-lived visitor tokens, per-visitor rate limits, and a daily spend cap that degrades gracefully to FAQ answers instead of overspending.
Straight answers
FAQ
Does it work on my existing website?
Yes — one script tag, no matter what your site is built with. It appears as a chat launcher in the corner of the page.
Can guests still cancel or change a booking?
Yes — a guest can cancel their own reservation from the same conversation using the reference code, or your staff can do it from the dashboard.
What happens when we're fully booked?
The assistant tells the guest plainly that the requested time is fully booked rather than guessing at a table — and can offer a human handoff for a waitlist request.
Is it limited to Vietnamese and English?
No — the AI itself can reply in whichever language a guest writes in. What's limited to Vietnamese and English today is the admin dashboard your staff use; more admin languages are on the roadmap.
Can I edit what it says?
Yes — persona, greeting, menu and FAQs are all yours to edit any time from the dashboard.
Does it answer on Facebook or Zalo?
The live channel today is your website widget. You can still route handoffs, leads and bookings to your team on other channels via a webhook (for example, through n8n).
Ready when you are
Stop losing the reservation nobody picked up
Set it up once with your tables, menu and service hours — it answers and books from that moment on.