The repair ticket — the right fields, and the digital version

What a proper repair ticket contains

Whether it is written in a carbon-copy book or produced by software, a ticket that protects you has the same fields. Copy them as they are:

• Customer details: name, phone — and consent to be contacted
• Device: brand, model, IMEI or serial number, passcodes if provided
• Intake condition: description plus photos (scratches, cracks, liquid damage)
• The fault, in the customer’s own words
• A cost estimate or an approval threshold, plus any diagnosis fee
• Terms: storage period, data responsibility, repair warranty
• Date, ticket number and the customer’s signature

Paper or digital — what the book costs you

The paper ticket works until you need something from it: the history of the same device, which technician had it, what part went in last year, or proof the screen was already cracked. On paper, all of that is page-flipping; when the book fills up, your archive is a drawer.

In Workflow Repair the ticket is issued in seconds with device details from the catalogue, QR intake photos and a customer signature, and prints to a PDF with your shop’s details. The customer gets a tracking code and checks the status without calling.

From the ticket to the receipt

The ticket is not a tax document — it is the intake agreement. When the repair is done, the charge happens at the till and the myDATA document is issued from the same screen, on the plans that include it. One flow: intake, repair, receipt.