On this page
AI phone bookings for restaurants: every call answered, even during the rush.
It answers calls in the middle of the rush, when the dining room is full and nobody can get to the phone. It books according to your actual tables, with their capacity and their dining room, and records allergies without mentioning them out loud.
Single plan: €120 + VAT a month · up and running in 1 day · free integration consulting
In a restaurant, the phone rings just when the dining room is full. These are the four most common calls every weekend.
With the dining room full and the phone ringing at the bar, the agent answers the call and, if another comes in, puts it on hold in order of arrival with the option to leave a message, which reaches the panel as a request with an assignee and a deadline.
The agent checks the tables in each dining room with their capacity and the sitting. If at nine there is only a table for four left, it does not offer it for six: it suggests the times when there is a table for the group, and the booking is recorded with its table and dining room.
Allergies, intolerances and conditions such as coeliac disease are stored as health data, encrypted and with the consent recorded: how the person gave it and when. The kitchen and the dining room staff see them when they open the booking, and the agent does not mention them on the phone unless you authorise it.
The customer cancels from the link in the reminder, without needing to call. The table is immediately available again for the next customer. The record logs the no-show risk of anyone who fails to turn up twice.
In phone handling, in the information your team receives, in the setup and in regulatory compliance.
It recognises the customer by their number and addresses them by name. It books, changes and cancels tables on the real chart, with each table’s capacity and the sitting, and it does not offer a time when there is no table for the group. It asks only one question at a time and, if interrupted, even with background noise, it stops talking and listens. If asked to speak to a person, it transfers the call to whoever is available at that moment.
Every call is transcribed turn by turn, with what the agent looked up and how long it took to answer. The bookings chart is shown by day, week and month, with tables and dining rooms as resources and out-of-hours slots marked. Records are created automatically, store health data encrypted and log the no-show risk, and duplicates are merged field by field.
You do not need to register professionals: setting up the tables and dining rooms with their capacity is enough to start taking bookings. The agent is tested before it is published, and the voice can be that of your front-of-house manager, cloned from ten or twelve seconds of recording and with their express consent. The menu, the opening hours and any information you prefer not to share are configured one by one.
An announcement states, as soon as the call is answered, that an artificial intelligence is answering, and it cannot be switched off (Regulation (EU) 2024/1689, Art. 50). Recording is off by default and, if you switch it on, it does not start until the recording notice has played. Allergies, intolerances and coeliac disease are health data: they are stored encrypted, with the consent recorded, and anyone with a view-only role sees them masked. Every time a recording is listened to, it is logged.
The table is a resource with its capacity and its dining room. There is no need to set up anyone from the team: what is booked is the table.
What the customer hears and what is recorded in the panel when the call ends.
01:03
Good afternoon, you’ve called the restaurant. You’re speaking to a virtual assistant powered by artificial intelligence. How can I help you?
Good afternoon. I’d like a table for six on Saturday at nine.
At nine, only a table for four is still available. For six people, I can offer you half past nine in the downstairs dining room or eleven in the main dining room. Which would you prefer?
Half past nine is fine. Oh, and one of the girls is coeliac.
Thank you for letting us know. This is health information: do you authorise me to add it to your record so that the kitchen and the dining room staff can see it?
Yes, of course.
It has been recorded in encrypted form. Let me confirm: Saturday the 20th at half past nine, six people, downstairs dining room.
Perfect.
Your booking is confirmed, Ms Gil. I will send you a link in case you need to cancel it or change the number of diners. Thank you for calling.
Marta Gil · recognised by her number
Sat 20, 21:30 · 6 people · downstairs dining room, table 7
coeliac disease (diner) · encrypted · verbal consent recorded
3, with a link to cancel
Dialogue re-created for this page, with made-up names. It is not the recording of any real call or of any real customer.
Customers, bookings, tables and dining rooms. Real screenshots of the panel, unretouched.
The agent books on this chart. Slots blocked by your team are never offered by phone, and out-of-hours times can only be assigned from the panel.
How many came in, how long they lasted and which ones are worth reviewing. Each call can be opened and read in full, turn by turn.
Up and running in 1 day and set up with your dining rooms, tables and sittings.
Each table has its seats and its dining room, and capacity is calculated automatically. If there is no table for the group at a given time, that time is not offered by phone.
Tables are booked, not people: you do not need to create staff records or timetables to start taking calls.
They are stored as health data, encrypted and with the consent recorded: how the person gave it and when. Anyone with a view-only role sees them masked.
The customer record is created automatically with the first booking, search works without accents and the panel flags records that appear to belong to the same person.
Up to six reminders per booking, each with its own text and time, and a link so the customer can cancel while there is still time. The record keeps each customer’s no-show risk.
Welcome message in your voice, waiting in order of arrival when all lines are busy, the option to leave a message and forwarding to another number.
Answers to the most common questions before you request a demo.
No. In a restaurant you book tables, not people. You only need to set up the tables and dining rooms with their capacity, and the agent books based on that information. You do not need to enter staff shifts to start taking calls.
It stores them in the customer’s record as health data: encrypted, with the consent recorded (how the person gave it and when) and visible to the kitchen and the dining room staff when the booking is opened. The agent does not mention them on the phone of its own accord, and anyone with a view-only role sees them masked.
The plan includes one simultaneous call, expandable to up to 25 in parallel. If all lines are busy, callers wait in order of arrival, hearing your message, and can leave a message that appears in the panel as a request with an assignee and a deadline. The panel shows how many times calls have overlapped, so you can judge whether it is worth adding lines. There is also a mandatory backup number to which the call is diverted if the system fails.
Not yet. Today the agent books, changes and cancels tables, answers questions about opening hours and the menu with the information you provide, and takes note of anything it cannot resolve.
A single plan at €120 + VAT a month, with 1,000 minutes of conversation included. Each additional minute costs €0.65 + VAT. We have it up and running in 1 day, additional integrations are ready within 3 weeks at most and integration consulting is free of charge.
We set up the demo with your dining rooms, tables and capacity, your sittings and whatever information on the menu and opening hours you wish to provide, and we show you the resulting call. We do not need any data about your customers.
Single plan: €120 + VAT a month with 1,000 minutes included · additional minute €0.65 + VAT · up and running in 1 day · free integration consulting