State the expected and actual result
Begin with the task you were trying to finish, the expected output and what appeared instead. Include the tool name, relevant plan label and time of the attempt. A message saying it does not work forces the support team to guess which feature or account is involved. Keep the description short enough to scan.
Provide a safe reproduction
List the smallest steps that show the problem using sample data where possible. Redact personal information and unrelated account details from screenshots. Never send passwords, security codes or full payment credentials in a support request. A public example file is preferable to a confidential client document when both demonstrate the same issue.
Ask one decision question
Finish with a specific request: is this export supported on my plan, is there a documented workaround, or should I stop retrying? Keep the ticket reference and any promised next step. Repeatedly submitting the same request can scatter the evidence. This is general tool-selection guidance, not a promise that every listed service offers live support or a response deadline.