Write down each meaningful action and its result in order. A short sequence helps you avoid repeating the same step and gives support a clearer picture of what changed, without requiring a full technical report.
Use plain language
A note such as “restarted the player; guide opened, but playback still stopped” is enough to be useful. Include the approximate time if the issue is intermittent. Do not label a step successful merely because the device restarted; record whether it changed the original behaviour.
Change one relevant thing
Where practical, follow one suggested action at a time so the result remains understandable. If several changes are necessary, record them separately. Unrecorded resets and account replacements can make it difficult to return to a known state or explain what happened.
Keep the log proportionate
Focus on the actions related to the issue and leave out unrelated personal details. When support asks for an update, send a concise summary rather than hundreds of screenshots. Keep any account credentials out of a log that may be shared more widely.
