Lead with the failed task
Start with one sentence that describes what you do and what happens instead of the expected result. “The printer receives the job but feeds a blank page” gives someone a better starting point than “printing is broken”. Include when the problem began and whether it happens every time or only under particular conditions.
Avoid diagnosing the cause in the subject line unless it has been established. “Possible cable issue: monitor disconnects after waking” leaves room for investigation. “Faulty graphics chip” can send the conversation down an unnecessarily narrow path when the only evidence is a dark screen.
Add the details that change the answer
Give the exact model and relevant software version, followed by a short description of the connection. For example, say that a laptop reaches the monitor through a USB-C dock, rather than listing every device in the house. Mention a recent update, replacement cable or network change if it preceded the fault.
Then list the meaningful tests in ordinary language. “Works directly with the same cable; fails through the dock” is compact and informative. Include the result of a restart if you tried one. There is no advantage in claiming to have completed suggested steps that you have not actually performed.
Share evidence selectively
Copy the exact error text or attach a screenshot that shows it clearly. Crop or conceal unrelated messages, account details, Wi-Fi passwords and personal files before sharing. Use the manufacturer's official support channel for serial numbers or diagnostic logs when requested; a public forum post should not become a record of your account access information.
For an intermittent issue, include two or three dated examples and roughly how often the task succeeds. A short video may help with a flickering display or an unusual sequence, but explain what the viewer should notice instead of sending a long recording without context.
End with the help you need: the next diagnostic step, confirmation of compatibility or a repair route. Keep a copy of the message and the reply together. When support asks for another test, add its outcome to the same conversation so that the investigation builds on the evidence rather than restarting from the beginning.
