Everyday conversations
Describe a phone problem abroad without guessing the fault
Explain what happens, when it happens and how it can be observed, then separate inspection from repair authorisation and protect private information.
Heyo · Published
Describe an observation, not a diagnosis
“The motherboard is broken” is a conclusion. “No charging symbol appears when I connect the cable” is an observation you can discuss together. If the cause is unknown, describe the screen, sound or result instead of accepting a translated technical term as a confirmed diagnosis.
For example: “Since yesterday, no charging symbol has appeared after connecting the cable. I tried another cable with the same result.” Mention only attempts you actually made. If the problem is intermittent, say so; one unsuccessful attempt to reproduce it does not mean it never happens.
Put the conditions in order
Explain what action precedes the problem, how long it lasts and how often it happens. Give one time relationship at a time: “The picture freezes after I open the camera.” Then add: “It recovers after about ten seconds.” Do not confuse that duration with repair time or describe one incident as a constant condition.
If you recorded the problem, show only a useful clip and hide notifications or private content. Ask the technician to repeat the symptom they will check, rather than merely asking whether they understand. Separate what they observed from what they suspect.
Distinguish inspection from replacement
Ask: “Is this just an inspection, or will you replace something immediately?” Request separate explanations of cost, timing and any backup arrangements before deciding. Permission to inspect is not permission for every repair, and one casual “yes” should not cover several different actions.
Try: “Please inspect it and explain the result first. Tell me the proposed work and cost before replacing a part.” Ask for a separate explanation and decision if data erasure is involved. This clarifies communication, not a remote diagnosis or a promise that data will be preserved.
Repeat the original observation at collection
Where safe and permitted, repeat the action you originally described, such as checking for the charging symbol after connecting a cable. Record the actual result. One successful check does not verify every function, particularly if the fault was intermittent.
Before unlocking the device or exposing an account, ask why it is needed and whether a less revealing check is possible. Keep passwords, verification codes and payment information out of translation fields. Confirm data-protection arrangements for the device and service involved; translation cannot make that decision for you.