> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/overview/how-to-use-the-check-in-button.md).

# Check-in Button

### Overview

QR Code Check-in lets a Club confirm a Customer's arrival for a Reservation or Event by scanning a QR code at the Front Desk, using a USB-compatible QR Code Scanner connected to the front desk computer.

The hardware to purchase is:

* A USB-compatible [QR Code Scanner](https://www.amazon.com/dp/B06XD8MFFC?ref=ppx_yo2ov_dt_b_fed_asin_title\&th=1) ([UK version](https://www.amazon.co.uk/Barcode-Omnidirectional-Hands-Free-Automatic-Computer/dp/B07CYLVHSV/ref=asc_df_B07CYLVHSV?tag=bingshoppinga-21\&linkCode=df0\&hvadid=80745591571118\&hvnetw=o\&hvqmt=e\&hvbmt=be\&hvdev=c\&hvlocint=\&hvlocphy=162586\&hvtargid=pla-4584345061925766\&psc=1\&msclkid=81ebae8cc8721e47302bc4be6f56af89)), available on Amazon for $70
* A [USB-C adaptor](https://www.amazon.com/dp/B01GGKYXVE) ($10) ONLY IF the front desk computer only has USB-C ports

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FdZ8Qhckc3p6X7T4qvwEo%2Fimage.png?alt=media&amp;token=54da808a-9935-4e79-aca6-18501235fc5d" alt=""><figcaption></figcaption></figure>

### Customer Checks-in

Once the QR Code Scanner (and the USB-C adaptor if needed) are plugged into the front desk computer, the scanner should work.

1. **Customer clicks the Check-in Button:** Before a Customer's Reservation or Event starts, a Check-in Button appears in the Reservation tab of the App.

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FsK1Nf85n6Pv367osfTwJ%2Fimage.png?alt=media&amp;token=d9fb464f-d16d-4a80-bc2f-ff9dbb1dd438" alt=""><figcaption></figcaption></figure>

The Customer sees a countdown until the button becomes clickable; when it ends, the bar expands and the Check-in Button appears.

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FNEyzjmfj59ha34t62vwn%2Fimage.png?alt=media&amp;token=3c3ed602-9f17-4e34-9f4f-4a5179c06048" alt=""><figcaption></figcaption></figure>

This timing is configurable, with the default being 15 minutes. If you have the Owner role, you can edit the check-in threshold on the Company Settings page of the Dashboard.

2. **Customer scans the QR code:** Clicking the Check-in Button shows a QR code (or verification) on the Customer's phone. The Customer waves it in front of the scanner, which buzzes to confirm the check-in.

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FQ5TxnYwR5uKoKMZigHS5%2Fimage.png?alt=media&amp;token=eed4fb44-e497-4c4f-b156-beb5db4ce726" alt=""><figcaption></figcaption></figure>

### In the Dashboard

Clicking the Check-in button also flips the Check-in toggle on the Dashboard side panel, the same toggle an Admin at the Front Desk could flip manually when welcoming a Customer in.

Staff can always flip the check-in toggle if the Customer forgot their phone at home.

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FSQ422jTFiNPVzEzebwI9%2FScreenshot%202026-10-07%20at%2011.33.05.png?alt=media&amp;token=cd23baa9-5722-418f-9321-5f0ad3387f59" alt=""><figcaption></figcaption></figure>

There will also be a little notification in the bottom of the screen saying the check-in was successful after the Customer performs a QR code scan, with the Customer's name visible. This is the alert shown to the front desk on the Dashboard, and there is an audible ping from the QR code scanner. The audible ping is positive or negative for a successful or unsuccessful Customer check-in.

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2FromgsWVv043qJFyYcqRM%2Fimage.png?alt=media&amp;token=159538a6-e452-46d1-802f-56e0948b98dc" alt=""><figcaption></figcaption></figure>

As the Customers are checking in, a count will show of all the Customers who are checked-in vs. not yet checked-in.

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2F4GdRhq61EcaXzzRyc2wu%2FScreenshot%202026-10-07%20at%2011.31.31.png?alt=media&amp;token=cf02bdad-6abb-405d-8d12-dfe694026fd0" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.podplay.app/overview/how-to-use-the-check-in-button.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.