A useful support message says what you tried, which step failed and the exact visible result. Include the device model, player name and nonsecret account reference if relevant. Start with the failure itself rather than a long history of every setting changed, and keep private credentials out of the message unless verified support specifically needs a necessary value.
Name the stage
Installation, account import, guide loading and media playback are different stages. “The app opens but rejects the login” is more informative than “the app does not work.” It also prevents advice aimed at a step you already completed.
Keep the error wording intact
Copy the actual nonsecret error text or attach a redacted screenshot. Rephrasing several different messages as “server down” can lead diagnosis in the wrong direction. Record whether the error appears immediately or after selecting an item.
State one recent change
A password update, new device or catalogue refresh can be relevant context. Separate that fact from assumptions about the cause. A clear short message gives support a practical starting point without requiring unnecessary account data.
A practical sequence
- State the device and player.
- Describe the failed action and exact result.
- Add one relevant recent change and a nonsecret reference.
An example
“Google TV, player version shown in Settings: account import says Invalid credentials; this began after yesterday’s password update” identifies a concrete stage and change.
Questions about this topic
Should I say the server is down when login fails?
Describe the observed error instead of guessing the cause.
Does support need my whole chat history first?
Usually a concise relevant summary is a better starting point.