> 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.md).
# Capturing Quick Replays
### Overview
Replays become available at the end of the Reservation or Event in which they were captured. Customers can review and share their Replays in two places: the email the system sends after the booking, or the History section inside the Club's App.
{% hint style="success" %}
**Replays are available on the Pro and Autonomous(+) Tier.** If your Club is on the Basic(+) Tier, you will not have the required PodPlay hardware setup.
{% endhint %}
### How to Capture Quick Replays
If a Customer wants to capture a Quick Replay, they can tap on the kiosk button at the court's centerline or hold down the Play Button near the court's baseline.
**The button on the kiosk looks like this:**
**The Play Button near the court's baseline looks like this:**
Each Quick Replay captured is associated with a specific court or table. Meaning, if a Customer is playing on court 2, and they hit the Replay button on the kiosk or hold down the Play Button, the PodPlay system will know that the last 25 seconds of court 2 is a Quick Replay.
{% hint style="success" %}
**Once a Quick Replay is captured, the Instant Replay is shown on the TV**. This is the last 10-seconds of the Quick Replay.
{% endhint %}
The system will then cut and splice the replay camera feed from court 2, sending the last 10-seconds of the Quick Replay as an Instant Replay to the scoreboard, and after the Reservation/Event is over, all Customers in the Attendee list will receive the Quick Replay captured in their email.
{% hint style="info" %}
Admins cannot capture Quick Replays from the Dashboard. Quick Replays can ONLY be captured from the kiosk or the Play Button.
{% endhint %}
### Who Pays for a Quick Replay
If Quick Replays at your Club cost money, then when a Quick Replay is captured, the person who pays for the Quick Replay will depend on if it was captured during a Reservation or an Event. If a Customer's Profile has Replay Credits, then the Replay Credits will be subtracted from their Profile.
Even if Quick Replays are free at your Club, it is still important to understand *who would pay* for the Quick Replay.
#### In a Reservation
The Reservation Owner is charged for every Quick Replay captured during their Reservation. The system charges this Customer because they hold the card on file for the Reservation, which makes them responsible for any Replays captured during the booked time.
If the Reservation Owner has Replay Credits, those Credits are used first and the Customer is not charged until the Credits run out. Once Credits are exhausted, the Owner is charged $0.50 per additional Quick Replay. Charges are aggregated and billed at the end of the Reservation. Example: if four Quick Replays are captured and the Reservation Owner has no Credits, they are charged a total of $2 at Reservation end.
{% @supademo/embed url="" demoId="cmomccobg00s4w9dowrx2lpxd" %}
#### In an Event
For Events, the Reservation Holder is the Admin who created the Event, not the Customers attending. Quick Replays captured during an Event pull from that Admin's Profile, so participating Customers can capture as many Quick Replays as they want at no cost to themselves.
To prevent the Admins who create Events from being charged, that Admin's Profile must hold a large quantity of Free Quick Replays before the Event runs. The Free Quick Replay count on an Admin Profile can be adjusted from the Customer tab in the Admin Dashboard.
{% @supademo/embed url="" demoId="cmomc23jd00l2w9dov41izu3e" %}
### Replay Credits
{% hint style="warning" %}
**If it costs money to capture a Quick Replay at your Club, whoever is creating programming at your Club should have A LOT of Replay Credits on their Profile so they are not charged during Events.**
{% endhint %}
When a Customer has Replay Credits on their Profile, those Credits are used in place of a $0.50-per-Quick-Replay charge. Customers can view their Credit balance in the Account tab of the App, directly under their name.
The default amount of Replay Credits on a new Customer Profile is 5. This default exists to incentivize Customers to use Replays, build the habit of capturing them, and create demand to purchase more.
Clubs can also grant Members extra Replay Credits as a Membership perk, for example 5, 10, or 50 Credits per month, refreshed each time the Membership renews.
{% @supademo/embed url="" demoId="cmomcr3sn00y4w9doowvhb0jq" %}
{% hint style="warning" %}
Replays are pulled from the Reservation Holder of an Event or Reservation because the replay cameras are not using facial recognition technology (it's illegal in some US states).
{% 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.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.