Booking policies and setup
Set your booking page and its address, choose auto-confirm or manual review, and lay out zones, slots, covers and closures.
Everything a guest meets is set in two rooms of the ops console: Admin → Guest app for the page and its rules, and Admin → Floor setup for the room itself. Both collect your edits as a draft and put them live with one Apply changes, so a half-finished change never reaches a guest.
Guest app → Booking page
Public address is where guests find you. Pick a booking page address of 3 to 40 lowercase letters, numbers and single hyphens; the page shows the composed URL with a Copy button and a QR button that opens a printable sheet for a table tent or a door. A Live switch decides whether the page answers at all.
Renaming keeps the old address working, so printed links still resolve. A few words are reserved by the app and refused.
Appearance sets the accent colour and the corner shape. Brand and Outlet details carry the name, tagline, address, contact number and icon. A phone-shaped live preview beside the fields shows the guest page as you edit.
Guest app → Booking rules
New bookings holds the one decision that changes how your whole day works:
| Auto-confirm | What happens |
|---|---|
| Off | “You review each request.” Bookings wait under Incoming as pending until someone confirms them. This is the default, and what the bell is built for. |
| On | “Requests confirm instantly.” Bookings are confirmed the moment they arrive, so Incoming will rarely fill and you watch the confirmed list instead. |
Booking rules sets three numbers:
- Hold table for: 10, 15, 20 or 30 minutes. How long a table waits past the booking time before it goes back to the floor. This is the number your house rules quote to the guest.
- Free cancellation up to: 1, 2, 4 or 6 hours. This one window governs both cancelling and requesting a change.
- Max party size online: 1 to 50. Larger parties are offered the enquiry path rather than a dead end.
House rules are the rows a guest reads at the bottom of the form, in the order you set. The hold rule and the cancellation rule are always there, cannot be switched off, and always compute their number from the settings above, so the page cannot promise something you no longer do. Alongside them you can run a call-ahead rule, a no-outside-food rule, and your own custom rules.
Guest form options edits the Occasions and Allergens chips. Guests always get a None option on occasions, and can always add their own allergen under Other, so neither list has to be exhaustive.
Floor setup
Five tabs, in the order a venue is set up.
- Floor is the map itself: the tables, where they sit, and how many each seats.
- Slots is what the booking page offers. Add a slot with its times and the days of the week it runs.
- Covers caps how many covers a given slot can take in a given zone.
- Zones names your rooms and decides which are bookable online, each with its own Online switch and its table and seat count.
- Closures blocks a date, either the whole day or one slot, with an optional reason.
A publish bar above the tabs republishes the guest configuration when you apply.
What is set elsewhere
Who can sign in to Reserve and what role they hold is managed in Admin → Users, and across Maska in the console’s Users page. Your own name and contact details are read-only inside Reserve.