How to Write a Support Request That Gets Resolved Faster

'It's not working' requires a follow-up question before anyone can help. Describing what you did, what you expected, and what actually happened instead gives a support team enough to start investigating immediately, without a back-and-forth just to establish the basics.

The exact error message, if there was one, a screenshot, and roughly when the issue occurred are small details that often make the difference between a quick diagnosis and a long, uncertain one.

If the issue is intermittent rather than constant, mentioning that explicitly matters too, since a team investigating an issue they can't reproduce needs to know they're looking for something occasional rather than assuming their fix attempt should immediately resolve it.

Bundling several unrelated problems into a single message tends to slow resolution of all of them, since they usually need to be investigated separately anyway. Separate requests, even sent close together, are usually easier for a support team to track and resolve individually.