> 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/replays/overview-of-replays/capturing-and-reviewing-replays/reviewing-quick-replays/quick-replays-email-for-customers.md). # Quick Replays Email for Customers {% hint style="info" %} The below email template can be edited and sent to Customers. It is an educational tool to help Customers understand how to capture and review their Quick Replays. {% endhint %} *** **Subject:** Capturing and viewing your Quick Replays Hi \[Customer Name], Quick Replays let you capture the last 25 seconds of play on your court or table, so you can save, share, or download highlights from your time at the Club. #### How to capture a Quick Replay You have two ways to trigger a Quick Replay during your Reservation or Event: * Tap the Replay button on the kiosk at the court's centerline * Hold down the Play Button near the court's baseline Each Quick Replay is tied to the court or table you're playing on. If you're on court 2 and hit the button, the system grabs the last 25 seconds of court 2. The moment you capture a Quick Replay, the last 10 seconds play on the court's TV as an Instant Replay so you can review it right away. #### Where to find your Quick Replays Quick Replays become available once your Reservation or Event ends. You can find them in two places. **Email.** Every Customer on the Attendee list gets an email after the booking with links to all Quick Replays captured during that Reservation or Event. Each link opens the Replay on a web page where you can download it, upload it, or send it to select social media platforms. The links don't expire. **In the App.** Open the App, tap the Reservation tab at the bottom, tap the History / Replays tab at the top, tap the past Reservation or Event, and scroll to the bottom to see captured Replays in a carousel. From there you can download, upload, or favorite a Quick Replay. Anything you favorite is saved under Favorite Replays in the Account tab. #### Why everyone on the Attendee list gets every Replay The replay cameras don't use facial recognition (it's illegal in some US states), so the system can't tell which player triggered a Quick Replay. Everyone on the Attendee list receives any Replay captured during the booking. Have fun out there, and let us know if you have any questions. See you soon, The \[Club Name] Team *** {% hint style="info" %} If your Club charges for Quick Replays: * During a Reservation, the Reservation Owner is charged $0.50 per Quick Replay. Replay Credits are used first if the Reservation Owner has any. Charges are bundled and billed at the end of the Reservation. * During an Event, the Admin who created the Event covers the Quick Replays. Customers attending pay nothing. {% endhint %} --- # 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://docs.podplay.app/replays/overview-of-replays/capturing-and-reviewing-replays/reviewing-quick-replays/quick-replays-email-for-customers.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.