Real time · 01 / 10
The booking engine that knows your dining room better than your diary.
Availability calculated in real time from the actual floor plan: every table, every service, every turn-time constraint. What the guest sees online is what the room can genuinely absorb.
See this module in a demo
What it changes
The details that hold a service together.
A living floor plan
The floor plan is the source of truth. Merging and splitting tables, zones, a terrace that depends on the weather, banquette constraints: the availability engine reads the room as it is tonight, not as it was configured in January.
Automatic allocation
For every request, OpenFlow seats the party where it costs the least lost turn. The maître d’ keeps control: a drag and drop reassigns, and the engine recalculates the open slots behind it.
Card holds and deposits
A card hold above a set party size, a deposit on group menus, cancellation terms configurable per service. Penalties trigger on their own, with a record of the terms the guest accepted.
Waiting list and reminders
A walk-in queue with an estimated wait, an SMS when the table frees up, and two confirmation reminders before service. The no-show becomes a documented exception.
Shifts and capacities
Cover limits per slot and per kitchen station, not only per room. The pass no longer takes twelve starters in eight minutes because the diary could not count.
Unified inbound channels
A widget on your site, Reserve with Google, phone, walk-in, conversational AI: everything lands in the same diary, under the same availability rule.
How it works
Four moments, one single entry.
The module never asks for the same information twice. Each step writes to the shared database, and the next one reads what it needs from it.
- 01
The guest asks
On your site, through Google or by phone. The engine queries the floor plan and only offers slots the room can actually serve.
- 02
The room absorbs it
The table is allocated, the kitchen capacity updated, the bill opened at the till with the guest’s preferences attached.
- 03
Service runs
Arrivals marked, table opened at the till, late parties flagged, waiting list moved automatically onto the tables that free up.
- 04
The data stays
Ticket, allergens, wine ordered, visit frequency: everything flows into the CRM record without a second entry.
Measured at our customers’
Figures recorded in operation, not in a laboratory.
- 41%
- fewer no-shows after six weeks of automatic reminders
- 2.4
- average turns recorded across evening services
- 0.6 s
- to recalculate availability for a full service
For which industries
The configuration changes with the industry.
The module is the same. The capacities, the permissions and the indicators are not.
Frequently asked
What people ask us before signing.
Can we keep our current floor plan?
Yes. The plan is redrawn exactly as it is during setup, using your existing table numbers, so the floor team has nothing to relearn.
What happens if the connection drops during service?
The diary stays readable and editable locally on the terminals and tablets. Changes resynchronise as soon as the network returns, with conflicts resolved by timestamp.
Do bookings reach the point of sale?
Automatically. The table opened at the till carries the guest’s name, their notes and their history, which also allows the bill to be transferred to the room in hotel properties.