Identify the device
Record the device type, brand and model family. A serial number may be needed privately for parts or warranty checks, but it should not appear in a public case study or public form response.
Customer-readable repair standards
How we handle your device
Before any paid work begins, the device, problem, data risk and approval pathway should be clear. These standards explain what we check, what we record, what we do not ask customers to send, and when inspection is needed before a repair decision can be made.
Quick answer
Your device should be handled through a clear intake, diagnosis and approval process. Customer passwords, PINs and banking codes should not be sent through public forms. Repair timing, parts and final price are confirmed only after the available information or device condition has been reviewed.
Before the device is accepted
Record the customer-reported symptom
Keep the customer’s description separate from the technician’s diagnosis. A device that “will not turn on” can have several possible causes and should not be described as a confirmed board fault before testing.
Confirm the priority
Ask whether the device is needed for work, school, accessibility, communication or urgent safety. Priority does not guarantee availability, but it helps determine the safest next step.
Data, accounts and privacy
| Public forms | Do not send passwords, PINs, banking codes, card details, identity-document numbers or private account screenshots. |
|---|---|
| Backups | Customers should be encouraged to back up important files where practical. A damaged or unstable device may not permit a complete backup. |
| Account access | Where sign-in is required, the customer should enter credentials themselves where possible. Any temporary access arrangement should be limited to the approved task. |
| Photos | Device photos should avoid visible messages, contact details, serial labels, addresses and other identifying information unless privately required for the job. |
| Public evidence | Case-study images and notes must be de-identified, redacted and linked to an internal evidence and consent record before they are represented as a customer-approved case study. |
Diagnosis and repair decisions
What a diagnosis should separate
- What the customer reported
- What was observed or tested
- What remains uncertain
- What repair, setup or replacement options are available
- What data or safety risks may affect the decision
When physical inspection may be required
- Liquid damage, swelling, burning smells or heat
- Intermittent power, charging or display faults
- Internal damage, broken hinges or ports
- Data recovery from unstable storage
- Parts compatibility or model verification
Quotes, parts and approval
Scope first
The expected work, diagnostic step or support task should be explained before it begins. Extra work should not be assumed from the original enquiry.
Price confirmation
Online estimates are indicative. Labour, travel, diagnostic work, parts and specialist costs should be confirmed before paid work proceeds.
Parts and alternatives
Where parts are required, compatibility, availability and quality level should be explained. Customers should be told when repair value is uncertain or replacement may be more sensible.
Special handling situations
Liquid or heat damage
Stop using and charging the device when it is wet, swollen, smoking, unusually hot or smells burnt. Continuing to power it can increase damage or create a safety risk.
Scam and remote-access concerns
Do not continue communicating with a suspicious caller. Record what happened, disconnect remote-access tools where safe, contact the relevant bank when financial details may be involved, and preserve useful screenshots without sharing passwords.
Senior and supported customers
Confirm who owns the device, who may approve work, who receives updates and what communication or accessibility needs should be respected.
Device return
The customer should receive a clear summary of work completed, unresolved risks, recommended backups, account actions and any follow-up that may still be required.
Reviewed by the Your IT & Tech Mates technical support team
This standard was checked for practical service boundaries, privacy, consent, data risk and customer approval. It does not replace model-specific diagnosis or written service terms.
Device handling questions
Do I need to provide my password?
Not through a public form. Where account access is genuinely required, the customer should enter the password themselves where possible or agree to a limited, task-specific arrangement.
Should I back up my device before repair?
Yes, where the device is stable enough to do so. Repairs and diagnosis can involve data risk, and damaged storage may fail without warning.
Will you confirm the price before work begins?
The scope and paid work should be confirmed before it starts. A preliminary estimate may change after inspection, model verification or parts availability is checked.
Can you guarantee my data will be recovered?
No. Data recovery depends on the storage condition, previous damage, encryption and whether the device can be read safely. The risks and available options should be explained before recovery work proceeds.
Can my repair be used as a case study?
Only through the evidence and consent process. Identifying information must be removed, images must be reviewed, and the public status must clearly state whether the page is a customer-approved case study or a composite educational example.
Need a clear repair pathway?
Describe the device, model, symptom, suburb and data importance. A technician can then review the safest next step.