Template, not built for a specific business

A repair that sits untouched for weeks should flag itself

Many repair shops track jobs the same way: a bench, a paper ticket or a spreadsheet row, and a staff member who is supposed to remember to call the customer at each step. When that person gets busy, a job can sit untouched for weeks with nobody noticing until the customer calls to ask. This page shows one small, working tool that fixes both sides of that gap: an internal queue that surfaces every open ticket sorted by how long it has sat in its current stage, and a customer-facing status page so a customer can check where their item stands without calling first.

Everything below is fictional. When this gets built for a real business, the office view reads from whatever already tracks the job (a bench log, a spreadsheet, a POS system), and the reference code on the customer view is whatever the shop already hands out, not a new system to adopt.

Log a new ticket

Open queue, longest stuck first

Check the status of a repair

Try RT-1001, RT-1002, RT-1003 or RT-1004 from the office view's sample queue.

How this gets built for real

The reference code is whatever the shop already hands out. A real build reads from an existing ticket or work order number instead of inventing a new one for the customer to remember.
"Stuck" here is a simple timer per stage. A real build can text or email the customer automatically the moment a stage changes, instead of relying on staff remembering to call.
The customer view shows only customer-safe wording. Internal notes stay in the office view, nothing typed there is exposed on the lookup page.
See it built for a real business: KA RV Repair, WatchRepair.net, Boat World MN, or SVE Autobody Specialists.