Industry Verticals
Reservations
Reservations — part of Restaurant Ops.
This page is public — no account required to read features.
Part of Restaurant Ops
Reservations lives inside SerapisERP Restaurant Ops. Guest bookings and timeline.
Every record is organization-scoped. Roles use None / View / Edit / Manage on the parent module so people only see what their job needs. Toggle Restaurant Ops on for orgs that need it — leave it off for everyone else.
Because reservations sits in the same suite as sales, calling, marketing, and finance, the same client or job account can carry commercial and operational context without re-keying.
Capabilities
Reservations
Guest bookings and timeline.
Organization tenancy
Data is isolated per organization — no shared demo bleed across customers.
Role-gated access
Access is controlled through Restaurant Ops permissions (None / View / Edit / Manage).
Cross-module context
Works next to CRM, calling, and finance when those modules are enabled for the org.
FAQ
Is Reservations sold separately?
No. Reservations is part of Restaurant Ops. Platform modules are free to enable; optional usage (AI, SMS, voice, email delivery) is metered at provider cost + 12.5%.
How do I open Reservations?
Enable Restaurant Ops for your organization, invite teammates with the right role, and use the product sidebar for that module family.
Does Reservations share contacts with sales?
When Sales CRM (and other modules) are on for the same organization, records share the same org graph — that is the all-in-one thesis.
One command deck. Every department.
Create your organization, switch on the modules you need, invite your team with the right roles — and get back to running the business.