Pause the disputed machine when a fault is plausible, preserve the evidence and give the guest a clear review process. A camera angle, an audit counter or a staff impression may answer part of the question. None should be stretched beyond what it actually records. Handle the technical claim, the customer remedy and any threatening conduct as separate decisions.
First, identify what the guest says happened
“I won” can mean several different things. The guest may have seen a success message, a key enter an opening, a claw lift a prize, a prize become stuck, or a physical item fail to reach the collection door. They may instead believe the game was unfair because several near wins looked identical. Ask the person to describe the exact event before explaining how you think the machine works.
Record the game, station or bay, prize, approximate time, number of disputed plays, payment identifier needed to find the transaction, and any screen message or sound. Ask whether another person witnessed the play. Avoid collecting full payment-card numbers or unrelated personal information just to investigate a single transaction.
This guide is an operating process, not a ruling on any particular Key Master, crane or prize machine. Cabinet names and visual similarity do not establish identical firmware or audit behavior. Obtain the manual and manufacturer guidance for the actual machine. SEGA's support portal is one example of a primary source for game manuals and technical bulletins; its existence is not evidence of how an unidentified cabinet recorded a specific play. [1]
Give an immediate response without deciding the outcome
A useful first response is: “I understand you're saying the game registered a win but you didn't receive the prize. I will record the details, preserve the available records and have the manager review it. We will contact you by [realistic time].” Choose a response time someone actually owns. If technical support is needed, promise an update by that time rather than an outcome you cannot yet deliver.
Do not make the guest keep buying plays to demonstrate a fault. If a controlled test is needed, use an authorized service procedure and document it. Keep any test credits, counter changes and prizes separate from the disputed event. Testing can change the very evidence needed to reconstruct the original claim.
If the machine might continue charging for a broken experience or create a mechanical hazard, remove it from service under your venue procedure. Mark the cabinet clearly and disable charging through an approved process. A handwritten note that can fall off is a weak control if the card reader still invites play.
Preserve an evidence packet before restarting or resetting
| Record | What it may establish | What it may not establish |
|---|---|---|
| Payment or reader transaction | A charge, authorization, time and reader identity. | Successful game start or a win. |
| Game audit or event history | Events or counters the particular controller records. | Prize delivery unless that event is specifically recorded. |
| Camera footage | Visible motion and actions within the frame. | Hidden sensors, missing audio or an obscured prize path. |
| Prize inventory | Counted stock and documented loading or removal. | Who received a particular prize without supporting records. |
| Witness account | What the person reports seeing or hearing. | An independently verified controller state. |
Photograph the relevant displayed audit values and record the current machine clock. Compare its time with the payment system and camera recorder; a clock offset can make a genuine event appear absent. Preserve an appropriately bounded period before and after the disputed play so the context remains visible.
Record recent loading, maintenance, audit resets, test plays and prize removals. A counter that reads zero after service is different from an uninterrupted event log showing no award. Ask the manufacturer what each field means, when it increments and whether its history survives loss of power. Do not assume a lifetime total is an event-by-event record.
Separate win detection from prize delivery
Have a qualified technician trace the approved sequence for the actual model: input accepted, game action completed, winning condition detected, award registered, delivery commanded, and item made available. Not every machine exposes each stage in diagnostics, and some have a different sequence. The purpose is to identify which observation is missing, not to invent a universal controller diagram.
If an award is recorded and the item is visibly jammed, the investigation is different from a game that never registered the required winning condition. Inspect safely using the service manual. Do not bypass switches, force a motor, alter payout settings or erase records to make the incident disappear. The separate prize-dispensing troubleshooting guide can help organize symptoms without substituting for model-specific procedures.
Where the evidence is conflicting, describe the conflict honestly. For example: “The video shows the key entering the opening, but the machine log available to us does not record individual award events. Manufacturer review is pending.” That is more defensible than declaring the video proves a sensor event it cannot show.
Choose a remedy that matches the supported finding
- Confirmed award and failed delivery: arrange fulfillment or a lawful agreed alternative through the manager, and document the fault.
- Confirmed paid play without the promised playable experience: consider restoring the affected play value or another remedy under the policy and applicable law.
- Evidence supports normal operation: explain what was checked and what it establishes, without accusing the guest of lying.
- Evidence remains inconclusive: explain the limits, the next review step, and whether management is offering a discretionary resolution.
These are management decision categories, not automatic legal entitlements or a rule that one outcome always applies. Prize-game legality, representations, refund obligations and dispute procedures can depend on jurisdiction and the actual facts. Have the venue's policies reviewed for where it operates. A sign saying “malfunctions void all wins” should not replace an investigation or be assumed to defeat every consumer right.
The FTC's general advertising guidance requires claims to be truthful and supported. Apply that principle to the guest-facing game description and prize offer: show what is actually included, follow the real rules and avoid promising a guarantee that the game does not provide. [2]
Keep threatening conduct separate from the prize claim
A guest can have a valid technical complaint and still behave unsafely. Conversely, a calm complaint is not proof of a win. Staff should document both issues independently. If threats create an immediate danger, follow the emergency plan; do not keep debating the prize at the counter. Use the guest conduct and de-escalation guide for roles and escalation.
Do not bargain for deletion of an honest review as the routine condition for examining a complaint. The FTC explains the Consumer Review Fairness Act's restrictions on standardized contract provisions that suppress or penalize honest reviews. A factual, private resolution process is usually more useful than an argument on the venue's social page. [3]
Close the case with a specific written outcome
A brief resolution should state the claim reviewed, the relevant checks, the finding and its limits, any approved remedy, and who to contact with new evidence. For example: “We confirmed your payment and reviewed the available footage. The cabinet does not retain per-play award history, so that record cannot settle the dispute. Our manager has approved [remedy]. The machine remains unavailable pending service.” Use only statements true in that case.
Keep sensitive evidence in controlled storage. Share only the material needed with the manufacturer, insurer, legal adviser or investigating authority, following your policy and applicable requirements. Do not publish children's faces, transaction details or a guest's identifying information to crowdsource a verdict.
Fix the process that made the dispute hard to resolve
Check camera sightlines, timestamp alignment, audit retention, prize-loading records and manager access to transaction searches. Give staff one incident form and a clear owner for technical escalation. Add a service follow-up so a refunded game does not quietly return to operation with the same fault.
Measure recurring dispute categories rather than counting all complaints as abuse. Multiple “won but no prize” reports on one bay are a reason to inspect that bay; they are not proof of coordinated dishonesty. Document verified faults, uncertain cases and ordinary misunderstandings separately. That distinction improves maintenance decisions and gives both guests and staff a more reliable process.