Quick answer
Describe the exact symptom, affected source, device/player, connection and time, then state what still works. Keep credentials and registration identifiers out of public screenshots.
Start with one sentence about the failure
Use an observable action: “video opens with sound but no picture,” “the app exits when opening this season,” or “the guide is shifted while live TV works.” An observation is more useful than an unverified explanation such as a server outage or deliberate network block.
Name the reference comparison
Keep the affected and working source names together, with rendition or season/episode where relevant. Record one change and its result. Reinstalling, changing network and replacing the source simultaneously makes the evidence difficult to interpret.
Include the environment
Provide exact device model, OS, player/build, connection path, full date and timezone. For an update issue, distinguish player, OS and firmware versions. For a guide problem, include expected and displayed programme times with their dates.
Redact more than the password box
A QR code, complete playlist URL, activation key, MAC/device identifier or customer list can reveal private access. Crop or cover every such field before sharing a capture. A visible account label can still identify a customer even when the password is hidden.
Send it to the right owner
Use Golden OTT’s private contact route for service/account enquiries. A manufacturer may request its own diagnostics through an existing support ticket; those logs should go through the intended manufacturer process. Do not publish a complete log or send it to an unrelated party just because it concerns a streaming device.

























