A customer drops off a device, you take it, work is done, and a week later there's a disagreement about what was agreed, what was promised, or what the device looked like when it arrived. Without a documented intake, the conversation becomes one person's word against the other's. The customer's version usually wins because the customer is the one writing the review.
A proper intake process closes that gap before any work begins.
Why intake is where the business is protected
Intake is the only moment where the device, the customer, and the technician are in the same room. Whatever isn't documented now is lost.
Memory fails. Customers genuinely forget what they were told. Damage that was present at drop-off gets attributed to the repair. Quotes that were verbal become "you said it would be cheaper." Every one of these problems is preventable, and the prevention happens in the first ten minutes.
The technicians who handle this well don't talk faster. They follow a structured intake every time, for every job.
The six elements of a complete intake
A complete intake captures the same information for every device.
Identification. Customer name, contact details, and date. The device serial number, model, and any external identifiers. This sounds obvious. It's the part most often skipped on "quick" jobs.
Reported issue. What the customer says is wrong, in their words. If they say "the screen is flickering sometimes," write that. Don't translate it into your technical language yet.
Observed condition. What the device looks like when it arrives. Cracks, dents, scratches, missing screws, prior repair signs. Photograph it.
Customer history. Has this device been repaired before. Has it been dropped or had liquid exposure. What did the customer try to fix it themselves. These answers change the diagnostic and the liability.
Diagnostic terms. What you will check, what the diagnostic costs (or that it's free), what happens if no fault is found, and how long the diagnostic takes.
Sign-off. The customer signs to acknowledge the recorded condition, the diagnostic terms, and that no work will begin without a quote and approval.
That's the structure. Every job, every time.
What to document and photograph
Photograph the device before it leaves the counter.
Front, back, sides, ports, and any pre-existing damage. Five to eight photos covering the external state of the device. Date them in your system or include the day's date visible in one shot.
Write down anything the customer reports in their own words. Quotes are more useful than your interpretation. If the customer says "I dropped it in the toilet last week and it worked fine until yesterday," that exact sentence matters more than "liquid damage, intermittent."
The cost of this documentation is two minutes per intake. The cost of skipping it is one disputed repair.
Using AI to build your intake form and script
The intake form needs to capture the six elements consistently. The verbal script needs to communicate the terms clearly. Both can be generated and refined in under an hour.
For the form:
Create a repair intake form for an Apple repair lab. Include sections for: customer details, device identification (model, serial, IMEI where applicable), customer-reported issue in their own words, external condition checklist with space for notes and photos, prior repair history, liquid or drop exposure history, diagnostic terms, estimated diagnostic timeframe, and customer signature acknowledging all of the above. Format as a one-page form that can be filled in on paper or tablet.
For the verbal script:
Write a short verbal script for an Apple repair technician to use at intake. The script should: greet the customer, ask them to describe the problem in their own words, confirm what they brought in, note any visible damage out loud while documenting it, explain that we run a diagnostic before any work begins, explain the cost structure, set a turnaround expectation, and obtain verbal acknowledgement that no work will begin without approval. Tone: professional, friendly, clear. Under 200 words.
Both outputs need adapting to your actual prices, timeframes, and policies. Generate them once, refine them, and use them consistently from then on.
What to do when the customer refuses to sign
It happens. The customer wants the device fixed but doesn't want to sign anything.
The answer is simple. The signature isn't a contract trap. It's a record of what was agreed. If they won't sign, the agreement doesn't exist, and the device shouldn't be accepted.
Phrase it without confrontation: "The form just records what you brought in and what we agreed on. It protects both of us. I can't start a diagnostic without it." Most customers sign at that point. The ones who don't are the ones who would have been the disputed jobs.
You lose one job. You avoid the dispute that would have followed.
Want the complete toolkit?
The Apple Repair Lab Toolkit — v1.0 includes 5 ready-to-use tools: AI diagnostic prompts, a repair estimate template, 6 customer email templates, a SOP template and a weekly KPI tracker. Everything an independent technician needs to run a more consistent lab.
Want the full prompt pack?
There are four more AI techniques in the free guide — diagnosing faster, writing better estimates, handling difficult customer conversations and building your own SOPs.
AI on the Bench — 5 ways to use AI in your Apple repair workflow.
BenchNotes publishes practical tools and guides for Apple technicians every week. Subscribe free to get them in your inbox.