What Every Repair Ticket Needs
Most repair disputes start at intake: a scratch nobody noted, a fault described differently, a phone number with a digit missing. A complete ticket prevents most of them.
Customer
- Name, phone and email.
- Preferred way to be contacted.
Item
- Type, brand and model.
- Serial number or IMEI where there is one.
- Accessories left with the item (charger, case, SIM).
- Condition on arrival: existing scratches, dents, cracks. Photos help.
The job
- The fault, in the customer’s words.
- What the customer agreed to: diagnosis only, or repair up to a set amount.
- Quote or estimate, if given.
- Deposit taken.
- Promised date.
Terms
- Data loss disclaimer for phones and computers.
- Collection deadline and what happens after it.
- Warranty on the repair.
During the job
- Status changes with dates: received, diagnosing, waiting for parts, ready.
- Notes from the technician.
- Parts used.
A complete ticket, filled in
| Field | Example |
|---|---|
| Ticket | #2047 |
| Customer | Maria L., mobile, prefers text messages |
| Item | Smartphone, black, IMEI recorded |
| Accessories | Case left with device; no charger |
| Condition | Screen cracked top-left; small dent on bottom edge; photos taken |
| Fault | “Screen flickers and doesn’t respond at the top” |
| Agreed | Screen replacement; call before spending over quote |
| Quote / deposit | Quote given; deposit taken per shop policy |
| Promised | Thursday after 3 pm |
Everything a technician, a colleague or the customer might ask later is on the ticket.
Photos at intake
A quick photo of each side of the device, taken at the counter, settles most “that scratch wasn’t there before” conversations in seconds. Attach photos to the ticket rather than keeping them on a personal phone.
The customer’s words matter
Write the fault as the customer describes it, then add your own observation separately. “Won’t charge” might be a cable, a port or a battery. Keeping both helps the technician and protects you if the diagnosis turns up something different.
Approval limits
Agree at intake how much the customer is willing to spend without being contacted again. “Go ahead up to the quote; call me if it is more” avoids work stopping while someone tries to reach the customer, and avoids surprise bills.
Terms on every ticket
- Data: you are not responsible for data loss; the customer should back up first.
- Collection: how long you hold items after they are ready, and what happens after that. See handling unclaimed repairs.
- Warranty: how long the repair is guaranteed and what it covers.
- Deposits: see setting a fair deposit policy.
Paper and screen
The ticket lives in your system; the customer takes a claim check, and a work order travels with the device. Read claim checks and work orders for what each should show.
Updating the ticket during the job
A ticket is only useful if it stays current. Every time the job moves, update the status and add a short note: what was found at diagnosis, which part was ordered and when it is due, whether the customer approved a revised quote, and what tests were done before marking it ready. Dated notes mean anyone on the team can answer a customer’s question without finding the technician. They also give you a record if the device comes back under warranty, showing exactly what was done and which parts were fitted. Keep notes factual and short; they may be read by the customer if there is ever a dispute.
When the job is finished, check the ticket is complete before marking it ready: parts recorded, tests ticked, final price confirmed. A complete ticket makes pickup quick and keeps your parts stock accurate; see tracking parts used on repairs.
How RepairRight helps
RepairRight records customer details, linked orders and parts used on each ticket, keeps notes and a status history, and prints claim checks and work orders. A ticket board tracks every job from received to pickup, and a “Needs attention” queue keeps jobs from falling through the cracks.
Read next: Shopify Repair Ticket Apps Compared (2026) · A Phone Repair Shop Workflow From Intake to Pickup
FAQ
Should I take photos of every device?
For anything with visible damage or high value, yes. It takes seconds and prevents disputes.
Do I need the customer’s passcode?
Only if testing requires it. Explain your data policy, and record what access you were given.
What if the customer disagrees with the condition notes?
Show them the device and the photos at intake, and agree the notes before they sign or leave.
Should the customer sign the ticket?
Many shops ask for a signature on the claim check or work order to confirm the terms and condition notes.