> 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/check-in/deploying-your-programme.md). # Deploying Your Programme Your programme only works when guests can check in — and that depends on making the check-in touchpoints easy to find and natural to use. This page covers the three check-in methods available and best practices for getting them in front of your guests. Go to **Engage > Loyalty** in your Merchant Admin, then select **Manage Check-in Options** to set up your check-in methods. *** ## Check-in Methods ### NFC Loyalty Check-in Blocks Physical blocks placed on tables that guests tap with their phone to check in. This is the most frictionless method — no camera needed, no QR to scan, just a tap. NFC blocks can also show an ordering button, letting guests check in and view your menu in one flow. **Setup:** 1. Select **NFC Loyalty Check-in Blocks** from the check-in options 2. Choose the store you're setting up 3. Select which tables to assign NFC blocks to 4. Optionally turn on **Show ordering button** to combine check-in with menu access 5. Program your NFC blocks **Best practices:** * **Place blocks where guests will naturally notice them** — centre of table, near the menu stand, or next to the table number * **Brief your floor staff** — staff should know what the blocks are and be able to prompt guests with a simple "Tap here to join our rewards programme." A quick mention during seating goes a long way * **Every table matters** — deploy blocks on all tables, not just some. Guests at tables without blocks can't check in > **Tip:** NFC blocks are the preferred check-in method. They're the most frictionless for guests (one tap vs opening camera and scanning) and capture the highest check-in rates. ### QR Codes Printable QR codes generated per store. When a guest scans the code, they're taken to the check-in page and asked to share their location to verify they're at your restaurant. **Setup:** 1. Select **Ready to print QR Codes** from the check-in options 2. Download QR codes for each store 3. Print and display at your restaurant **Best practices:** * **Table cards or standees** — place QR codes at each table, ideally with a short call-to-action ("Scan to join our rewards programme and earn a welcome reward") * **Entrance display** — a standee or poster near the entrance catches guests while they're waiting to be seated * **Receipts** — consider adding the QR code to printed receipts as a post-meal touchpoint ### Check-in Kiosk A device (tablet or phone) at your restaurant that displays a dynamic QR code. Guests scan it to check in. This works well as a centralised check-in point — for example, at the entrance or the counter. **Setup:** 1. Select **Set up a Check-in Kiosk** from the check-in options 2. Customise your kiosk: * **Background image** — upload an image to brand the kiosk screen (landscape 21:9 for desktop/tablet, portrait 9:16 for phone) * **Header text** — the message displayed above the QR code (default: "Scan to Check-in or Join our Rewards Programme", max 120 characters) 3. Copy the kiosk URL for each store and open it on your device **Best practices:** * **Host stand or counter** — position the kiosk where staff can prompt guests to scan * **Dedicated device** — use a tablet that stays on the kiosk page. Avoid sharing with other apps *** ## Choosing Your Method | Method | Best for | Friction level | | -------------- | ---------------------------------------------------- | ---------------------------------- | | **NFC blocks** | Table service restaurants, maximising check-in rates | Lowest — one tap | | **QR codes** | Any format, flexible placement, low cost | Low — scan with camera | | **Kiosk** | Counter service, centralised check-in point | Medium — walk to device, then scan | You can use multiple methods at the same store. Many restaurants use NFC blocks at tables with a kiosk at the entrance as a fallback. --- # 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/check-in/deploying-your-programme.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.