Report Desk

Report Desk

Simple issue reporting for unattended machines

1 follower

Simple QR-code based issue reporting for car washes, laundromats, arcades, EV chargers, and more. Customers scan, report, you fix. No app required.
Report Desk gallery image
Report Desk gallery image
Report Desk gallery image
Report Desk gallery image
Report Desk gallery image
Report Desk gallery image
Free Options
Launch Team
Anima - OnBrand Vibe Coding
Design-aware AI for modern product teams.
Promoted

What do you think? …

Hriday Talur
Maker
📌
Hey Product Hunt! 👋 I’m Hriday, the solo founder behind Report Desk. If you’ve ever run unattended machines (arcade routes, laundromats, self‑service car washes, vending, etc.), you probably know this pain: You only find out a machine is broken when revenue drops or someone gets angry. Issues are reported through random texts, calls, sticky notes, or a Google Form someone forgets to check. Refunds are manual and messy, with no evidence to separate legit problems from “machine ate my money” guesses. Report Desk aims to be the missing layer between your customers and your machines. 💡 How it works Put a QR code on each machine. When something goes wrong, customers scan, pick an issue type, optionally attach a photo, and submit. You get a clean, per‑location dashboard with issues, photos, timestamps, and simple actions like “Mark resolved” or “Refund issued”. No apps, no hardware, no complicated setup—just a lightweight inbox for machine problems. I built this after talking with arcade, vending, car wash, and laundromat operators who were all hacking together their own solutions with Google Forms and spreadsheets. The goal is to give small and mid‑sized operators something that feels purpose‑built instead of duct tape. 🧪 Who this is for (right now) Route arcade operators Self‑service / unattended laundromats Self‑service car washes Independent vending operators 🆓 Pricing / pilot Free 30‑day trial, no card required Then a simple flat plan (starting at $9/month) I’d love feedback on: Where the workflow feels smooth vs. clunky Which actions/operators most want after an issue (refund, tech visit, notes, etc.) Any edge cases I might be missing for your specific type of machines Happy to answer any questions, brainstorm use cases, or set up a quick pilot for your machines. Thanks for checking out Report Desk! 🙏 - Hriday