> For the complete documentation index, see [llms.txt](https://www.oddle.me/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.oddle.me/docs/new-guests/reserve/setting-up-reservations/notification-settings.md). # Notification Settings Oddle Reserve sends notifications to both your guests and your team when reservations are made, modified, or cancelled. You configure all of this in the Host App under **Settings > Notifications**. If queue management is enabled for your account, the Settings > Notifications page is split into two cards — **Reserve** (covered below) and **Queue** (see [Queue Management](/docs/new-guests/queue.md) for the full product, plus the [Queue Notifications](#queue-notifications) section near the bottom of this page). *** ## Customer Notifications These are the notifications your guests receive about their reservations. ### Automated Customer Confirmation When enabled, Oddle automatically reaches out to guests to confirm their reservation. Once the guest confirms, the reservation status updates to "Confirmed" automatically — no action needed from your team. If disabled, guests won't be asked to confirm, and the reservation stays in "Booked" status until your team manually updates it. You can enable or disable this under **Customer Notifications > Automated Customer Confirmation**. {% hint style="info" %} Charges may apply for SMS and Automated Call methods. Email is included at no extra cost. {% endhint %} ### Notification Methods for Online Reservations For reservations made online (through your booking page), you choose how guests are notified: * **Email** — Always on by default. Guests receive booking confirmations, reminders, and confirmation requests via email. * **SMS** — Optional. Sends text message notifications. Charges apply. * **Automated Call** — Optional. An automated voice call that prompts the guest to confirm their reservation. Charges apply. The call is triggered when a reservation hasn't been confirmed a set number of hours before the booking time. Requires a call subscription on your account — if you don't have one, the toggle stays off and you'll see a prompt to upgrade. Talk to your account manager to enable it. {% hint style="info" %} **In Malaysia, SMS notifications are delivered via WhatsApp.** When the SMS channel is on for an MY brand, guests receive the message as a WhatsApp message instead of a text — same content, lower friction, no extra setup needed. Singapore and Taiwan continue to use standard SMS. {% endhint %} ### Notification Methods for Manual Reservations For reservations your team creates manually through the Host App, you set a **preferred notification method** — the default channel used when staff add a reservation. Your team can still override this on a per-reservation basis when creating the booking. The same three methods are available: Email, SMS, and Automated Call. You can enable any combination. *** ## Your Notifications These are the notifications your team receives about reservation activity. **Receive Customers' Reservation Updates** — Get email notifications whenever a guest makes a new reservation, modifies an existing one, or cancels. This keeps your team in the loop without having to constantly check the Host App. **Push Notifications** — If your team uses Host App as an installed web app (PWA), they can receive push notifications for new and updated reservations. **Card Guarantee Summary** — Receive a summary of card guarantee charges, useful for tracking no-show fees. *** ## Notification Recipients You can configure which team members receive reservation notifications. This is useful if you want only managers to get email alerts, or if different outlets have different notification recipients. *** ## Queue Notifications {% hint style="warning" %} **Beta.** Queue notifications are part of [Queue Management](/docs/new-guests/queue.md), currently rolling out in Taiwan and Singapore. {% endhint %} When queue management is enabled for your account, a second **Queue** card appears on the Settings > Notifications page covering customer notifications for walk-in queues. Two trigger points: * **Joining** — Sent when the guest joins your queue. Confirms their position and wait estimate. * **Table Ready** — Sent when your team pings the guest. Calls them in. Two channels: * **WhatsApp** — Default on. Sent on both Joining and Table Ready when the guest has provided a phone number. Shown as on in the Notifications card and not commonly edited; WhatsApp is the primary channel for queue notifications because it's the lowest-friction message for guests to receive on their phone. * **Automated Call** — Optional. Toggle on under **Queue > Automated Calls**. When on, the system places an automated voice call to the guest's phone when their table is ready. The call result (answered, missed) is reflected on the queue card on the Bookings page — a red **Missed call** badge appears when a call wasn't answered. There is no separate Email channel for queue notifications — guests get the in-channel queue page link via WhatsApp or staff entry. Reservation notifications above are unaffected by the queue settings — they're configured independently in the **Reserve** card. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://www.oddle.me/docs/new-guests/reserve/setting-up-reservations/notification-settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.