What information should you collect when a customer drops off a device?

When a device comes in, record six things: who brought it and how to reach them, the device with brand, model, and serial number, its condition and accessories, the problem in the customer's own words, what work is authorized and up to what amount, and the date with the order number. The rest can wait. These cannot.

Why record it at drop-off instead of later?

Because the customer is standing in front of you only once. Whatever goes unasked in that minute turns into a phone call, and a phone call nobody answers turns into a device sitting on a shelf.

Which customer details are actually needed?

Full name, a phone number, and an email address. Plus one short question that saves calls later: how the customer would rather be notified.

A mobile number is worth asking for. A landline is fine for talking, but it cannot receive text messages, and “your device is ready” travels much better written than spoken.

What do you record about the device, not just the problem?

Type, brand, model, and serial number. The serial number is the only thing that tells this device apart from the one another customer brought in yesterday, same brand and same model.

If the plate is worn off or there is no readable serial number, the shop assigns one of its own and labels the device before it reaches the work area. A device with no identifier is a device that can be mixed up with another.

And about the condition it arrives in?

Dents, scratches, missing parts, and the accessories the customer leaves behind: cable, remote, tray, charger. Written down and photographed.

This is the part that prevents the most uncomfortable conversation in the trade, the “it was already like that” one. With a photo taken in front of the customer, that conversation never starts.

How should the problem be written down?

In the customer's own words, exactly as spoken: “it makes a noise when it spins,” “it heats up and shuts off.” Not translated into a diagnosis.

The diagnosis comes later and belongs on its own line. Once the two are mixed together, nobody can tell what the customer said from what the technician assumed, and that gap is precisely what gets argued about at the counter.

What has to be authorized in writing?

Three things: whether the device may be opened, how high the work can go before the customer has to be asked again, and what happens if it cannot be repaired, meaning whether it goes back as is, whether the inspection is billed, or whether it is disposed of.

And a fourth one that is almost never written down and is always needed: how long the shop keeps a device nobody comes back for.

What does the customer walk out with?

A receipt with the order number, the date, the device, the problem as recorded, and what was authorized.

That piece of paper is what keeps three weeks from producing two versions of the same conversation.

How do you do all this without turning drop-off into an interrogation?

Almost none of it gets typed: it gets picked. Paradoxon Assistant ships with lists of devices, brands, models, and colors already loaded, and the order is completed by tapping the screen.

Photos are taken from the order itself and stay stored with it, not loose in the gallery of a phone that is gone tomorrow.

And the ticket prints when you are done, order number already on it, so the customer leaves with the paper in hand.

If you change one thing at the counter today

Make it this: write the problem in the customer's own words, and photograph the device before it goes into the shop. Those are the two pieces of information that cannot be reconstructed from memory later.