Lunch, dinner and terrace
At half past two nobody can put the tray down. The AI receptionist answers on your usual number, takes the booking with its sitting and leaves it in the diary for the floor team to confirm.
Restaurants
Aipiter handles a restaurant’s bookings through the two places they arrive from: the phone, with the AI receptionist, and WhatsApp, with the AI agent. Both check the same menu, the same sittings and the same tables, and each booking goes into the diary as a request, with its place held, for the floor team to confirm. Whoever books stays in the CRM with their visits and what they asked for.
A Saturday on the floor
A Saturday in a forty-cover restaurant with a terrace, from the first coffee to the last table.
On opening, the manager goes through five requests that came in overnight on WhatsApp, each with its sitting and number of guests, and confirms them from each customer’s conversation.
With the dining room full, the AI receptionist takes all three. A table for four on Saturday night, a question about parking and someone asking whether there is a set lunch menu.
On WhatsApp, someone asks which dishes a coeliac guest can have. The agent replies with the allergens you have published on the menu and notes in the request that one of the four is coeliac.
A company wants dinner next Friday. A large group is the restaurant’s call: the agent takes the date, the numbers and whether they want a set menu, and leaves it for the team to phone back.
A couple cancels their half past nine booking. The table is offered again to whoever asked for it and missed out, in order and with a deadline to reply.
With the kitchen closed, another call comes in: lunch for six on Sunday. The agent offers the tables left in the first sitting and the request waits for the manager in the morning.
Six moments that today depend on someone having a free hand, and who looks after each one in Aipiter.
You set your lunch and dinner sittings, your tables or areas and how many guests fit. The agent only offers what is still free in each sitting, so the same table is never booked twice.
The AI receptionist answers every call on the number your customers already know, with the menu, opening hours and sittings in the panel. It does not record the call and notes what each person wanted.
Dishes, set menus and allergens are published once and both agents answer from them. Nothing unpublished is made up: any doubt about an allergy goes to a person on the team.
When someone cancels, the table is offered to whoever was waiting, in order and with a deadline to reply. The first to accept gets it; WhatsApp notices follow Meta’s rules. How it works: appointments and bookings.
Every customer gets a record: their bookings, their messages and what is worth remembering, such as the terrace or an intolerance. It lives in the CRM, in view of the whole floor team.
A large group, an event or a complaint about a dinner goes to the team with the full conversation. The agent does not negotiate prices or compensation: the restaurant decides that from customer service.
Getting started
We set it up with you once, and after that every booking follows the same path.
We load your sittings, your tables or areas and the menu with its allergens into Aipiter. If you keep bookings in another program, its data comes in by file.
The AI receptionist and the WhatsApp agent answer, offer what is free in the sitting and leave each booking with its table held.
The manager sees the requests in the diary by sitting and confirms each one to the customer from their conversation.
In hospitality, many bookings still come in by phone, and they tend to come at the busiest times: the lunch rush and the dinner rush. A call nobody picks up is a table that goes somewhere else.
The AI receptionist works from the same information as the WhatsApp agent. It speaks Spanish and Catalan, introduces itself as an assistant and does nothing the restaurant has not published.
Aipiter is not a point-of-sale system and does not charge for tables: your till, your card reader and your invoicing program stay the same, and invoicing connects through integrations if needed.
If you take bookings through a reservations portal, they keep reaching you there. What Aipiter picks up are the ones that reach you directly, by phone and on WhatsApp, which today are written down by hand.
A bar without bookings still gets calls and messages: opening hours, whether there is a terrace, whether dogs are allowed, whether there is anything lactose-free. The agent answers from what has been published, and the team only steps in when a person is needed.
For bookings that come in by phone and on WhatsApp, yes: the agents offer what is free in each sitting and every request goes into the diary with its table held for the floor team to confirm.
Yes. Your customers keep calling the number they already know and the AI receptionist answers every call. What each person asks for is noted in their conversation, without recording the call.
The agent notes what they need and leaves it in the team’s inbox, and someone calls them back or writes to them as soon as they can. A large group or a complaint always reaches a person.
With the allergens you have published on the menu, yes. If the question goes beyond what is published, the agent does not guess: it passes it to the team.
The table is released and offered to whoever was on the waiting list, in order and with a deadline to reply. If nobody accepts, it stays free for anyone.
No. Aipiter does not take payments or act as a till: it answers calls and messages, keeps bookings in order and stores each customer’s record.
Yes, with appointment reminders on WhatsApp, sent with a Meta-approved message before the day of the booking.
We show you how the AI receptionist would answer with your menu and your sittings, and what the floor team would see of each booking.
Book a demoWith your permission, we use analytics cookies to see how the site is used and improve it. If you reject them, the site works just the same. Cookie policy
