> 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/owners-playbook/new-to-podplay/onboarding/front-desk-set-up.md). # Front Desk Set-up ### Overview Opening a Club is exciting and stressful at the same time. The hardware, QR Codes, Dashboard tabs, and staff training below make front desk operations smoother from day one. ### Hardware checklist If your Club has a front desk, gather the following before opening day: * A high-speed internet connection. * A computer or laptop with 8 to 16 GB of RAM. Two computers are recommended, especially if your Club has more than 4 bookable spaces. Staff can then watch arriving Customers on one computer and answer Customer questions on the other. * A Front Desk Profile in the Dashboard tied to a generic email address, such as `info@company.com`, that any staff member at the front desk can use. * A QR Code scanner for efficient Customer [Check-ins](https://docs.podplay.app/overview/how-to-use-the-check-in-button). Not necessary for Autonomous(+) Clubs. * A [credit card terminal](https://docs.podplay.app/payments/credit-card-terminals). Recommended, not required. Not necessary for Autonomous(+) Clubs. ### QR Codes at the front desk Post QR Codes at the front desk so walk-in Customers create a Profile, sign the Liability Waiver, and book on their own phone. For the list of QR Codes, their URLs, and the walk-in flows staff follow, see: * [Rapidly Assist Walk-ins](https://docs.podplay.app/overview/rapidly-assist-walk-ins) (QR codes at front desk and in marketing campaigns) * [Links to the App](https://docs.podplay.app/marketing/link-from-the-app) (QR codes in marketing campaigns) * [Create Event Deep Links](https://docs.podplay.app/marketing/link-from-the-app/create-event-deep-links) (QR codes in marketing campaigns) ### Dashboard tabs to keep open Keep these two Dashboard tabs open in the front desk browser: * **Overview page** (`https://.podplay.app/admin/v2/overview`): Staff see which Customers are arriving and how many people are expected for each Reservation or Event. Staff can open the side panel on any Reservation or Event for more detail. * **Check-in page** (`https://.podplay.app/admin/v2/overview/areas/`): Needed only if your Club uses a QR Code scanner for Customer Check-ins. ### Staff training before day 1 The set-up above does not make day 1 smooth on its own. Front desk staff also need to know how to handle the most common situations before the doors open. The PodPlay Academy is the fastest way to get them there. In the two to three weeks before opening, every staff member who will work the front desk completes the [Manager and Staff course in the PodPlay Academy](https://docs.podplay.app/support-and-troubleshooting/the-podplay-academy). Prioritize these modules: * The Customer's Experience. * The Overview Page. * The Customer Page. * Reviewing Purchases. A few days before opening, the General Manager or staff manager runs a short dry run in your live Environment. Simulate a few Reservations, an Event Check-in, and a Membership signup. This surfaces gaps before real Customers walk in. {% hint style="success" %} **Want a training session with the Customer Success team?** Club Owners and General Managers can email . Take the PodPlay Academy courses first, because they answer many questions. Bring any remaining questions to the session. {% endhint %} Club Owners, General Managers, and staff call the PodPlay Academy one of the most thorough onboarding courses they have taken. Many of them have worked at Fortune 100 and Fortune 500 companies. --- # 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/owners-playbook/new-to-podplay/onboarding/front-desk-set-up.md?ask=&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.