Repair Tickets
A repair ticket is a single device's repair job. It tracks diagnosis, parts, labor, QC, and completion.
Where to find it
Portal: /portal/repairs/{id} (from queue or history)
Admin (legacy): /repairs/ticket?tid={id}
API: /api/v1/repairs/{id}
Ticket detail view
Includes:
- Device info — make, model, serial, asset tag, photos
- Services — what's being done + pricing
- Diagnostic results — from test runs (if kiosk/diagnostics app was used)
- Parts used — parts inventory drawn down
- Labor time — technician time tracking
- Tech notes — free-form notes with timestamps
- Customer contact — message history with customer
- QR code — links to customer-facing status page
QR code
Each ticket gets a unique QR code. Print and stick it on the device. Scanning:
- As a tech: opens the ticket in the internal UI
- As the customer: opens a public-facing status page showing just what they need to know
Knowledgebase articles
Linked articles appear on the ticket detail — relevant how-to guides for the services on this ticket. Techs can reference them without leaving the ticket.
Status transitions
Ticket status changes are logged with timestamp + user. You can see who did what when.
| Transition | Typical trigger |
|---|---|
| open → in_progress | Tech picks up the ticket |
| in_progress → waiting_parts | Parts need to be ordered |
| waiting_parts → in_progress | Parts arrived |
| in_progress → completed | Work done, entering QC |
| completed → billed | Customer paid or account billed |
Webhook
repair.completed fires when status → completed.
Related features
- Repair Queue
- Kiosk — ticket source for self-service