Tickets & Repair Workflow
How to create, manage, and close repair tickets — including statuses, time tracking, photos, QA checklists, and customer pickup signatures.
Tickets & Repair Workflow
Tickets are the heart of QuantumRepair. Every repair your shop does — from a cracked screen to a complex motherboard repair — lives as a ticket from the moment the device walks in until the customer picks it up.
What is a ticket?
A ticket is a record that tracks:
- The customer and their device
- The reported issue and your diagnosis
- Every status change the repair goes through
- Parts and labor added as line items
- Photos taken before, during, and after the repair
- Time logged by the technician
- A QA checklist confirming the repair is complete
- The customer's pickup signature
- Any comments between staff members (internal) or to the customer (external)
The repair statuses
Tickets move through a defined workflow. The system only allows valid transitions, so a ticket cannot jump from Pending straight to Repaired by mistake.
| Status | What it means |
|---|---|
| Pending | Device received, waiting to be looked at |
| Diagnosed | Technician has assessed the issue |
| Quoted | A quote has been prepared for the customer |
| Awaiting Approval | Quote sent, waiting for customer to approve |
| Approved | Customer approved the repair |
| Waiting for Parts | Parts ordered, repair is on hold |
| In Repair | Active repair work in progress |
| Quality Check | Repair complete, undergoing final QA |
| Repaired | All QA checks passed |
| Ready for Pickup | Customer notified to collect |
| Picked Up | Device collected (requires customer signature) |
| Cancelled | Job cancelled — no charge |
| Warranty Claim | Customer returned with a warranty issue |
When you change a status, QuantumRepair automatically sends the customer the matching notification template (SMS or email, depending on your settings).
Creating a ticket
- Go to Tickets and click New ticket (or press
GthenTto open Tickets, then click the button). - Find or create the customer — search by name, phone, or email. If they are new, click "New customer" and fill in their details without leaving the form.
- Enter the device — brand, model, type (phone, tablet, laptop, etc.), serial number if known, and the passcode (stored encrypted).
- Describe the issue — enter what the customer reported. The more detail here, the better your AI diagnosis will be.
- Upload a photo (optional but recommended) — if you upload an image, the AI Vision system analyses it and pre-fills the damage type, estimated severity, suggested parts, and cost range. You can accept or edit the AI suggestions.
- Set priority: Low / Normal / High / Rush. Rush tickets appear with a red indicator on the queue.
- Assign a technician and optionally set an SLA due date.
- Click Create ticket.
The ticket is created as Pending and appears in your queue.
AI Intake tip: The AI Vision analysis works best with a clear, well-lit photo of the damaged area. The AI suggests parts from your actual inventory catalog, so your catalog needs to be reasonably populated for best results.
The ticket queue
The Tickets list has two views — toggle between them using the icons in the top-right:
- List view — sortable table with customer name, device, status, priority, assigned tech, and SLA countdown
- Kanban board — columns for each active status (Pending through Ready for Pickup); drag a ticket card to a new column to change its status
Both views have:
- Search — by ticket number, customer name, or device
- Status filter — show only specific statuses
- Bulk actions — select multiple tickets, then change status, assign, or export as CSV
SLA indicators are shown on each ticket card: orange = warning (less than 4 hours remaining), red = breached.
Managing a ticket in detail
Click any ticket to open its detail page.
Changing the status
Click the status pill at the top of the ticket. A menu shows the valid next statuses. Select one, optionally add a note, and click Confirm. The customer is notified automatically.
Pickup requires a signature. When you move a ticket to Picked Up, a signature pad appears. The customer signs on your screen or tablet and the signature is saved to the ticket record permanently.
Adding comments
The comments panel is below the ticket details. Comments can be:
- Internal (staff-only) — visible only to your team; useful for technician notes
- External (to customer) — sent to the customer by SMS or email and recorded in the thread
Time tracking
Click the Start timer button when the technician begins working. Click Stop when they finish. Every session is recorded with a timestamp. The total logged hours appear on the ticket and feed into technician performance reports.
Photo gallery
Click Upload photo and choose a type:
- Before — condition on intake
- During — in-progress work
- After — completed repair
- Damage — specific damage documentation
- Receipt — supplier receipt for parts
Photos are stored securely in the cloud and are never deleted from the ticket record.
Parts and line items
Add parts from your inventory directly to the ticket as line items. Each line item shows the part name, quantity, unit price, and subtotal. The ticket total updates in real time.
When the ticket is ready to invoice, click Create invoice to turn the line items into a chargeable invoice.
QA checklist
Before moving a ticket to Repaired or Ready for Pickup, you must complete the QA checklist. The checklist items are set up in Settings → Repair and may include:
- Screen test
- Functionality check
- Cosmetic inspection
- Battery health
- Connectivity test
Each item is marked Pass or Fail. Required items must all pass before the checklist can be submitted.
Review request
From the ticket detail, click Request review to send the customer a link to leave a Google or in-platform review via SMS or email. Best sent right after the customer picks up their device.
Warranty card
Completed tickets show a warranty countdown. If the customer returns within the warranty period, they can open a Warranty Claim from the ticket. This creates a new linked ticket with the original repair history attached.
Ticket number and tracking
Every ticket gets a unique ticket number (e.g. T-10042) and a tracking code that customers can use on your public storefront to check the status of their repair without contacting you.
You can find both on the ticket detail page. Click Copy tracking link to get a URL you can send to the customer.
Intake condition checklist
When creating a ticket, you can walk through the intake condition checklist with the customer. Each item (screen cracks, buttons, charging port, etc.) is marked OK / Damaged / Not tested. The customer can initial each item, creating a clear record of the device's condition at drop-off. This protects you if the customer later claims damage was caused by your shop.
The checklist template is fully customizable in Settings → Repair.
Tips for a smooth workflow
- Use the kanban view during busy periods — it gives your team a visual snapshot of what's in each stage
- Set SLA due dates on every ticket — the color-coded countdown keeps urgent jobs visible
- Add internal comments generously — they are free and create a searchable history of the repair
- Complete the QA checklist before calling the customer — moving to "Quality Check" auto-notifies the customer that the repair is nearly done
- Always collect a pickup signature — it is your proof of delivery if there is ever a dispute