> 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/what-your-guests-see.md). # What Your Guests See Understanding the guest experience helps you set up a programme that feels natural, not intrusive. Here's what happens from the moment a guest checks in to when they earn their first reward. *** ## Checking In Your check-in programme runs through a dedicated check-in page — a branded page hosted on your Virtual Lounge that guests access by tapping an NFC block or scanning a QR code at your restaurant. This page isn't visible on your regular Virtual Lounge — it's only accessible through the physical check-in touchpoints you deploy. When a **new guest** taps or scans for the first time, they'll be asked to: 1. Enter their name and phone number to create an account 2. Answer your insight questions (if enabled) — like whether they live or work nearby, or how they discovered your restaurant 3. Opt in to marketing communications (if you've made this compulsory, they're subscribed automatically) Once checked in, they land on a confirmation screen showing their welcome reward and any vouchers for their next visit. When a **returning guest** taps or scans, they're recognised automatically — no need to re-enter details. They check in with a single tap and immediately see their reward progress. *** ## Earning Rewards Your programme is built around check-ins. Every time a guest visits and checks in, they make progress toward their next reward. The exact rewards depend on how you've set up your programme, but the default structure works like this: **First check-in** — The guest checks in and receives a welcome reward they can use right away — an immediate incentive for signing up. They also receive a set of vouchers to use on their next visit, giving them a reason to come back. **Subsequent check-ins** — Each check-in counts toward a milestone. If your milestone is set to 3 check-ins within 180 days, the guest sees their progress (e.g., "2 of 3 check-ins completed") each time they visit. **Milestone reached** — When the guest hits the target number of check-ins within the time window, they earn a milestone reward. If the milestone is repeatable, the counter resets and they start working toward the next one. **Lapsed guest returns** — If a guest hasn't checked in for a long time (e.g., 270+ days) and you've set up a welcome back reward, they receive it on their return visit — a nudge to re-engage. **Birthday** — If enabled, guests receive a birthday reward either at the start of their birth month or a set number of days before their birthday. *** ## What Guests See on the Check-in Page The check-in page is branded with your restaurant's identity — your logo, colours, and programme headline. After checking in, guests can see: * Their **reward progress** — how many check-ins until their next milestone * Any **active rewards** they've earned and can redeem * Your **programme benefits** — the headline and description you set up when creating your programme > **Tip:** The check-in page is hosted through your Virtual Lounge, so you'll need to have a Virtual Lounge set up before creating your programme. See **Virtual Lounge** for details. --- # 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/what-your-guests-see.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.