> 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/reserve-with-google.md).

# Reserve with Google & Other Booking Channels

The more places guests can find and book you, the more reservations you'll get. Oddle Reserve connects to several booking channels beyond your own booking page — and all reservations flow into your Host App in one place.

***

## Reserve with Google

Reserve with Google is one of the highest-traffic booking channels available. It lets guests start a booking from Google Search or Google Maps — right from your Google Business listing.

When a guest searches for your restaurant and sees the "Reserve a table" button, they can:

1. See your available time slots
2. Select a date, time, and party size
3. Confirm the booking — on Google if the ticket is free, or on Oddle if it takes payment

The reservation then appears in your Host App alongside all your other bookings.

### Paid Tickets on Google

Tickets that require payment work on Google too. You keep your deposit, prepayment, or card guarantee, and still capture the bookings that start on Google Search and Maps.

Google doesn't take the payment. The guest picks their date, party size, and time on Google, then continues to Oddle to review your policy and either pay or add their card. The booking is confirmed after that step and lands in your Host App like any other reservation.

| Payment type       | On Google                                                        |
| ------------------ | ---------------------------------------------------------------- |
| **Deposit**        | Yes — as long as the ticket has a refundable cancellation window |
| **Prepayment**     | Yes — the guest pays in full before the booking is confirmed     |
| **Card guarantee** | Yes — the guest adds a card before the booking is confirmed      |

{% hint style="warning" %}
**A deposit ticket on Google has to be refundable.** Google requires a cancellation window that allows a refund, so **Non-refundable** isn't offered on a deposit ticket while Reserve with Google is turned on — the Host App asks you to pick a refund window before it lets you save. Prepayments and card guarantees aren't affected.
{% endhint %}

If your ticket varies payment by party size, Google follows the same rules. On a ticket where parties of 4 or fewer book free and 5 or more leave a card guarantee, Google lets the small parties book straight through and sends the larger ones to Oddle to add a card.

{% hint style="info" %}
If a paid ticket hasn't appeared on Google after 24 hours, check that **Reserve with Google** is on for that ticket and that any deposit has a refundable cancellation window. If it's still missing, contact Oddle support.
{% endhint %}

### How to Turn It On

Reserve with Google is set **on each ticket**:

1. In the Host App, go to **Settings > Tickets** and open the ticket
2. Find the **Bookable Channels** section
3. Toggle on **Reserve with Google**

To take a ticket off Google, turn the same toggle off.

### Requirements

For Reserve with Google to work:

* Your store must be active with an accurate address (Google matches your listing by address)
* You need at least one service schedule with online-enabled tables
* The ticket must be active
* If the ticket takes a deposit, it needs a refundable cancellation window

You can put up to **10 tickets** on Google per brand, free and paid together. Once you reach the limit, the toggle is unavailable on your other tickets until you take one off.

> **Important:** Google reviews and processes your listing, so it may take up to 24 hours after enabling for the "Reserve a table" button to appear on Google. If it doesn't show up, double-check that your store address is complete and accurate.

### Reservations from Google

Bookings made through Google show up in your Host App just like any other reservation. There's no difference in how you manage them — same statuses, same workflow.

***

## Embedded Reservation Widget

If you have your own website, you can embed a reservation widget directly on it. This lets guests book without leaving your site.

The widget provides the same booking flow as your Oddle booking page but embedded within your website's design. Your web developer can install it with a simple code snippet.

## Oddle Shop Integration

If you use Oddle Shop for online ordering, you can also surface your reservation option on your shop page. Guests browsing your menu for delivery or takeaway can discover that you also accept reservations.

## Oddle Eats

Oddle Eats is Oddle's food discovery marketplace. When your restaurant is listed on Oddle Eats, new diners can discover you and book a reservation — this is an acquisition channel that brings in guests who might not have found you otherwise.

***

## All Channels, One Dashboard

Regardless of where the reservation comes from — your booking page, Google, your website widget, Oddle Shop, or Oddle Eats — every booking appears in your Host App. Your team manages everything in one place with no need to check multiple systems.


---

# 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/reserve-with-google.md?ask=<question>&goal=<endgoal>
```

`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.
