# Oddle Reserve Oddle Reserve gives your restaurant its own direct reservation channel — with all the essentials you need for bookings, seating, and no-show controls, without unnecessary complexity. Guests book through your branded booking page, your website, Reserve with Google, or your Oddle Shop. Every reservation flows into one place: the Host App, where your floor team manages the day-to-day. The smart part? Reserve is connected to the rest of Oddle. Every booking captures guest data that feeds into Customer Intelligence and Marketing — so follow-ups like cancelled reservation win-backs and lapsed guest re-engagement happen automatically, without a separate tool. *** ## Key Concepts Before diving in, here's how Oddle Reserve is structured: **Tickets** define *what* guests can book — a standard table reservation, a prix fixe dinner, an outdoor brunch. Each ticket has its own capacity rules, payment settings, and availability. **Schedules** define *when* those tickets are available. You set weekly recurring schedules, override them with special schedules for holidays or events, and block out dates when you're closed. **Tables & Floor Plan** define *where* guests sit. You set up your areas, tables, and seating capacity — then your floor team handles the rest from the Host App. *** ## Where to Manage What Reserve settings live in two places: **Merchant Admin** (`panel.oddle.me`) is where you manage your booking channels — your reservation link, website widget, and Oddle Shop reservation page. This is also where you configure brand-level settings like house rules. **Host App** (`host.oddle.me`) is where your team manages everything operational — schedules, tickets, tables, floor plan, notifications, and day-to-day reservations. Most of the setup covered in this section happens here. *** ## In This Section * [**What Your Customers See**](/docs/new-guests/reserve/reserve-overview.md) — The guest booking experience from start to finish * [**Setting Up Your Booking Page**](/docs/new-guests/reserve/setting-up-reservations/setting-up-booking-page.md) — Booking channels, page settings, and house rules * [**Tables, Capacity & Floor Plan**](/docs/new-guests/reserve/setting-up-reservations/tables-capacity-floor-plan.md) — Areas, tables, combinations, and your visual floor plan * [**Tickets & Schedules**](/docs/new-guests/reserve/setting-up-reservations/tickets-and-schedules.md) — Define what guests can book and when * [**Prepayment, Deposit & Cancellation Window**](/docs/new-guests/reserve/setting-up-reservations/prepayment-deposit-cancellation.md) — Payment collection and cancellation settings * [**Reserve with Google & Other Booking Channels**](/docs/new-guests/reserve/setting-up-reservations/reserve-with-google.md) — Google integration, widgets, and Oddle Shop * [**Notification Settings**](/docs/new-guests/reserve/setting-up-reservations/notification-settings.md) — Customer confirmations, team alerts, and SMS * [**Managing Reservations Day-to-Day**](/docs/new-guests/reserve/managing-reservations.md) — Statuses, auto-updates, and handling arrivals * [**Make Every Booking Work For You**](/docs/new-guests/reserve/make-every-booking-work-for-you.md) — How every reservation powers automatic follow-ups and grows your guest database --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://www.oddle.me/docs/new-guests/reserve.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.