As of November 2026 · CODLAB editorial team
Short answer: A reservation system helps a restaurant most when the phone, its own website and the floor plan all write into the same book. Before switching, check whether tables are assigned in real time, whether a waiting list runs alongside, which guest details are really needed and who processes the data.
1. Why separate channels lead to double bookings
In a restaurant, reservations arrive from several directions: calls during service, requests through the restaurant’s own website, guests at the door and sometimes third-party platforms. Each of these sources is harmless on its own. Problems start when they end up in different lists – a paper book next to the phone, an inbox for website requests, a tablet at the host stand. Then it is down to chance who checks first, and the same table can be given away twice.
A shared reservation book does not solve every problem, but it removes one source of error: nobody has to reconcile lists any more. Every booking, whatever the channel, immediately occupies the same table on the same plan.
2. What belongs in a shared reservation book
- A real-time floor and table plan: during service the team sees which tables are free, reserved or occupied and can combine tables for groups without shouting across the room.
- A waiting list: when an evening is fully booked, a cancellation should not go to waste. A waiting list makes freed-up tables visible for guests who are waiting.
- Guest details with a clear purpose: a name, the number of guests, the time and a way to call back are usually enough. Preferences or allergy notes belong in the book only if the guest shares them and the team needs them for the visit.
- Your own website as an entrance: a reservation made on your own site stays with the restaurant and goes straight into the book instead of passing through someone else’s portal first.
3. Platforms and dependency
Reservation portals can bring new guests. They also change the relationship, because the guest then books through a third party. So check the terms to see who may use the guest data, whether fees apply to reservations and how easily your data can be exported if you want to switch. A system that charges no commission on your own bookings separates the question of the reservation book from the question of advertising.
4. Guest data under the GDPR: minimal, purpose-bound, deletable
Article 5 of the GDPR lists, among others, the principles of purpose limitation, data minimisation and storage limitation. For a reservation book this means in practice: collect only what the visit requires, do not use guest data for marketing without asking, and delete old entries after a defined period. Also clarify where the system processes data and which services are involved – this belongs in your privacy notice.
5. When the phone rings and nobody has time
The call at half past seven, in the middle of a full service, is the classic case. This is where Hallo Pronto comes in, the AI phone assistant from our product overview (provider: Riservati GmbH): it answers restaurant calls when nobody has time and takes down callback requests. With the Riservati reservation book, the assistant checks for free tables and enters the reservation directly in the book. Here too, the shared book is what matters: an assistant writing into a list of its own would only move the problem from section 1 elsewhere.
6. How to test a system before switching
- Play through an ordinary evening: phone, website and walk-in guests book one after another on the same plan.
- Test the edge case: two channels want the last free table at the same time.
- Cancel a reservation and watch whether the waiting list makes the table visible.
- Ask to be shown how guest data is exported and deleted.
- Ask about the data path: which services process guest data, and where?
7. Riservati at a glance
Riservati is listed in our product overview as a reservation system in use (provider: Riservati GmbH): commission-free reservations, with phone, floor plan, guests and the restaurant’s own website in one system, a real-time floor and table plan, a guest CRM and waiting list, and disclosed European AI processing with Mistral through an EU/EFTA endpoint. Details are on riservati.de (in German). If you need a custom solution for your own workflows instead, get in touch through our contact page.
Frequently Asked Questions (FAQ)
Not necessarily, but it helps: a reservation made on your own site stays with the restaurant and goes straight into the shared book. According to our product overview, Riservati brings phone, floor plan, guests and the restaurant’s own website together in one system.
Without help they are lost or returned later. According to our product overview, Hallo Pronto answers restaurant calls when nobody has time, takes down callback requests and, with the Riservati reservation book, enters reservations directly in the book.
Only what the visit requires: usually a name, the number of guests, the time and a way to call back. The GDPR requires purpose limitation, data minimisation and storage limitation, so set a deletion period and do not use guest data for marketing without asking.