The system

Reservations

Take and shape bookings the way the room runs — floor, deposits, policies, and shifts — on the same record as the order and the payment.

Inservo reservations diary on iPhone

What it covers

Everything the booking touches.

Reservations, orders, and the till are one front-of-house application, not separate systems passing a record between them. Payments are taken on a Stripe terminal, or on the same iPhone over contactless.

Floorplan management
The live plan of the room, shared across the system.
Service shifts
Separate services, each with its own hours, capacity, and pacing.
Deposits and cancellation policies
Deposit and cancellation terms set per service and shown at the point of booking.
Automatic rules
Pacing, capacity, and availability shaped by rule.
Guest profiles and history
Preferences, spend, and reliability on one profile.
Online booking widget
Bookings taken on the restaurant’s own website, written onto the same diary.

Part of one system

A reservation that does not stop at the door.

The booking becomes the seated table, the order, and the payment — one record, no exports, no reconciliation.

Reservations carry through to ePOS and payments on the same record, at 1.4% + 20p on standard UK cards.

Integrations

Bookings and messages, from where guests already are.

Inservo connects to the channels guests already use, so bookings and messages reach the system directly. Guest messaging runs over WhatsApp through the Meta partnership.

Google

Guests book directly from Google Search and Maps.

Facebook

Guests book directly from a restaurant's Facebook page.

Instagram

Guests book directly from a restaurant's Instagram profile.

WhatsApp

Direct messaging with guests over WhatsApp.

A booking is a promise about a table. The system keeps the promise from the first click to the final payout.

Questions

Reservations, answered.

What is a restaurant reservation system?

A restaurant reservation system manages bookings, the floorplan, deposits, and cancellation policies. In Inservo the reservation is not a separate tool: it sits in one front-of-house application alongside the orders and the till, on a single record, so a booking carries through to the order and the bill with no exports and no reconciliation.

Are reservations, orders, and the till separate systems?

No. Reservations, orders, and the till are one front-of-house application on a single record, so nothing is passed between separate tools. Payments are taken on a Stripe terminal, or on the same iPhone over contactless.

Can deposits and cancellation policies be set per service?

Yes. Deposits and cancellation terms can be set by service, and are shown to the guest at the point of booking.

See reservations on one record.

A short walkthrough from the booking to the payout, run against a real service.