Support can move quickly when a report explains the expected result, the smallest sequence that reproduces the problem, and the exact message that appeared. 'It doesn't work' becomes actionable once those three pieces are present.
Describe the result you expected
Start with one sentence explaining what you were trying to do. For example, say that you completed a claim and expected the loader to accept the key. This tells the person helping you what success would have looked like.
Next, describe what actually happened. Quote the visible error rather than paraphrasing it as a crash or a failure. If no message appeared, say whether the page stayed still, closed, or continued loading.
Include the smallest useful sequence
Write the few steps that led to the problem in their actual order. Mention an account switch, refresh, or repeated launch if it happened. Do not invent a cleaner sequence because you think your actions were supposed to work another way.
Useful context includes the approximate time, browser or device type (sponsored), and whether the issue happens on every attempt. Include version information when it is visible and relevant, but do not paste entire logs just because they exist.
Remove sensitive details
Hide keys, tokens, cookies, and passwords before sending screenshots or logs. Check code snippets too, because they may contain the same key you removed from the page above them.
Finish by saying what you already tried and what changed afterward. A short report with an observed before-and-after result gives support more to work with than a long list of unrelated guesses.
Before sending your report, read it as someone who has never seen your screen. Can they identify what you tried, what should have happened, and what appeared instead? Replace vague phrases such as "everything failed" with the exact action and message, then remove any private account or access details.
A picture can fill in interface details that are difficult to describe. Follow how to capture a useful error screenshot, attach the redacted image, and send it with your short sequence of steps. Keep later updates in the same conversation so the investigation remains easy to follow.