Sari la conținut

Nemvio for restaurants

Bookings taken while you’re serving tables

You don't get a booking module inside a platform. You get the bot built around how you actually work: your tables, how many seats each one has, and which hours you take reservations. It takes the reservation on WhatsApp at any hour, picks the right table on its own, sends a reminder with a confirm button, and you see the whole dining room in the panel.

Example conversation

From the first question to a confirmation, without anyone replying.

I'd like a table for 4, Friday evening.

We have Friday at 19:00 or 20:30 open, for 4 people. Which time works for you?

20:30, please.

Reservation confirmed: Friday, 20:30, table for 4. See you soon!

What you get

What we build for a restaurant

Not a platform for you to configure. We build these ourselves, around how you already work.

The right table, picked on its own

It knows your tables and how many seats each has. For a party of 4 it picks the smallest free table they fit at, so the big tables stay free for big groups.

The booking, at any hour

The customer writes whenever, including after hours. The bot checks what's free and confirms on the spot, without pulling anyone away from a table.

A reminder with Confirm or Cancel

It goes out on its own before the reservation, with two buttons. The customer confirms in one tap, and a cancellation frees the table for whoever is waiting.

The daily special, hours, and address

You update them in the panel. You write the daily special in the morning, the bot tells whoever asks, and it disappears on its own the next day.

Your panel

What stays behind after every conversation

The conversation does not end in WhatsApp. Everything the virtual assistant did lands in the panel, where you can step in any time.

The dining room, table by table

Your tables on a drawing of your own room, each with its state: free, reserved, or seated. On your phone or your computer.

The reservation details

Who booked, for how many people, at what time, and anything extra they asked for, from a birthday to a high chair.

The whole conversation

Everything that was written, if you want to check something or step in.

One tap when they leave or never come

Free the table when the guests leave, or note that they did not show up. That way you know who tends not to come.

Honestly

What the virtual assistant will not do

We would rather you know where it stops from the start than find out after launch.

No delivery orders by default

The booking bot takes bookings. Delivery can be built separately, but we settle that at the start, it does not appear on its own.

It never overbooks

If there is no free table, it offers another time or puts them on the waiting list, and writes to them on its own when a table frees up.

No answers on allergens

It says only what your own up-to-date menu says. For anything beyond that, a person on your team takes over.

Not just the assistant

What else we build for a restaurant

The virtual assistant is one piece of four. The site and the calls connect straight to it, and AI automations we implement separately, across the rest of the business.

Website

A site with your menu, hours, and address, updated from the same panel, with a booking button that opens the WhatsApp conversation.

WhatsApp calls

Customers who call at peak hour get a spoken answer and make their reservation, without anyone leaving a table.

AI automations

Separately from the assistant, we implement AI automations in the business's own processes, so the repetitive work gets done on its own.

You can start with a single system. Most projects do, and the rest gets added when you need it.

How it starts

From the first conversation to launch

The same process for any project, with the price known upfront and no technical jargon.

01

A free first conversation

You tell us how you work today. We tell you exactly what can be automated and what it costs, before anything starts.
02

We build the system

Usually 1-2 weeks for the WhatsApp virtual assistant. It takes that long because we build it around how you work, not from a template. You configure nothing, you just answer our questions.
03

Launch, then maintenance

The first 30 days after launch are included. After that, a monthly subscription keeps everything running.

What we need from you

  • Your tables, how many seats each has, and which hours you take reservations
  • The menu and the information you want the bot to give
  • The WhatsApp number you want the virtual assistant to answer on

That is it. The rest is on us.

FAQ

Questions about this

What people ask most often before starting a project in your field.

01

How do I see the day's reservations?

They all appear automatically in the panel, on a drawing of your own room: every table, who is coming and when, on your phone or computer.
02

What does it do with large groups?

You decide from how many people a reservation needs a person to look at it. Above that, the bot does not confirm on its own: it notes the request and alerts you, and you decide.
03

Can it take delivery orders too?

Not together with the booking bot. It gets built separately if you need it, and we discuss that in the first conversation.
04

Who configures the virtual assistant around the restaurant's schedule?

We do, before launch. You tell us how you work, we build the assistant around your schedule.
05

How long until it goes live?

Usually 1-2 weeks for the WhatsApp virtual assistant. It takes that long because everything is set up for your restaurant, not taken from a template. The first 30 days after launch are included.

Let's see how it fits your business

Tell us how you work today and we'll tell you exactly what can be automated, before we start anything.

Let's talk

More fields

See how it looks for another kind of business